Skip to Content
avatar image
Former Member

3 dumps corresponding to dbif_rsql_sql_error

HI Experts,

I have 3 runtime errors in production for the same user that has occurred over the course of last 2 weeks.

Dump details:

Category: Installations Errors

Runtime Error: dbif_rsql_sql_error

Except.: cx_sy_open_sql_db

Short Text:

SQL error "-911" when accessing table /USE/PATI_TRMSTN ( DD02Land DD03L in other two cases)

What happened?

    Error Text of the Database: "SQL0911N The current transaction has been rolled

     back because of a deadlock or timeout. Reason code "68". SQLSTATE=40001 row=1"

What happened?

    Error Text of the Database: "SQL0911N The current transaction has been rolled

     back because of a deadlock or timeout. Reason code "2". SQLSTATE=40001 row=1"

What happened?

    Error Text of the Database: "SQL0911N The current transaction has been rolled

     back because of a deadlock or timeout. Reason code "68". SQLSTATE=40001 row=1"

Source Code points to DELETE operation on the above mentioned tables.

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 "TABL_SOURCE_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:

    Error Text of the Database: "SQL0911N The current transaction has been rolled

     back because of a deadlock or timeout. Reason code "68". SQLSTATE=40001 row=1"

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 "DELETE_DATA" "(METHOD)", 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:

    Error Text of the Database: "SQL0911N The current transaction has been rolled

     back because of a deadlock or timeout. Reason code "2". SQLSTATE=40001 row=1"

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 "TABL_SOURCE_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:

    Error Text of the Database: "SQL0911N The current transaction has been rolled

     back because of a deadlock or timeout. Reason code "68". SQLSTATE=40001 row=1"

The dump mentions deadlock and timeout.

Please let me know how I can rectify this, OSS notes if any would be of great help.

Thanks in advace,

Peter

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • Nov 07, 2012 at 02:31 PM

    Hi Peter,

    You are using DB2 for Linux, Unix and Windows if I am not mistaked?

    The error

    Error Text of the Database: "SQL0911N The current transaction has been rolled

         back because of a deadlock or timeout. Reason code "68". SQLSTATE=40001 row=1"

    indicates a lock timeout issue and is liekyl due to the locklist not being large enough for the applciation.

    What is your release and fixpack level of the DB?

    Are you using Self Tuning Memory Management for the lock parameters?

    I would recommend using this.

    Regards,

    Paul

    Add comment
    10|10000 characters needed characters exceeded

  • Nov 07, 2012 at 02:35 PM

    Without the short dump context this is simply a guessing game, there is 21 Notes related to SQL0911N in SAP Marketplace, have you had a look?

    Regards, Juan

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Nov 07, 2012 at 02:46 PM

    You have 2 lock timeouts (Reason code 68) and 1 deadlock (Reason code 2). Deadlock is more application error. If source is not SAP then redesign your application. If source is SAP open OSS to SAP. For more info you can read SQL0911N and locktimeout - Lock timeout configuration parameter.

    Regards,

    Roman

    Add comment
    10|10000 characters needed characters exceeded

  • Nov 07, 2012 at 03:01 PM

    Hi Peter,

    As per the notes (for db2 udb / DB6)

    for errors SQL0911N see/follow SAP Notes:

    92495   Examination of lock situations (SQL0911)

    327595  Analysis of database lock situations with db6util

    175036  DB6: The DBSL Deadlock Trace

    "

    The SQL error message SQL0911 occurs in the database. Another

    information deadlock (reason code 2) or lock timeout (reason code 68).

    "

    So it appears you have two lock timeouts and 1 deadlock.

    Check the dbdiag.log aat the time of the lock timeout error. It should say something like,

    could not extend the locklist, this would be a sign that you need to increase the size of the locklist or set if to be handled by STMM

    For the deadlock, it may just be a once off, but if it keeps occuring (with same program) then you can collect the traces mentioned in SAP Notes

    327595  Analysis of database lock situations with db6util

    175036  DB6: The DBSL Deadlock Trace

    which MUST be collect at the same time and during the deadlock. This will show what held the lock and what was requesting the lock.

    Hope this helps.

    Regards,

    Paul

    Add comment
    10|10000 characters needed characters exceeded