DB2 - Problem description
Problem IC62705 | Status: Closed |
DB2HAICU FAILS AT THE END OF THE SETUP ON PRIMARY. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problem description: | |
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 Summary: | |
**************************************************************** * 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. | |
available fix packs: | |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows | |
Solution | |
db2haicu fails at the end of the setup on primary when instance name contains underscore | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC64856 IC65623 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 21.08.2009 31.05.2010 31.05.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.5.FP6 | |
Problem solved according to the fixlist(s) of the following version(s) |