PH20355: HEAD NODE MAY CRASH WITH FODC_APPERR.

APAR status

• Closed as fixed if next.

Error description

• The head node may crash with signal 11 with an incomplete stack
  trace as below -
  
  <StackTrace>
  -----FUNC-ADDR----
  ------FUNCTION + OFFSET------
  
  <DB2TrapResilience>
  <Criteria>
  0x400041801 </Criteria>
  <IsTrapSustainable> No
  </IsTrapSustainable>
  </DB2TrapResilience>
  
  The following error
  is recorded in the db2diag.log:
  
  2019-09-13-04.40.03.219125-240
  I13156797E555 LEVEL: Severe
  PID : 30098 TID : 140164022134528
  PROC : db2sysc 0
  INSTANCE: bigsql NODE : 000 DB :
  BIGSQL
  ...
  EDUID : 28344 EDUNAME: db2agent (BIGSQL) 0
  FUNCTION:
  DB2 UDB, RAS/PD component, pdEDUIsInDB2KernelOperation,
  probe:180
  MESSAGE : Stack analysis failed due to incomplete
  'StackTrace' section in trap
   file.
  
  
  2019-09-13-04.40.06.823587-240 E13233683E1627 LEVEL:
  Severe
  PID : 30098 TID : 140164022134528 PROC : db2sysc
  0
  INSTANCE: bigsql NODE : 000 DB : BIGSQL
  ...
  EDUID : 28344
  EDUNAME: db2agent (BIGSQL) 0
  FUNCTION: DB2 UDB, oper system
  services, sqloEDUCodeTrapHandler, probe:90
  MESSAGE : ADM14011C
  A critical failure has caused the following type of error:
  
  "Trap". The database manager cannot recover from the failure.
  First
   Occurrence Data Capture (FODC) was invoked in the
  following mode:
   "Automatic". FODC diagnostic information is
  located in the following
   directory:
   "/var/ibm/bigsql/diag/DI
  AG0000/FODC_AppErr_2019-09-13-04.40.02.923789
  
  _30098_28344_000/".
  DATA #1 : Signal Number Recieved, 4
  bytes
  11
  DATA #2 : Siginfo, 128 bytes
  0x00007F7A7A80FBF0 : 0B00
  0000 0000 0000 0100 0000 0000 0000
  ................
  0x00007F7A7A80FC00 : 98E8 BE7A 0000 0000 0000
  0000 0000 0000 ...z............
  0x00007F7A7A80FC10 : 0000 0000
  0000 0000 40D1 27EF F79C FFFF
  ........@.'.....
  0x00007F7A7A80FC20 : 0000 0000 0000 0000 0000
  0000 0000 0000 ................
  0x00007F7A7A80FC30 : 0000 0000
  0000 0000 0000 0000 0000 0000
  ................
  0x00007F7A7A80FC40 : 0000 0000 0000 0000 0000
  0000 0000 0000 ................
  0x00007F7A7A80FC50 : 0000 0000
  0000 0000 0000 0000 0000 0000
  ................
  0x00007F7A7A80FC60 : 0000 0000 0000 0000 0000
  0000 0000 0000 ................
  
  2019-09-13-04.40.10.606007-240
  I13235311E510 LEVEL: Error
  PID : 30114 TID : 140186924652416
  PROC : db2vend (PD Vendor Process - 11)
  INSTANCE: bigsql NODE :
  000
  ...
  FUNCTION: DB2 UDB, oper system services, DB2VEND_main,
  probe:1040
  MESSAGE : ZRC=0x870F0009=-2029060087=SQLO_EOF "the
  data does not exist"
   DIA8506C Unexpected end of file was
  reached.
  DATA #1 : String, 63 bytes
  Fenced vendor process pipe
  failure, terminating vendor
  process.
  
  2019-09-13-04.40.11.370708-240 E13235822E608 LEVEL:
  Severe
  PID : 30096 TID : 140234134120192 PROC : db2wdog 0
  [bigsql]
  INSTANCE: bigsql NODE : 000
  ...
  EDUID : 2 EDUNAME:
  db2wdog 0 [bigsql]
  FUNCTION: DB2 UDB, base sys utilities,
  sqleWatchDog, probe:20
  MESSAGE : ADM0503C An unexpected
  internal processing error has occurred. All
   database manager
  processes associated with this instance have been
   shutdown.
  Diagnostic information has been recorded. Contact IBM
   Support
  for further assistance.
  

Local fix

Problem summary

• See problem description
  

Problem conclusion

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

Applicable component levels