DB2 - Problembeschreibung
Problem IC87209 | Status: Geschlossen |
ADMIN_CMD LOOPS IF MORE THAN 32767 MSG IN SQLLIB/TMP, AND/OR ADMIN_REMOVE_MSGS FAILS WITH SQL20193N RC=10. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * 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. * **************************************************************** | |
Local-Fix: | |
Please remove message files in the utility file path (sqllib/tmp or specified by DB2_UTIL_MSGPATH). | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows | |
Lösung | |
This problem was first fixed in DB2 V9.7 FixPack 8. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC91740 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 15.10.2012 08.04.2013 21.05.2014 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP8 | |
Problem behoben lt. FixList in der Version | |
9.7.0.8 |