Dump - DBIF_RSQL_SQL_ERROR - CX_SY_OPEN_SQL_DB

[Former Member]

Hi,

I am getting  DBIF_RSQL_SQL_ERROR dump, Dump triggered while updating the table.

Dump Analysis from ST22

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 "ISU_CRMQ_BEFORE_RESTART" "(FUNCTION)", 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/UPDT/EVER_CRMQ ]"
    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"
    "SAPLECRM_CRMQ" or "LECRM_CRMQU07"
    "ISU_CRMQ_BEFORE_RESTART"

    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
   "ISU_CRMQ_BEFORE_RESTART" "(FUNCTION)", or its possible occurrence must be
    declared in the
   RAISING clause of the procedure.
   To prevent the exception, note the following:

Thanks,

Alexander

[Former Member]

Hi Alex

meanwhile im searching around

Would you mind to explain when does this error comes?

Can you past any screenshot or the activity done before it?

Regards,

a

[Former Member]

Hi Andrea,

Thanks for your effort.

I already tried I am not able catch this dump.

Thanks,

Alexander

[ashish_vikas]

This looks to be a transactional Deadlock.

please try to find out if you had any update failures in SM13 for same time when this dump occurred ?

Also check if this happens for any batch job OR SMQ1/SMQ2 processing.

best regards

ashish

[Former Member]

Hi Ashish,

Thanks for your reply.

I dont have access for TXN--> SM13 (I asked DBA people to check the details)

Issue raised while running the batch program and online time.

Thanks,

Alexander