home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IC64169 Status: Closed

DB2 AND NSE: DB2IUPDT DOES NOT CREATE NEW LINKS TO RESOURCES AND DDL IF
THE LINKS EXISTED PREVIOUSLY

product:
DB2 FOR LUW / DB2FORLUW / 910 - DB2
Problem description:
When NSE and DB2 are installed, db2iupdt does not create 
new links to resources and ddl if the links existed previously. 
 
Consider the following sample scenario: 
 
DB2 and NSE are installed in the path say /opt/IBM/db2/V9.1 
After creating an instance say db2inst1 
the symbolic links ddl and resources present in 
$HOME/sqllib/db2ext, point to 
 resources -> /opt/IBM/db2/V9.1/db2ext/resources 
 ddl -> /opt/IBM/db2/V9.1/db2ext/ddl 
 
Later new version of DB2 and NSE are installed in another path 
/opt/IBM/db2/V9.1_new 
cd /opt/IBM/db2/V9.1_new/instance 
db2iupdt db2inst1 
The instance db2inst1 got updated successfully, 
 
After updating the instance the symbolic links still point to 
the same old path 
resources -> /opt/IBM/db2/V9.1/db2ext/resources 
ddl -> /opt/IBM/db2/V9.1/db2ext/ddl
Problem Summary:
USERS AFFECTED 
 
All using DB2 and NSE 
 
PROBLEM DESCRIPTION 
 
see ERROR DESCRIPTION 
 
PROBLEM SUMMARY 
 
see ERROR DESCRIPTION
Local Fix:
Manually remove the links sqllib/db2ext/resources and 
sqllib/db2ext/ddl and run db2iupdt afterwards.
available fix packs:
DB2 Version 9.1 Fix Pack 9  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

Solution
The complete fix for this problem first appears in DB2 UDB 
Version 9.1 FixPak 9.
Workaround
Manually remove the links sqllib/db2ext/resources and 
sqllib/db2ext/ddl and run db2iupdt afterwards.
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC64180 IC64183 IC64542 IC64546 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
28.10.2009
14.04.2010
14.04.2010
Problem solved at the following versions (IBM BugInfos)
9.0.,
9.1.
Problem solved according to the fixlist(s) of the following version(s)
9.1.0.9 FixList