Skip to Content
0
Former Member
Feb 24, 2010 at 12:29 PM

Runtime error DBIF_RSQL_SQL_ERROR when executing DTP

460 Views

Hi all,

We have recently upgraded our BW solution from SAPKW70020 to SAPKW70023. After this upgrade we are experiencing runtime errors when executing a DTP. We have a process chain set up that loads data using three different datasources into three different DSO's. They are executed in parallel.

One of DTPs that loads data into the DSO fails with the runtime error DBIF_RSQL_SQL_ERROR and the exception CX_SY_OPEN_SQL_DB:

Short text: SQL error in the database when accessing a table.

What happened?: The database system detected a deadlock and avoided it by rolling back your transaction.

What can you do?: If possible (and necessary), repeat the last database transaction in the hope that locking the object will not result in another deadlock.

Error analysis: An exception occurred that is explained in detail below. The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught in procedure "DD_DD04T_RANGE_DEL" "(FORM)", nor was it propagated by a RAISING clause. Since the caller of the procedure could not have anticipated that the exception would occur, the current program is terminated.

The reason for the exception is: The database system recognized that your last operation on the database would have led to a deadlock. Therefore, your transaction was rolled back to avoid this.

ORACLE always terminates any transaction that would result in deadlock. The other transactions involved in this potential deadlock are not affected by the termination.

If I delete data from the DSO and load manually, everything works ok.

The process chain was running without errors before the upgrade.

Has anyone experienced this problem?

Does anyone know what the table DD04T contain and why this is accessed during the DTP?

Thanks for your help:)

Best regards,

Linda