Regarding runtime error DBIF_RSQL_SQL_ERROR and exception CX_SY_OPEN_SQL_DB

Question

Hi All,
I am loading a COPA cube from a DSO.
There are about 15million records to be loaded. every time i try loading the data, 1 or 2 Data packages gets stuck and finally it leads to a runtime error DBIF_RSQL_SQL_ERROR with exception CX_SY_OPEN_SQL_DB.
When i checked in SM21 transaction code, i got the following message
10:41:52 BTC  018 500 AMRUKV                     BY  O Deadlock occurred
10:41:53 BTC  018 500 AMRUKV                     BY  4 Database error 60 at INS access to table /BIC/FCSDV
10:41:53 BTC  018 500 AMRUKV                     BY  0 > ORA-00060: deadlock detected while waiting for resource
10:41:54 BTC  018 500 AMRUKV                     AB  0 Run-time error "DBIF_RSQL_SQL_ERROR" occurred
10:41:58 BTC  018 500 AMRUKV                     AB  1 > Short dump "080818 104154 s0173bel PB100 " generated
10:41:58 BTC  018 500 AMRUKV                     D0  1 Transaction Canceled 00 671 ( DBIF_RSQL_SQL_ERROR 20080818104154s0173bel_PB1_00 AMRUKV 500 )
In transaction code ST22 i got the following message:
Runtime Errors         DBIF_RSQL_SQL_ERROR
Exception              CX_SY_OPEN_SQL_DB
Date and Time          18.08.2008 10:41:54
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.
     Note which actions and input led to the error.
     For further help in handling the problem, contact your SAP administrator
     You can use the ABAP dump analysis transaction ST22 to view and manage
     termination messages, in particular for long term reference.
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 "WRITE_ICFACT" "(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.
How to correct the error
    Database error text........: "ORA-00060: deadlock detected while waiting for
     resource"
    Internal call code.........: "[RSQL/INSR//BIC/FCSDVD_C02 ]"
    Please check the entries in the system log (Transaction SM21).
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
    "GPD3UMZD6V4YAKZAIWAOCYLV07Y" or "GPD3UMZD6V4YAKZAIWAOCYLV07Y"
    "WRITE_ICFACT"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    The exception must either be prevented, caught within proedure
    "WRITE_ICFACT" "(FORM)", or its possible occurrence must be declared in the
    RAISING clause of the procedure.
    To prevent the exception, note the following:
Can anybody suggest on what can be done?
Thanks in Advance,
Regards
A.T

Answer 1

Hi ,
This is a table space issue....
u will be getting a Dump...as DBIF_RSQL_SQL_ERROR check in ST22. in this DUMP if u scroll down u will find the table for which this is failing. Actually this is like some of the table related to the DSO is not having sufficient space to cary out the transaction. hence it is failing.
U can also see in DB02--> Deadlock....u will see that there is a deadlock for this table. So find the table from ST22 and ask ur basis team to increase the space for this table....
This can be solved only by increasing the space of the table...no other solution....ask help from ur basis team.
Thanks
Sandeep