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 IC62705 Status: Geschlossen

DB2HAICU FAILS AT THE END OF THE SETUP ON PRIMARY.

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
If an instance name contains underscores (_) like 'dba_hadr', 
then db2haicu will fail at the end of the setup on primary. 
db2haicu will not fail on the standby side. This is because 
db2haicu relies on "_" as the delimiter for all the resource 
names. lssam will show both primary and standby resource groups 
but not an HADR resource group, it fails while creating one. 
 
Sample db2haicu interactive mode output: 
... 
Adding HADR database DBA_HADR to the domain ... 
The HADR database TESTDB cannot be added to the cluster because 
the standby instance is not configured in the domain. Run 
db2haicu on the standby instance to configure it into the 
cluster. 
All cluster configurations have been completed successfully. 
db2haicu exiting ... 
 
In db2diag.log, you will see a message like this: 
 
2009-08-19-10.00.52.138860-300 E5618A591          LEVEL: Error 
PID     : 421924               TID  : 1           PROC : 
db2haicu 
INSTANCE: dba_hadr             NODE : 000 
EDUID   : 1 
FUNCTION: DB2 Common, SQLHA APIs for DB2 HA Infrastructure, 
sqlhaUICreateHADR, probe:900 
RETCODE : 
ECF=0x9000056F=-1879046801=ECF_SQLHA_HADR_VALIDATION_FAILED 
          The HADR DB failed validation before being added to 
the cluster 
DATA #1 : String, 8 bytes 
dba_hadr 
DATA #2 : String, 8 bytes 
dba_hadr 
DATA #3 : String, 8 bytes 
amdha1 
DATA #4 : String, 8 bytes 
amdha2 
DATA #5 : String, 8 bytes 
TESTDB
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users on cluster env                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* db2haicu fails at the end of the setup on primary            * 
* wheninstance name contains underscore                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to 9.5 FP6                                           * 
****************************************************************
Local-Fix:
Either create a new instance name or change the existing 
instance name such that it does not contain any underscore, and 
recatalog the database on both primary and standby.
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
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

Lösung
db2haicu fails at the end of the setup on primary when instance 
name contains underscore
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC64856 IC65623 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
21.08.2009
31.05.2010
31.05.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP6
Problem behoben lt. FixList in der Version