IBM Support

IC72105: INSTANCE CRASH FOR MISSING SORT FILE

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as fixed if next.

Error description

  • Error Description:
    
    DB2 instance can crash due DB marked bad message as a result of
    improper error handling.  The stack trace for the problem may
    look like the following: -902 error and may have a stack trace
    like the following:
    
    <StackTrace>
    sqloCrashOnCriticalMemoryValidationFailure
    sqloCrashOnCriticalMemoryValidationFailure@glue1E8
    sqlofmblkEx
    sqldTermApplication
    sqlesrsp
    sqlesrspWrp
    sqleUCagentConnectReset + 0xA0
    sqljsCleanup
    sqljsDrdaAsInnerDriver
    sqljsDrdaAsDriver
    sqleRunAgent
    
    In addition to "DB Marked Bad" errors you may see the
    db2diag.log messages similar to the following:
    
    2009-09-30-13.36.50.901110-420 I268486A536 LEVEL: Error
    PID : 1286386 TID : 1 PROC : db2agent (PROD9) 0
    INSTANCE: inst1 NODE : 000 DB : dbname
    APPHDL : 0-3780 APPID: XXXXXXXX.ID08.01C700203835
    AUTHID : userid
    FUNCTION: DB2 UDB, access plan manager, sqlracal, probe:12
    RETCODE : ZRC=0x87130055=-2028797867=SQLS_PRGERR
    "A data management services programming error occurred."
    DIA8576C A data management services programming error occurred.
    
    >><<
    
    And that is why:
    2009-09-30-13.36.50.901852-420 I269023A470 LEVEL: Error
    PID : 1286386 TID : 1 PROC : db2agent (PROD9) 0
    INSTANCE: inst1 NODE : 000 DB : dbname
    APPHDL : 0-3780 APPID: XXXXXXXX.ID08.01C700203835
    AUTHID : userid
    FUNCTION: DB2 UDB, access plan manager, sqlracal, probe:999
    MESSAGE : Error on rollback
    DATA #1 : Hexdump, 2 bytes
    0x0000000110052858 : 0004 ..
    
    2009-09-30-13.36.50.902493-420 I269494A768 LEVEL: Error
    PID : 1286386 TID : 1 PROC : db2agent (PROD9) 0
    INSTANCE: inst1 NODE : 000 DB : dbname
    APPHDL : 0-3780 APPID: XXXXXXXX.ID08.01C700203835
    AUTHID : userid
    FUNCTION: DB2 UDB, trace services, sqlt_logerr_data, probe:0
    DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
    sqlcaid : SQLCA sqlcabc: 136 sqlcode: -902 sqlerrml: 2
    

Local fix

  • Not applicable
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * N/A                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Error Description:                                           *
    *                                                              *
    *                                                              *
    *                                                              *
    * DB2 instance can crash due DB marked bad message as a result *
    * of                                                           *
    * improper error handling.  The stack trace for the problem    *
    * may                                                          *
    * look like the following: -902 error and may have a stack     *
    * trace                                                        *
    * like the following:                                          *
    *                                                              *
    *                                                              *
    *                                                              *
    * <StackTrace>                                                 *
    *                                                              *
    * sqloCrashOnCriticalMemoryValidationFailure                   *
    *                                                              *
    * sqloCrashOnCriticalMemoryValidationFailure@glue1E8           *
    *                                                              *
    * sqlofmblkEx                                                  *
    *                                                              *
    * sqldTermApplication                                          *
    *                                                              *
    * sqlesrsp                                                     *
    *                                                              *
    * sqlesrspWrp                                                  *
    *                                                              *
    * sqleUCagentConnectReset + 0xA0                               *
    *                                                              *
    * sqljsCleanup                                                 *
    *                                                              *
    * sqljsDrdaAsInnerDriver                                       *
    *                                                              *
    * sqljsDrdaAsDriver                                            *
    *                                                              *
    * sqleRunAgent                                                 *
    *                                                              *
    *                                                              *
    *                                                              *
    * In addition to "DB Marked Bad" errors you may see the        *
    *                                                              *
    * db2diag.log messages similar to the following:               *
    *                                                              *
    *                                                              *
    *                                                              *
    * 2009-09-30-13.36.50.901110-420 I268486A536 LEVEL: Error      *
    *                                                              *
    * PID : 1286386 TID : 1 PROC : db2agent (PROD9) 0              *
    *                                                              *
    * INSTANCE: inst1 NODE : 000 DB : dbname                       *
    *                                                              *
    * APPHDL : 0-3780 APPID: XXXXXXXX.ID08.01C700203835            *
    *                                                              *
    * AUTHID : userid                                              *
    *                                                              *
    * FUNCTION: DB2 UDB, access plan manager, sqlracal, probe:12   *
    *                                                              *
    * RETCODE : ZRC=0x87130055=-2028797867=SQLS_PRGERR             *
    *                                                              *
    * "A data management services programming error occurred."     *
    *                                                              *
    * DIA8576C A data management services programming error        *
    * occurred.                                                    *
    *                                                              *
    *                                                              *
    * >><<                                                         *
    *                                                              *
    *                                                              *
    *                                                              *
    * And that is why:                                             *
    *                                                              *
    * 2009-09-30-13.36.50.901852-420 I269023A470 LEVEL: Error      *
    *                                                              *
    * PID : 1286386 TID : 1 PROC : db2agent (PROD9) 0              *
    *                                                              *
    * INSTANCE: inst1 NODE : 000 DB : dbname                       *
    *                                                              *
    * APPHDL : 0-3780 APPID: XXXXXXXX.ID08.01C700203835            *
    *                                                              *
    * AUTHID : userid                                              *
    *                                                              *
    * FUNCTION: DB2 UDB, access plan manager, sqlracal, probe:999  *
    *                                                              *
    * MESSAGE : Error on rollback                                  *
    *                                                              *
    * DATA #1 : Hexdump, 2 bytes                                   *
    *                                                              *
    * 0x0000000110052858 : 0004 ..                                 *
    *                                                              *
    *                                                              *
    *                                                              *
    * 2009-09-30-13.36.50.902493-420 I269494A768 LEVEL: Error      *
    *                                                              *
    * PID : 1286386 TID : 1 PROC : db2agent (PROD9) 0              *
    *                                                              *
    * INSTANCE: inst1 NODE : 000 DB : dbname                       *
    *                                                              *
    * APPHDL : 0-3780 APPID: XXXXXXXX.ID08.01C700203835            *
    *                                                              *
    * AUTHID : userid                                              *
    *                                                              *
    * FUNCTION: DB2 UDB, trace services, sqlt_logerr_data, probe:0 *
    *                                                              *
    * DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes                *
    *                                                              *
    * sqlcaid : SQLCA sqlcabc: 136 sqlcode: -902 sqlerrml: 2       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 9.7 Fix Pack 4                                *
    ****************************************************************
    

Problem conclusion

  • First fixed on DB2 9.7 Fix Pack 4
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC72105

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-10-21

  • Closed date

    2011-05-26

  • Last modified date

    2011-05-26

  • APAR is sysrouted FROM one or more of the following:

    IC64710

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

  • R970 PSN

       UP

  • R970 PSY

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IC72105

Modified date: 26 May 2011