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

INSTANCE REGISTRY VARIABLES ARE DELETED WHEN DB2IMIGR FAILS.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
When db2imigr fails for some reason(for example, the instance is 
still active), the instance registry variables are deleted 
during the undo process. 
 
 
For example, if you have these variables set before the upgrade: 
 
$ db2set -all 
[i] DB2_NUM_CKPW_DAEMONS=0 
[i] DB2COMM=TCPIP 
[g] DB2SYSTEM=myhostname 
 
after upgrade the instance variables are no longer defined: 
 
$ db2set -all 
[g] DB2SYSTEM=myhostname
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 6.                       * 
****************************************************************
Local Fix:
- take a backup of the registry before upgrade 
$ db2set -all 
[i] DB2_NUM_CKPW_DAEMONS=0 
[i] DB2COMM=TCPIP 
[g] DB2SYSTEM=myhostname 
 
- restore the registry after upgrade: 
 
db2set DB2_NUM_CKPW_DAEMONS=0 
db2set DB2COMM=TCPIP
Solution
First fixed in Version 9.7 Fix Pack 6.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
30.09.2011
13.06.2012
13.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)