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

DB2DART TRUNCATES DBPATH NAMES CONTAINING BLANKS ON WINDOWS AND LINUX

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
db2dart fails with 
Error: Failed sqledosd API on open local database directory 
C:\Program\DB2_01. 
 
SQL1031N  The database directory cannot be found on the 
indicated file system. 
on Windows and Linux when you use a dbpath that contains blanks. 
eg. C:\Program Files\DB2_01 would be truncated to 
C:\Program\DB2_01
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 3.                      * 
****************************************************************
Local Fix:
A workaround could be to use Windows generation of 
MS-DOS-compatible 
file name in 8.3 format. 
 
e.g. use 
 
db2 "create db test on 'C:\Progra~1\DB2_01'" 
 
instead of 
 
db2 "create db test on 'C:\Program Files\DB2_01"
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 10.1 Fix Pack 3.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
19.04.2013
02.10.2013
02.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList