home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC72449 Status: Closed

SYSPROC.ADMIN_REMOVE_MSGS DOES NOT DELETE MESSAGE FILES(GENERATE D BY
ADMIN_CMD) WHOSE NAME IS APPENDED WITH UNDERSCORE(_).

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Executing a LOAD operation via ADMIN_CMD and option MESSAGES ON 
SERVER creates and leaves a message file on the database server. 
This message file is named like 
'LOAD_<STRING>_<USERID-postfix>'. 
SYSPROC.ADMIN_REMOVE_MSGS should be used to remove these message 
files if no longer needed. 
 
In certain situations DB2 will name the message file like 
following: 'LOAD_<STRING>_' 
E.g. if the user id information is not available at the time of 
the DB2 internal message file rename. 
 
The attempt to remove a message file whose name ends with 
underscore will not be successful although ADMIN_REMOVE_MESSAGES 
reports successful execution as shown below. 
 
# ls 
LOAD_N8BYSB_ 
# db2 "CALL SYSPROC.ADMIN_REMOVE_MSGS('31393')" 
 
  Return Status = 0 
# ls 
LOAD_N8BYSB_ 
 
 
This APAR addresses the correct removal of such message files.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 4                        * 
****************************************************************
Local Fix:
Check the default message file path (if DB2_UTIL_MSGPATH is not 
set) '<instowner home>/sqllib/tmp' and delete these message 
files manually if no longer needed.
available fix packs:
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 9.7 Fix Pack 4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
08.11.2010
01.05.2011
01.05.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP4
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.4 FixList