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

DB2CPTSA DOES NOT ALLOW THE HA SCRIPTS FOR BOTH V95 AND V97 TO CO-EXIST

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
In a case where the same physical nodes contain 2 instances of 
V95, and if one of the instances is upgraded to V97 then the V95 
related files in the location '/usr/sbin/rsct/sapolicies/db2' 
get replaced by the V97 files. 
 
The same thing also happens when the script 
'/opt/ibm/db2/V97_ESE_T_FP2/install/tsamp/db2cptsa' is run, ie. 
the V95 related files will get replaced by the V97 files. 
 
Similarly running the script 
'/opt/ibm/db2/V9.5_FP5/install/tsamp/db2cptsa' will cause the 
V97 related files to be replaced by the V95 files. 
 
So the basic problem is that the script 'db2cptsa' when executed 
does not allow the files for both V9.5 and V9.7 to co-exist. 
 
The design should be that 'db2cptsa' will update existing 
scripts that are at the same level or lower for the given 
version.  So the db2cptsa should only be concerned about the 
same 
version and not affect other versions.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All Users of DB2 V9.5 below FixPack 7                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* In a case where the same physical nodes contain 2            * 
* instancesofV95, and if one of the instances is upgraded to   * 
* V97 then theV95related files in the                          * 
* location'/usr/sbin/rsct/sapolicies/db2'get replaced by the   * 
* V97 files.The same thing also happens when the               * 
* script'/opt/ibm/db2/V97_ESE_T_FP2/install/tsamp/db2cptsa' is * 
* run,ie.the V95 related files will get replaced by the V97    * 
* files.Similarly running the                                  * 
* script'/opt/ibm/db2/V9.5_FP5/install/tsamp/db2cptsa' will    * 
* causetheV97 related files to be replaced by the V95 files.So * 
* the basic problem is that the script 'db2cptsa'              * 
* whenexecuteddoes not allow the files for both V9.5 and V9.7  * 
* to co-exist.The design should be that 'db2cptsa' will update * 
* existingscripts that are at the same level or lower for the  * 
* givenversion.  So the db2cptsa should only be concerned      * 
* about thesameversion and not affect other versions.          * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.5 FixPack 7.                               * 
****************************************************************
Local Fix:
- Ensure /usr/sbin/rsct/sapolicies/db2/ contain only v9.7 
scripts 
  e.g. run db2cptsa from V9.7 install path 
  /opt/ibm/db2/V9.7/install/tsamp/db2cptsa 
- Append the V9.5 scripts to /usr/sbin/rsct/sapolicies/db2/spec 
  e.g. 
  ls <DB2 V9.5 Install Path>/ha/tsa >> 
/usr/sbin/rsct/sapolicies/db2/spec 
- Copy the scripts from DB2 V9.5 installation: 
  e.g. 
  cp <DB2 V9.5 Install Path>/ha/tsa/* 
/usr/sbin/rsct/sapolicies/db2
available fix packs:
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem First Fixed in DB2 V9.5 FixPack 7.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC71172 IC71328 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
24.08.2010
21.12.2010
21.12.2010
Problem solved at the following versions (IBM BugInfos)
9.5.FP7
Problem solved according to the fixlist(s) of the following version(s)
9.1.0.7 FixList
9.5.0.7 FixList