IBM Support

IC87209: ADMIN_CMD LOOPS IF MORE THAN 32767 MSG IN SQLLIB/TMP, AND/OR ADMIN_REMOVE_MSGS FAILS WITH SQL20193N RC=10.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • The ADMIN_CMD manages the message files on server by unique
    operation ids, and corresponding unique message names.
    
    The random_number in operation id (<random_number>_<userid>)
    would be values in the range of 0-32767 on AIX and Windows
    system.
    This lack of variety on the operation id can cause the following
    issues.
    
    a) Infinite loop in admcmdCreateNewMsgFile()
    
    Once utility message path (sqllib/tmp by default) is filled by
    32767 number of message files, the function keeps looping to
    look for unique id (but never find).
    In this case, admin_cmd(EXPORT, IMPORT or LOAD) never returns to
    caller, and db2fmp consumes high CPU time.
    
    b) Duplicate operation id.
    
    DB2 intends to use unique operation id, but concurrent execution
    of the ADMIN_CMD()s can exploit a timing hole to use duplicate
    operation id. And Subsequent ADMIN_REMOVE_MSGS() will fail with
    SQL20193N rc=10 due to the duplicate operation id.
    
    This defect will fix these issues by using more wide variety of
    and non-duplicate operation id.
    

Local fix

  • Please remove message files in the utility file path (sqllib/tmp
    or specified by DB2_UTIL_MSGPATH).
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users who use EXPORT, IMPORT or LOAD via ADMIN_CMD on AIX.   *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Please upgrade to V9.7 FixPack 8 or later.                   *
    ****************************************************************
    

Problem conclusion

  • This problem was first fixed in DB2 V9.7 FixPack 8.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC87209

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-10-15

  • Closed date

    2013-04-08

  • Last modified date

    2014-05-21

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

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

    IC91740

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSN

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IC87209

Modified date: 21 May 2014