home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC89344 Status: Geschlossen

AUTOMATIC HADR PAIR REINTEGRATION DID NOT OCCUR AFTER RESTARTING STANDBY
SERVER

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 V9.7 Fix Pack 7 and below                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v9.7 Fix Pack 8                               * 
****************************************************************
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?}
verfügbare FixPacks:
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

Lösung
First fixed in DB2 v9.7 Fix Pack 8
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC91748 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
03.01.2013
02.04.2013
02.04.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP8
Problem behoben lt. FixList in der Version
9.7.0.8 FixList