IZ16345: DB2 DOES NOT MAKE USE OF IPC MESSAGE QUEUES GREATER THAN 64K, EVEN THOUGH MSGMNB IS GREATER THAN 64K ON HPUX

DB2 Version 9.5 Fix Pack 3b for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 2a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 2  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 fixed if next.

Error description

• On HP UNIX platformes, the following error can be seen in the
  db2diag.log:
  
  2008-01-31-19.23.53.326330+540 E4135528A742       LEVEL: Error
  (OS)
  PID     : 17540                TID  : 1           PROC :
  db2lfrm2 0
  INSTANCE: db2inst1             NODE : 000         DB   : CODB
  APPHDL  : 0-549                APPID:
  *LOCAL.db2inst1.080131102129
  AUTHID  : DB2INST1
  FUNCTION: DB2 UDB, oper system services, sqlowqueInternal,
  probe:40
  MESSAGE : ZRC=0x870F0041=-2029060031=SQLO_QUE_NOT_SENT "Message
  Not Sent"
            DIA8557C No message was sent using the message queue.
  CALLED  : OS, -, write
  OSERR   : EAGAIN (11) "ﾷ￩ﾨﾛﾷﾯ ﾷﾠﾫￇ ﾯﾇﾨﾉﾀ￣ ﾬﾔ  ﾛﾫﾷ`￘`￫."
  DATA #1 : system V message queue identifier.,
  PD_TYPE_SYSV_QUEUE_ID, 4 bytes
  0x000B0078
  DATA #2 : Pointer, 8 bytes
  0x800003ffc0009558
  DATA #3 : unsigned integer, 8 bytes
  48
  
  The cause of the error, is due an IPC message queue created by
  the DB2 instance becoming full and no additional data can be
  written to the IPC message queue.
  
  The size of the IPC message queue is governed by the UNIX kernel
  parameter msgmnb.  When the size of the IPC message queue is
  greater than 64k as set by msgmnb in the kernel, DB2 will still
  only create IPC message queues of 64K.
  
  To avoid the 64k IPC message queue size limitation, DB2 has to
  be compiled with the compile flag: __BIGMSGQUEUE_ENABLED
  
  This APAR ensures that DB2 is compiled with the
  "__BIGMSGQUEUE_ENABLED" flag set, to allow IPC message queues
  used by DB2 to be greater than 64k.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users, running on HP-UX with MsgQs larger than 64K (set by
  msgmnb kernel parameter)
  ****************************************************************
  PROBLEM DESCRIPTION:
  The customer may see errors from function  sqlowqueInternal(),
  indicating that write() call fails with OSSER = EAGAIN..
  ****************************************************************
  RECOMMENDATION:
  Upgrade to v9.5 FP2
  ****************************************************************
  

Problem conclusion

Temporary fix

Comments

APAR Information

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

  IZ16052

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

Fix information

Applicable component levels

• R950 PSY

     UP