|
Problem IC91740
|
Status: Closed |
ADMIN_CMD LOOPS IF MORE THAN 32767 MSG IN SQLLIB/TMP, AND/OR ADMIN_REMOVE_MSGS FAILS WITH SQL20193N RC=10. |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem 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. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users who use admin_cmd(EXPORT, IMPORT or LOAD) on AIX *
* systems. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Please upgrade to V10.1 FixPack 3 or later. *
**************************************************************** |
| Local Fix: |
Please remove message files in the utility file path (sqllib/tmp
or specified by DB2_UTIL_MSGPATH). |
| available fix packs: |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
This problem was first fixed in DB2 V10.1 FixPack 3. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.04.2013
07.10.2013
21.05.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
