IBM Support

IT05370: DB2 PRIMARY INSTANCE MAY CRASH DURING EXECUTION OF DB2STOP IN HADR

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • There is a limitation in the protocol used during shutdown
    that can lead to this problem and affect db2stop only.
    
    1. db2diag.log
    
    2014-10-21-00.57.13.842019+480 I447685308A1644    LEVEL: Event
    PID     : 44762284             TID  : 1           PROC : db2stop
    INSTANCE: db2inst1             NODE : 000
    EDUID   : 1
    FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSingleNode,
    probe:1130
    DATA #1 : String, 34 bytes
    /home/db2inst1/sqllib/adm/db2stop2
    DATA #2 : Hexdump, 256 bytes
    0x0FFFFFFFFFFF4B80 : 2F68 6F6D 652F 6462 3269 6E73 7064 2F73
    /home/db2inst1/s
    0x0FFFFFFFFFFF4B90 : 716C 6C69 622F 6164 6D2F 6462 3273 746F
    qllib/adm/db2sto
    0x0FFFFFFFFFFF4BA0 : 7032 004E 4F4D 5347 0053 4E00 0000 0000
    p2.NOMSG.SN.....
    0x0FFFFFFFFFFF4BB0 : 0000 0000 0000 0000 0000 0000 0000 0000
    ................
    0x0FFFFFFFFFFF4BC0 : 0000 0000 0000 0000 0000 0000 0000 0000
    ................
    0x0FFFFFFFFFFF4BD0 : 0000 0000 0000 0000 0000 0000 0000 0000
    ................
    0x0FFFFFFFFFFF4BE0 : 0000 0000 0000 0000 0000 0000 0000 0000
    ................
    0x0FFFFFFFFFFF4BF0 : 0000 0000 0000 0000 0000 0000 0000 0000
    ................
    0x0FFFFFFFFFFF4C00 : 0000 0000 0000 0000 0000 0000 0000 0000
    ................
    0x0FFFFFFFFFFF4C10 : 0000 0000 0000 0000 0000 0000 0000 0000
    ................
    0x0FFFFFFFFFFF4C20 : 0000 0000 0000 0000 0000 0000 0000 0000
    ................
    0x0FFFFFFFFFFF4C30 : 0000 0000 0000 0000 0000 0000 0000 0000
    ................
    0x0FFFFFFFFFFF4C40 : 0000 0000 0000 0000 0000 0000 0000 0000
    ................
    0x0FFFFFFFFFFF4C50 : 0000 0000 0000 0000 0000 0000 0000 0000
    ................
    0x0FFFFFFFFFFF4C60 : 0000 0000 0000 0000 0000 0000 0000 0000
    ................
    0x0FFFFFFFFFFF4C70 : 0000 0000 0000 0000 0000 0000 0000 0000
    ................
    
    <strip>
    
    2014-10-21-00.57.18.858613+480 E447693878A376     LEVEL: Warning
    PID     : 41551002             TID  : 76333       PROC : db2sysc
    0
    INSTANCE: db2inst1             NODE : 000         DB   :
    P012BAND
    APPHDL  : 0-3
    EDUID   : 76333                EDUNAME: db2agent (P012BAND) 0
    FUNCTION: DB2 UDB, data protection services, sqlpterm, probe:100
    MESSAGE : Posting HDR_RTYPE_HARD_CHK
    
    2. Stack.
    
    -------Frame------ ------Function + Offset------
    0x09000000092D717C sqloCrashOnCriticalMemoryValidationFailure +
    0x34
    0x0900000006C44440
    diagnoseMemoryCorruptionAndCrash__13SQLO_MEM_POOLFUlCPCcCb +
    0x2B8
    0x0900000006C440B0
    diagnoseMemoryCorruptionAndCrash__13SQLO_MEM_POOLFUlCPCcCb@glue8
    0C + 0x7C
    0x090000000780B8FC
    .MemTreePut.fdpr.clone.224__13SQLO_MEM_POOLFP8SMemNodeUlP17SqloC
    hunkSubgroup + 0x14
    0x09000000078126EC sqlofmblkEx + 0x288
    0x09000000077EF55C sqlofmblkEx@glue801 + 0x78
    0x0900000006B40118
    sqlpterm__FP16sqeLocalDatabaseP8sqeAgentP5sqlcab + 0x38C
    0x090000000770B9D0 CleanDB__16sqeLocalDatabaseFP5sqlca + 0x2BC
    0x090000000777E174
    TermDbConnect__16sqeLocalDatabaseFP8sqeAgentP5sqlcai + 0x1A0
    0x090000000777AAE4
    AppStopUsing__14sqeApplicationFP8sqeAgentUcP5sqlca + 0xCF0
    0x0900000007A45DE0
    AppLocalStart__14sqeApplicationFP14db2UCinterface + 0xF4
    0x090000000796E3FC sqlelostWrp__FP14db2UCinterface + 0x4C
    0x090000000796E4B0 sqleUCengnInit__FP14db2UCinterfaceUs + 0x60
    0x0900000007A4BE1C sqleUCagentConnect + 0x2A0
    0x0900000007EE4994
    @72@sqleDeactivateOneDB__FP14db2UCconHandleP8sqeAgent + 0x164
    0x0900000007619440 DeactivateDBs__8sqeDBMgrFP8sqeAgentb + 0x52C
    0x0900000007618D7C sqleDeactivateDBs__FP8sqeAgentb + 0xB4
    0x0900000006AA9E40 RunEDU__8sqeAgentFv + 0x224
    0x090000000776A114 EDUDriver__9sqzEDUObjFv + 0xDC
    0x0900000007788D94 sqloEDUEntry + 0x250
    

Local fix

  • N/A.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply DB2 V9.7.11                                            *
    ****************************************************************
    

Problem conclusion

  • Problem was first fixed in DB2 UDB version 9.7 fix pack 11.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT05370

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-11-05

  • Closed date

    2015-10-07

  • Last modified date

    2015-10-07

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

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

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSN

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IT05370

Modified date: 07 October 2015