IY94828: AN ERROR DURING COMMUNICATION BETWEEN THE DATABASE ENGINE AND A FENCED ROUTINE IS INCORRECTLY HANDLED IN THE DB2FMP PROCESS.

DB2 UDB Version 8.1 FixPak 16 (also known as Version 8.2 FixPak 9 )

APAR status

• Closed as program error.

Error description

• When a fenced routine is invoked, it will be run inside the
  db2fmp process in db2.
  If any error happens during a communication between the db2fmp
  process and the database agent process, then it can result in
  the db2fmp process crashing with signal #11 rather than handling
  the error more gracefully.
  
  The following is an example from the db2diag.log showing how a
  normal error (such as running out of memory), can result in the
  db2fmp mis-handling the error:
  
  2006-11-27-09.07.04.079262+060 E5225365A454  LEVEL: Severe (OS)
  PID     : 1106                 TID  : 12121  PROC : db2fmp (C) 0
  INSTANCE: db2                  NODE : 000
  FUNCTION: opersystem services, getPrivateChunksFromOs, probe:100
  CALLED  : OS, -, malloc
  OSERR   : ENOMEM (12) "Not enough space"
  MESSAGE : Private memory and/or virtual address space exhausted
  DATA #1 : Requested size, PD_TYPE_MEM_REQUESTED_SIZE, 8 bytes
  266240
  
  2006-11-27-09.07.04.113866+060 I5226189A351  LEVEL: Severe
  PID     : 1106                 TID  : 12121  PROC : db2fmp (C) 0
  INSTANCE: db2                  NODE : 000
  FUNCTION: DRDA Communication Manager, sqljcReceive, probe:30
  RETCODE : ZRC=-2026503986=SQLZ_RC_OUT_OF_MEMORY, SQLT_SQLJC
            "Out of private memory"
  
  2006-11-27-09.07.04.786223+060 I5228996A268  LEVEL: Severe
  PID     : 1106                 TID  : 12121  PROC : db2fmp (C) 0
  INSTANCE: db2                  NODE : 000
  FUNCTION: DB2 UDB, common communication, sqlccFreeIPCs, probe:9
  RETCODE : ZRC=0xFFFFFFFF=-1
  
  2006-11-27-09.07.04.870192+060 I5229889A319  LEVEL: Severe
  PID     : 1106                 TID  : 12121  PROC : db2fmp (C) 0
  INSTANCE: db2                  NODE : 000
  FUNCTION: common communication, sqlccFreeIPCs, probe:100
  RETCODE : ZRC=-2146500356=SQLO_INV_PARM "Invalid input
             parameter"
  
  
  The db2fmp will receive a signal #11 SIGSEGV with a stack
  traceback that looks something like this:
  
  sqlerFreePSetiBlocks + 0x10
  sqlerReleaseLibLatch + 0x94
  sqlerPoolConHandle + 0xb8
  sqlerFmpListener + 0x1350
  
  Note that it does not have to be a memory error.  Above was only
  an example.  ANY error during this particular communication can
  result in the db2fmp failure.
  

Local fix

Problem summary

• Users affected: see PMR text
  Problem description: see PMR text
  Problem summary: see PMR text
  

Problem conclusion

• First fixed in DB2 UDB Version 8.1, FixPak 16
  

Temporary fix

• see PMR text
  

Comments

APAR Information

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

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

  IY95611

Modules/Macros

• ENG_SQER
  

Fix information

• Fixed component name

  DB2 UDB ESE SOL

• Fixed component ID

  5765F4102

Applicable component levels

• R810 PSN

     UP

• R820 PSN

     UP