IBM Support

IC73472: MISLEADING "MESSAGE QUEUE FULL" ERROR MESSAGES IN DB2DIAG.LOG

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In V9.5 Fixpak 7 on Windows platforms, there may be misleading
    error messages reported in the db2diag.log
    
    e.g.
    
    2010-12-17-13.27.42.859000+060 I25918F726         LEVEL: Error
    PID     : 15240                TID  : 11144       PROC :
    db2bp.exe
    INSTANCE: db2inst1        NODE : 000
    EDUID   : 11144
    FUNCTION: DB2 UDB, oper system services, sqlowque, probe:35
    MESSAGE : Message queue full. QueCb.
    DATA #1 : Hexdump, 76 bytes
    0x0000000004560254 : 0200 0000 F401 0000 0000 0000 C000 0000
    ................
    0x0000000004560264 : 0100 0000 C9FF 0700 7518 0000 7451 0100
    ........u...tQ..
    0x0000000004560274 : 0000 0000 0000 0000 4643 5230 4F33 3331
    ........XXX0O331
    0x0000000004560284 : 3639 3136 4100 0000 0000 0000 0000 0000
    6916A...........
    0x0000000004560294 : 0000 0000 0000 0000 0000 0000
    ............
    
    2010-12-17-13.27.42.874000+060 I26646F404         LEVEL: Error
    PID     : 15240                TID  : 11144       PROC :
    db2bp.exe
    INSTANCE: db2inst1        NODE : 000
    EDUID   : 11144
    FUNCTION: DB2 UDB, oper system services, sqlowque, probe:36
    MESSAGE : Message queue full. Message.
    DATA #1 : Hexdump, 16 bytes
    0x00000001401E8810 : 4400 0000 0000 0000 0000 0000 0100 0000
    D...............
    
    This can for instance be triggered by the CLP execution of a
    statement that returns a lot of data to the db2.exe frontend
    
    process.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * DB2 for Windows users                                        *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Misleading error messages in the db2diag.log.                *
    * These messages do not indicate a problem with DB2.           *
    * The Message queue full situation is handled gracefully       *
    * internally.                                                  *
    *                                                              *
    * The fix for this apar will remove these messages.            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 V9.5 FixPack 8                                *
    ****************************************************************
    

Problem conclusion

  • This problem has first been fixed in V9.5 FixPack 8
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC73472

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    950

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-12-23

  • Closed date

    2011-07-29

  • Last modified date

    2011-07-29

  • 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 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R950 PSN

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.5","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
29 July 2011