We have a cube with multiple partitions on the fact table. These partitions
are based on the date of an order and the most recent partition contains the
orders for the last seven days. This partition's storage setting is Automatic
MOLAP and it watches the fact table for changes.

When an update is received, the partition will process and the aggregations
will be built, then one of two things will happen (I am seeing this in a
profiler trace):

1- I'll see a message with the EventClass "Notification" and EventSubClass
"8-Object Altered" with no other data and the cube will show the updated data.

2- I see a message with the EventClass "Error", no EventSubClass, and the
message "While attempting to acquire one or more locks, the transaction was
canceled." The partition won't be updated but will process again and usually
get the same error. This will happen 5-10 times before it is finally udpated.

What exactly is it trying to update that is locked? How can I find out what
is being locked and alleviate the locking problem?

Thanks,
John Williams

My guess is that while processing the partition, another notification came
in and the server cancelled processing because the new notification would
invalidate the MOLAP cache shortly.

HTH,
Akshai
--
This posting is provided "AS IS" with no warranties, and confers no rights
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.

"John Williams" <JohnWilliams (AT) discussions (DOT) microsoft.com> wrote