dbTalk Databases Forums  

Non-shared dimension fails on full cube process (OLAP 2000)

microsoft.public.sqlserver.olap microsoft.public.sqlserver.olap


Discuss Non-shared dimension fails on full cube process (OLAP 2000) in the microsoft.public.sqlserver.olap forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Fergus
 
Posts: n/a

Default Non-shared dimension fails on full cube process (OLAP 2000) - 08-25-2006 , 12:53 PM






I have a cube with a dimension which is built from a column in the fact
table. i.e. it does not have a dimension lookup table.
When a row is deleted from the fact table and I reprocess the cube, I get
the error:
"A member with a key value of '<deleted_value>' was found in the fact table
but was not found in the level '<level>' of the dimension '<dim_name>'"
Obviously, this is looking at the "old" cube data and comparng it with the
"new" dimension, which it clearly should not, because this is a "full
process".
The only way I could get around this after 3 days of experimenting was:
copy the cube structure to a new name
drop the old cube
copy the cube structure back to the old name
process the cube

Is there a way to avoid or correct this?
Can I get rid of the cube data without dropping the cube?
Can I flag the cube as "not processed" somehow?
( I already tried going through the cube editor and saving without making
any actual changes. Didn't help)
I believe I could process a shared dimension and force the cube to a "not
Processed" state, but I have lots of other cubes that would then have to be
fully processed.
--
Thanks and Good Luck.
Fergus


Reply With Quote
  #2  
Old   
yongli
 
Posts: n/a

Default RE: Non-shared dimension fails on full cube process (OLAP 2000) - 08-25-2006 , 04:45 PM






Will making the dimension shared solve this problem?

I used to have the similar problem when processing virtual dimension when a
row iwas dropped from the dimension table. but that was incremental update...

"Fergus" wrote:

Quote:
I have a cube with a dimension which is built from a column in the fact
table. i.e. it does not have a dimension lookup table.
When a row is deleted from the fact table and I reprocess the cube, I get
the error:
"A member with a key value of '<deleted_value>' was found in the fact table
but was not found in the level '<level>' of the dimension '<dim_name>'"
Obviously, this is looking at the "old" cube data and comparng it with the
"new" dimension, which it clearly should not, because this is a "full
process".
The only way I could get around this after 3 days of experimenting was:
copy the cube structure to a new name
drop the old cube
copy the cube structure back to the old name
process the cube

Is there a way to avoid or correct this?
Can I get rid of the cube data without dropping the cube?
Can I flag the cube as "not processed" somehow?
( I already tried going through the cube editor and saving without making
any actual changes. Didn't help)
I believe I could process a shared dimension and force the cube to a "not
Processed" state, but I have lots of other cubes that would then have to be
fully processed.
--
Thanks and Good Luck.
Fergus


Reply With Quote
  #3  
Old   
privatenews
 
Posts: n/a

Default RE: Non-shared dimension fails on full cube process (OLAP 2000) - 08-28-2006 , 12:12 AM



Hello Fergus,

You may also consider use a dummy dimension table with only column that is
same as that in the fact table.

I think you could not configure cube as "not processed" since only
partition has a readonly property "state" indicates the process state of
cube partitions:

297933 FIX: Full Process of a Remote Partition Unprocesses Other Remote
Partitions in Same Server
http://support.microsoft.com/default...b;EN-US;297933

You may consider remove all aggregations and/or partitions to see if this
helps in your situation. Please see the following links for more details:

Script to Remove all Aggregations
http://blogs.msdn.com/bi_systems/articles/164496.aspx

Copying OLAP Partitions using DSO in Analysis Services 2000
http://geekswithblogs.net/darrengosb...les/53082.aspx

If you have any questions or concerns, please let's know. I look forward to
your comments.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.


Reply With Quote
  #4  
Old   
Fergus
 
Posts: n/a

Default RE: Non-shared dimension fails on full cube process (OLAP 2000) - 08-28-2006 , 10:11 AM



Thanks for trying.
The hint on the "Dummy Dimension Table", assuming it only ever got
incremental updates, and was never reprocessed, would probably work to mask
the situation.
However it's not a fix, which my business folks want.
The other items do not address my situation.
--
Thanks and Good Luck.
Fergus



""privatenews"" wrote:

Quote:
Hello Fergus,

You may also consider use a dummy dimension table with only column that is
same as that in the fact table.

I think you could not configure cube as "not processed" since only
partition has a readonly property "state" indicates the process state of
cube partitions:

297933 FIX: Full Process of a Remote Partition Unprocesses Other Remote
Partitions in Same Server
http://support.microsoft.com/default...b;EN-US;297933

You may consider remove all aggregations and/or partitions to see if this
helps in your situation. Please see the following links for more details:

Script to Remove all Aggregations
http://blogs.msdn.com/bi_systems/articles/164496.aspx

Copying OLAP Partitions using DSO in Analysis Services 2000
http://geekswithblogs.net/darrengosb...les/53082.aspx

If you have any questions or concerns, please let's know. I look forward to
your comments.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.



Reply With Quote
  #5  
Old   
privatenews
 
Posts: n/a

Default RE: Non-shared dimension fails on full cube process (OLAP 2000) - 08-29-2006 , 02:41 AM



Hello Fergus,

Thank you for your reply and please rest assured your feedback on this
product limitation is routed to the proper channel. I also encourage you
submit via the link below

http://lab.msdn.microsoft.com/produc...k/default.aspx

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support


================================================== ===

This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.