Wednesday, March 7, 2012

AS dont process cubes

Hi,

my english is very bad, so i try to explain....

We have a MOLAP structure and several jobs executing SSIS packages. This jobs yesterday and today don′t finished , just stay executing without error messages and the cubes not up to date. I stop and restart AS instance and the cubes is up to date. But i can not do this every time. I see in Event viewer and dont have any error messages. I see in other forun to disable proactive caching...is this correct ?...wich problems i can have doing this ?...and what i can do to resolve this problem ?..

Thanks

To clarify, you have a cube with MOLAP partitions. Do you have proactive caching enabled? Are you using SSIS to process your cubes?

Thanks,
Bryan

|||

Yes..i have a cube with MOLAP partitions, but proactive caching is disabled and SSIS process the cubes.

But in some cases only stop and restart AS to process de cubes, and the job with ssis package stay runing ..stay runing..stay runing and dont do anything....i start the profile and the command to begin the cube shows up, but stay...stay..stay....can you help me ?....thanks a lot

|||

It's very hard to say what is happening with the cube. So, I would recommend some experimentation. Does the cube process when done manually in BIDS or in SSMS? Do parts of the olap database process while other parts hang?

There have been some posts and blogs indicating this happens when a resource limitation is being hit. I would think you would see something in the error logs regarding this, but maybe not. One of the recommendations from this was to break apart the processsing job into a series of steps. This might help as well.

Another poster on SQL Junkies is complaining of the same issue. You may want to reach out to him/her to see if the problem has been resolved:

http://groups.google.com/group/microsoft.public.sqlserver.datawarehouse/browse_thread/thread/77d4f542ff7d288a/307dfc5dc1bcdfc3#307dfc5dc1bcdfc3

Finally, I would recommend making sure you are on SP2.

Good luck,
Bryan

No comments:

Post a Comment