Here is a familiar phrase for anyone who has worked in SAP BW or BI production support environment: ‘Short dump in the Warehouse’
Checking transaction ST22, you should see another familiar screen telling you about a deadlock issue.
Personally, I find it hilarious that the system message tells you to try again and hope the outcome will be different.
There are a few ways to get around the deadlock issue and reload your data successfully. I like the two options below because that means less hoops to jump through (from a business approval standpoint).
Option 1: Delete the Index
In BI 7.0, the process chain creation wizard is smart enough to delete and generate an index when loading data into an infocube. In BW 3.x, this data target administration had to be specified.
I was performing the ETL manually, so forgot this step. In general, deleting the index of an infocube will speed up the loading process. (I can find the SAP Note if anyone is interested.)
Option 2: Change the Package Size
If you would prefer not to bother the Basis team to increase the global memory size, then changing the DTP package size is another quick remedy for dead lock issues.
Since dead lock situations arise when a number of processes encounter a circular waiting pattern (where A waits for B, B waits for C, and C waits for A), decreasing the number of parallel processes may be a remedy.
Here, I changed the default size of a data package from 20,000 kByte to 5,000 kByte. Also, I changed the number of data packages from a previous value of 10 to 5.
After deleting the index on my cube and changing the package setting, I restarted the load.
The cube was loaded with 3.4 million records in under 40 minutes. That’s a success in my book. =D
Posted via email from hau
Leave a comment