Hi,
There are many situations where we come across this deadlock error, they r while loading, activating,dead locks on update rules etc...
<i>Here I,m giving the reason for loading in cube</i>
For basic InfoCubes in SAP BW, there are two fact tables for including transaction data: The F and the E fact table.
Unlike the E fact table, the F fact table contains the information about the request from where the transaction data originates.
When loading data (when receiving requests), the system writes data into the F fact table.
During "compression", the system summarizes data from different requests and writes it to the E fact table.
To ensure good reporting performance, it is important that you only keep data from a few requests in the F fact table, which means that you should compress requests as soon as possible.
Also bear in mind that deleting transaction data according to the request is only possible from the F fact table, as only this table contains the information regarding which data belongs to which request.
You should therefore compress a request as soon as you are certain that the data loaded is correct.
When you install BW on an ORACLE database, BITMAP indexes are created on the fact tables to improve the reporting performance of the system.
These indexes have a negative effect on system performance when you load data; the deadlock (ORA 60) mentioned above may also occur so that data loading terminates completely. The DEADLOCKs occur during parallel insert operations because ORACLE does not support a blocking concept for BITMAP indexes at data record level.
<b>To</b> have access to service.sap u just need the installation number which is there in system status and other details... contact ur basis guy he will help u in this regard...
Regards
Siddhu
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.