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

FILENAME IN DB2LOOK -O PARAMETER IS CONVERTED INTO LOWER-CASE AND IT MAY
INDUCE 'DB2LOOK UTILITY COULD NOT OPEN FILE' ERROR

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
On Windows systems, if you specify an output filename in 
upper-case letters by the -o option in the db2look utility, the 
file is created in lower-case. 
 
  In addition, if you specify an output file pathname in 
multi-byte letters, the different multi-byte named file may be 
created or db2look fails with 'db2look utility could not open 
file' error. 
 
  There is no such problem on Unix based systems.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Windows users                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2 Version 9.5 FixPak 10                         * 
****************************************************************
Local Fix:
Not use upper-case or multi-byte letters as an output file 
pathname
Solution
Problem was first fixed in Version 9.5 FixPak 10
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC84046 IC87893 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
07.06.2012
26.10.2012
26.10.2012
Problem solved at the following versions (IBM BugInfos)
9.5.
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.10 FixList