dbif_rsql_sql_error in process chain

[Former Member]

Hi guru's

while maintaining process chains I came across this error at DTP.I thought it occurs because many chains are running at same time and causing table space issues.So I waited for some time and repaired it but still error persists.I am not authorised to access DBO2.So what else can I do to rectify it?Whether I have to wait for some more time and escalate the issue to BASIS?

Regards

Kuldeep

[former_member182196 · Accepted solution]

This message was moderated.

[Former Member · Accepted solution]

Hi Satendra

Explanation which you have shared is really useful to get indepth clarity of concepts.Thanks a lot

Kind regards

Kuldeep

[former_member182196 · Accepted solution]

Hi,

Thanks for your appreciation kuldeep...... really i am very happy....

Regards,

SM

[former_member182196 · Accepted solution]

Dear Kuldeep,

Can u mark it my ans as a correct ans again bcz my reply has been hided by moderator..... If you do this it will be a good reference for others also....So please mark it as correct ans I am not bothering about Marks....

Regards,

Satendra Mishra

[former_member182196]

Hi....

U can check SAP Note : 631668........for ur reference......it may help u......

Symptom

This note applies only to BW systems under ORACLE.

Loading data into InfoCubes terminates with an error: ORA 60, "deadlock detected". The monitor log displays the entry "CALLER 70 missing" and the request is flagged as red.

Other terms

Caller 70, DEADLOCK, ora0060, bitmap, indexes, DBIF_RSQL_SQL_ERROR

CX_SY_OPEN_SQL_DB

Reason and Prerequisites

In SAP BW, there are two fact tables for including transaction data for Basis InfoCubes: 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.

Therefore, transaction data is always written to the F fact table and the package dimension contains the request to which the loaded data belongs.

Using 'Request compression', the system reads the data of a request from the F fact table and writes it to the E fact table without request ID and compresses.

For good reporting performance, you must keep only the data of a few requests in the F fact table since the F fact table is partitioned according to the key of the package dimension and the data of all requests is always read. Therefore, you should compress the request if you are sure that the loaded data is correct and that you no longer have to delete the request.

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 have a negative effect on the performance when loading data and the deadlock mentioned above (ORA 60) may occur as a result. The DEADLOCKs occur during parallel insert operations because ORACLE does not support a blocking concept for BITMAP indexes at data record level.

Solution

Before loading movement data, delete secondary indexes from the F fact table and create them again after the loading process. If the F fact table is small, no performance problems occur.

Alternatively, you can also load requests serially into InfoCubes by first loading the data only into the Persistent Staging Area (PSA) and then serially into the InfoCube. If you use the data transfer process (DTP) for loading in BW 7.0, this option is no longer available.

           NOTE

           This avoids the deadlock problem. However, you should note that after some loading processes, it is necessary to reorganize the BITMAP indexes because they degenerate very heavily and, therefore, the read and writing performance deteriorates dramatically.

Regards,

SM

[former_member185177]

Hi Kuldeep,

It is because of index problem. 

Please go through the steps suggested in the sap note 1692199.

https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/sno/ui_entry/entry.htm?param=69765F6D6F6465...

Hope it will resolve your issue.

Regards,

Krishna Chaitanya.

[Former Member]

Hi Krishna

I deleted indexes and again I fixed the issue by repeating failed step and it is running successfully.

Kind regards

Kuldeep

[former_member185177]

Is it not correct/helpful answer for you?

[Former Member]

actually it was correct answer but Satendra has given conceptual explanation and i dont know how to assign correct answer to two persons.

[former_member185177]

I think you need correct answer.  You did not raise for the conceptual explanation. 

Anyways its up to you.  No problem

Cheers,

Krishna Chaitanya.

[former_member182470]

Whatever has fixed your question, you should mark it as answered. You can assign Helpful answers to your favorite replies. This is the only way to justify multiple answers. I feel Krishna deserves..

[RamanKorrapati]

Hi,

Please check with your DB team. its SQL related error. As well as It may solve notes also as per your bw version. need use right one.

Thanks

[former_member182470]

Please implement SAP Note: 1606565. Otherwise you may install SP26 in your system.