Hi,
I'm experiencing a TIME OUT when updating a cube with data from an ODS. This is due to some complex calculations in the UpdateRule. It needs more time than the standard 600 seconds. When I schedule the update as a job to be executed in the background, when looking in sm50, still I can see that dialog processes are opend anyway. This leads to a time out. Isn't here a way to run updates in the background? Is it because I've coded som routines in th UpdateRule? Any solution ideas on my problem? Why is this?
BR
/Daniel
1 Answer
-
Best Answer
Former MemberPosted on Feb 25, 2005 at 07:08 PMDaniel,
1. Do you have internal tables of very large size running in a loop??...If so, try to reduce the size of the tables as much as possible. One way to do it is, try reducing the datapacket size in your InfoPackage. Open your infopackage
>right click>"DataS. default data transfer" --> reduce maximum datapacket size to 10000 or 5000 or even lower (by default it is 20,000). Then run your job.If still not successful, then consider the following...
2. Try to recude size of internal tables as much as possible by using more restricted select statements.
3. This also could be because of the code. try to avoid SELECT statements inside a big loop, if you have any. Try to remove loop iniside another loop situations if any and can be avoided.
Let me know if you still have this problem.
Good Luck
J
Add comment
Add comment