|
Problem IC64658
|
Status: Closed |
DB2HAICU ON PRIMARY HADR DATABASE MAY FAIL AT THE END OF THE SETUP. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
At the end of the setup, db2haicu on primary node may fail
saying:
The HADR database TSA 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.
In the db2diag.log, we can see the following probe point. Data
#2 showed 'DB2TSA' as the remote instance name in uppercase
letters.
2009-01-21-14.34.07.639034-300 E5403185A588 LEVEL: Error
PID : 344298 TID : 1 PROC :
db2haicu
INSTANCE: db2tsa 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, 6 bytes
db2tsa
DATA #2 : String, 6 bytes
DB2TSA
DATA #3 : String, 10 bytes
amdha01
DATA #4 : String, 10 bytes
amdha02
DATA #5 : String, 3 bytes
TSA
This was because HADR_REMOTE_INST was set to capitalized
letters, as in
HADR instance name of remote server (HADR_REMOTE_INST) = DB2TSA |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* db2haicu users with HADR configuration *
****************************************************************
* PROBLEM DESCRIPTION: *
* At the end of the setup, db2haicu on primary node may fail *
* *
* saying: *
* *
* *
* *
* The HADR database TSA 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. *
* *
* *
* *
* In the db2diag.log, we can see the following probe point. *
* Data *
* #2 showed 'DB2TSA' as the remote instance name in uppercase *
* *
* letters. *
* *
* *
* *
* 2009-01-21-14.34.07.639034-300 E5403185A588 LEVEL: *
* Error *
* PID : 344298 TID : 1 PROC : *
* *
* db2haicu *
* *
* INSTANCE: db2tsa 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, 6 bytes *
* *
* db2tsa *
* *
* DATA #2 : String, 6 bytes *
* *
* DB2TSA *
* *
* DATA #3 : String, 10 bytes *
* *
* amdha01 *
* *
* DATA #4 : String, 10 bytes *
* *
* amdha02 *
* *
* DATA #5 : String, 3 bytes *
* *
* TSA *
* *
* *
* *
* This was because HADR_REMOTE_INST was set to capitalized *
* *
* letters, as in *
* *
* HADR instance name of remote server (HADR_REMOTE_INST) = *
* DB2TSA *
****************************************************************
* RECOMMENDATION: *
* This is a configuration error, ensure the db cfg are correct *
* and in the same case. (e.g. HADR_REMOTE_INST) *
* A warning message will be added to the db2diag.log in DB2 *
* V9.7.0.1. *
**************************************************************** |
| Local Fix: |
Change the value for HADR_REMOTE_INST to lower-case letters on
both primary and standby databases like the following.
HADR instance name of remote server (HADR_REMOTE_INST) = db2tsa |
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
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 10 for Linux, UNIX, and Windows
|
| Solution |
A better diagnostic warning message will be added to db2diag.log
to remind customer to check the db cfg to ensure they match and
are the same case. This message is added to DB2 V9.7.0.1. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 19.11.2009
18.02.2010
18.02.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.0.1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
