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

ADD DBPARTITIONNUM fails with SQL1031N if the DB is created on a path that
contains symbolic links to different physical paths

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
In a DPF environment, if a database was created with a path 
that contains symbolic links to different physical paths, the 
ADD DBPARTITIONNUM command could fail with SQLCODE -1031 
(SQL1031N) 
because the database configuration path from a non-catalog 
partition cannot be resolved on the catalog partition.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DPF                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 10.1 Fix Pack 1                           * 
****************************************************************
Local Fix:
Do not use symlink for the Database path.
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
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
problem was fixed in db2 Version 10.1 Fix Pack 1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.06.2012
16.11.2012
16.11.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList