LI73874: HADR PRIMARY CRASH TRIGGERED BY DISCONNECTION FOLLOWED BY CONNECTION QUICKLY.

DB2 Version 9.5 Fix Pack 4  for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 4a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

APAR status

• Closed as program error.

Error description

• After an HADR connection was broken on standby, any further
  attempts to reconnect quickly with primary may lead to a crash
  on primary because of partial cleanup during the last HADR
  connection closure.
  
  Sample entries on db2diag.log :
  
  2008-10-01-16.30.42.899422-240 E14146A321         LEVEL: Event
  PID     : 16132                TID  : 2199111800080PROC :
  db2hadrp
  (LKMDDB) 0
  INSTANCE: db2inst1        NODE : 000
  FUNCTION: DB2 UDB, High Availability Disaster Recovery,
  hdrSetHdrState,
  probe:10000
  CHANGE  : HADR state set to P-Peer (was P-NearlyPeer)
  
  2008-10-01-16.30.42.900136-240 E14468A321         LEVEL: Event
  PID     : 16132                TID  : 2199111800080PROC :
  db2hadrp
  (LKMDDB) 0
  INSTANCE: db2inst1                NODE : 000
  FUNCTION: DB2 UDB, High Availability Disaster Recovery,
  hdrSetHdrState,
  probe:10000
  CHANGE  : HADR state set to P-NearlyPeer (was P-Peer)
  
  2008-10-01-16.30.49.023938-240 E15449A522         LEVEL: Severe
  PID     : 16132                TID  : 2199111800080PROC :
  db2hadrp
  (LKMDDB) 0
  INSTANCE: inst8                NODE : 000
  FUNCTION: DB2 UDB, oper system services, sqloEDUCodeTrapHandler,
  probe:10
  MESSAGE : ADM0503C  An unexpected internal processing error has
  occurred.  ALL DB2 PROCESSES ASSOCIATED WITH THIS INSTANCE HAVE
  BEEN
  SHUTDOWN. Diagnostic information has been recorded.  Contact IBM
  Support
  for further assistance.
  
  There will not be any errors logged on standby's db2diag.log
  during this crash. Callstacks for db2hadrp would look like:
  
   0000020003E49FEA ossDumpStackTrace + 0x00d6
    0000020003E475BE _ZN11OSSTrapFile4dumpEmiP7siginfoPv + 0x00c2
    0000020002420604 sqlo_trce + 0x0418
    0000020000C98F10 sqloEDUCodeTrapHandler + 0x0084
    000003FFFFB62210 address: 0x3ffffb62210
    000002000170405A
  _Z15sqlplfrScanNextPvS_P13sqle_agent_cbPP9SQLP_LFPBPlPmP26SQL
  PLFR_SCAN_NEXT_METADATAl + 0x004a
    000002000179E448 hdrEduP(HDR_DBCB*, HDR_EDU_ARGS*, bool,
  SQLOPDBNODEADDRHANDLE
  *, unsigned long*) + 0x0f98
    00000200017A4026 hdrEduEntry(char*, unsigned int) + 0x0de6
    0000020000C99E2E _Z13sqloCreateEDUPFvPcjES_mP13SQLO_EDU_INFOPi
  + 0x0432
    0000020000C9ADA8 sqloInitEDUServices + 0x0794
    0000020000C94A86 sqloSystemControllerMain + 0x030a
    0000020000C95D84 sqloRunInstance + 0x035c
    000000008000BD10 DB2main + 0x0610
    000000008000C288 main + 0x0010
    00000200041ED558 __libc_start_main + 0x0100
    000000008000669A __libc_start_main + 0x007e
  

Local fix

Problem summary

• Users Affected:
  All HADR users
  
  Problem Description:
  HADR PRIMARY CRASH TRIGGERED BY DISCONNECTION FOLLOWED BY
  CONNECTION QUICKLY.
  
  Problem Summary:
  HADR PRIMARY CRASH TRIGGERED BY DISCONNECTION FOLLOWED BY
  CONNECTION QUICKLY.
  

Problem conclusion

• First fixed in DB2 UDB Version 9.5, FixPak 4 (s090429)
  

Temporary fix

Comments

APAR Information

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

  LI73873

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

Fix information

• Fixed component name

  DB2 UDE ESE LIN

• Fixed component ID

  5765F4104

Applicable component levels

• R950 PSY

     UP