LI73601: TRAP IN REGISTERAGENT DURING NODE FAILURE RECOVERY IN LOCALDEACTIVATE

DB2 Version 9.5 Fix Pack 3b for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 4  for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 3 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

• The scenario requires a DPF instance with 2 or more databases
  that have been explicitly activated. When a node failure of the
  catalog node is detected on a non-cat node, node failure
  recovery is run by calling LocalDeactivate. In this function we
  loop through all dbs which are activated and make a connection
  to that db to deactivate it. However, if we run into an error or
  warning we would exit while setting the m_appState for this
  application. When this application is reused again to deactivate
  the next db in the loop, it will break certain assumptions and
  lead the application down a code path that can result in a panic
  or trap. The m_appState needs to be reset after each deactivate
  of a db, so that it can be reinitialized if needed on subsequent
  deactivates.
  
  Following two callstacks may be seen:
  
  0000002A96838B78 _ZN17OSSAtomicSigned649incrementEv + 0x0014
  0000002A96838BA6 _ZN11OSSAtomic649incrementEv + 0x0006
  0000002A9687BA76 _ZN19sqzReservableObject13ReserveObjectEb +
  0x0006
  0000002A9688017C _ZN11sqeDatabase9ReserveDBEv + 0x000c
  0000002A96FC524B _ZN11sqeDatabase13RegisterAgentEP8sqeAgent +
  0x0041
  0000002A96F7E8F7 _ZN8sqeAgent8AssocAppEP14sqeApplicationi +
  0x06b7
  0000002A96F8A151
  _ZN14sqeApplication22AppSecondaryStartUsingEP8sqeAgentP16SQLE_CL
  IENT_INFOP5sqlca + 0x0475
  0000002A96FC0D9A _ZN8sqeDBMgr15LocalDeactivateEP8sqeAgentPKci +
  0x01f6
  0000002A96F67BF3 _Z20sqleSubRequestRouterP8sqeAgentPjS1_ +
  0x0685
  0000002A96F66F67 _Z21sqleProcessSubRequestP8sqeAgent + 0x005f
  0000002A96F7DF63 _ZN8sqeAgent6RunEDUEv + 0x03eb
  
  or
  
  0000002A97CB238C sqloDumpEDU + 0x002c
  0000002A96F75ABD _Z10sqle_panicv + 0x0043
  0000002A96FC1029 _ZN8sqeDBMgr15LocalDeactivateEP8sqeAgentPKci +
  0x0485
  0000002A96F67BF3 _Z20sqleSubRequestRouterP8sqeAgentPjS1_ +
  0x0685
  

Local fix

Problem summary

• See Problem Description above.
  

Problem conclusion

• First fixed in DB2 UDB Version 9.5, FixPak 3
  

Temporary fix

Comments

APAR Information

• 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 UDE ESE LIN

• Fixed component ID

  5765F4104

Applicable component levels

• R950 PSY

     UP