IBM Support

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

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • On HP UNIX platformes, the following error can be seen in the
    db2diag.log:
    
    2008-01-31-19.23.53.326330+540         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) "Resource Temporarily unavailable"
    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

  • see problem description above
    

Problem conclusion

  • First Fixed in DB2 Version 9.1 fixpack 5
    

Temporary fix

Comments

APAR Information

  • APAR number

    IZ16052

  • Reported component name

    DB2 UDB ESE HP-

  • Reported component ID

    5765F4103

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-02-20

  • Closed date

    2008-07-10

  • Last modified date

    2011-01-22

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

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

    IZ16345

Fix information

  • Fixed component name

    DB2 UDB ESE HP-

  • Fixed component ID

    5765F4103

Applicable component levels

  • R910 PSY

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
22 January 2011