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

AUTOMATIC HADR PAIR REINTEGRATION DID NOT OCCUR AFTER RESTARTING STANDBY
SERVER

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
In a HADR/TSA environment, where the language is not set as 
English, automatic HADR pair reintegration fails in the case 
where the standby server is restarted. 
 
E.g. In a French environment, where LANG=fr_FR@euro 
The standby instance is successfully started after a reboot, 
but the start HADR is not done automatically by TSA. 
 
The db2V97_start.ksh script is being initiated correctly, but 
reintegration does not take place. This is due to the 
following line within the db2V97_start.ksh script: 
 
su - ${DB2INSTANCE?} -c "db2 list database directory" | grep 
"Database name" \ 
| tr "[a-z]" "[A-Z]" | awk '{print $4}' > ${dbFN?} 
 
The script expects the pattern "Database name", but in a French 
environment this would instead read as "Nom de la base de 
donnツes". As a result the database is not activated as expected.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 V10 Fixpak 2 and below                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10 Fixpack 3                                 * 
****************************************************************
Local Fix:
In the case of a French environment, the following change will 
need to be done to the db2V97_start.ksh script: 
 
Change: 
su - ${DB2INSTANCE?} -c "db2 list database directory" | grep 
"Database name" \ 
| tr "[a-z]" "[A-Z]" | awk '{print $4}' > ${dbFN?} 
 
To: 
su - ${DB2INSTANCE?} -c "db2 list database directory" | grep 
"Nom de la base de donn" \ 
| tr "[a-z]" "[A-Z]" | awk '{print $8}' > ${dbFN?}
available fix packs:
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
First fixed in DB2 v10 Fixpak 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.04.2013
07.10.2013
07.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList