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

DB2CKUPGRADE FAILS WITH DBT5501N IF PATH/FILENAME CONTAINS "-D"

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
db2ckupgrade can fail with DBT5501N if the path/filename options 
contains "-d" 
 
For example : 
 
ls -l /home/db2inst1/int-data/ 
total 0 
 
db2ckupgrade SAMPLE -l /home/db2inst1/int-data/toi-dito.log 
DBT5501N  The db2ckupgrade utility could not open or write to 
the file named "/home/db2inst1/intata/toiito.log". 
 
As you can see , the script removed "-d" from int-data (replaced 
by intata) and removed the "-d" from toi-dito.log (replace by 
toiito.log).
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All Platforms                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Db2 LUW v11.1 Mod 3 Fixpack 3                     * 
****************************************************************
Local Fix:
Do not include the "-d" with the path/filename on this command.
available fix packs:
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows

Solution
First Fixed in Db2 LUW v11.1 Mod 3 Fixpack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
09.08.2017
16.03.2018
16.03.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)