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 IC74719 Status: Closed

ALTOBJ DOES NOT DELETE THE MESSAGE FILE AFTER IT RUNS SUCCESSFUL LY AND ONE
CANNOT PICK WHERE THE MESSAGES FILE SHOULD GO.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
When ALTOBJ is called to alter columns for a give table, 
it calls db2load stored procedure under the cover to load 
the data into the table.  The message file by default goes 
under sqllib/tmp directory which is not visible to the 
user. 
. 
This apar is to do two things: 
. 
1)  Option under DB2_UTIL_MSGPATH registry to pick the location 
of the message file. 
. 
2)  Remove the message file after a successful completion 
of ALTOBJ. 
.
Problem Summary:
When ALTOBJ is called to alter columns for a give table, 
it calls db2load stored procedure under the cover to load 
the data into the table.  The message file by default goes 
under sqllib/tmp directory which is not visible to the 
user. 
. 
This apar is to do two things: 
. 
1)  Option under DB2_UTIL_MSGPATH registry to pick the location 
of the message file. 
. 
2)  Remove the message file after a successful completion 
of ALTOBJ.
Local Fix:
create symbolic link from sqllib/tmp to somehwere where you 
want the messages file to go.
available fix packs:
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
fixed >= v97 fpk4
Workaround
create symbolic link from sqllib/tmp to somehwere where you 
want the messages file to go.
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
25.02.2011
07.07.2011
07.07.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FPk4
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList