|
Problem IC81043
|
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 / 970 - 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 9.7 Fix Pack 6 *
**************************************************************** |
| Local Fix: |
Do not use symlink for the Database path. |
| available fix packs: |
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 |
problem was fixed in db2 Version 9.7 Fix Pack 6 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC84294
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 26.01.2012
06.06.2012
06.06.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.6
|
 |
