Fixes are available
DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows
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
APAR status
Closed as program error.
Error 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
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
Problem summary
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * DB2HAICU ON PRIMARY HADR DATABASE MAY FAIL AT THE END OF THE * * SETUP. * **************************************************************** * RECOMMENDATION: * * Upgrade to 9.5 FP5 * ****************************************************************
Problem conclusion
Problem was first fixed in Version 9.5 Fix Pack 5
Temporary fix
Comments
APAR Information
APAR number
IZ42701
Reported component name
DB2 UDB QP AIX
Reported component ID
5724E2500
Reported release
950
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-01-28
Closed date
2009-12-23
Last modified date
2009-12-23
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
DB2 UDB QP AIX
Fixed component ID
5724E2500
Applicable component levels
R950 PSN
UP
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEPGA","label":"DB2 Query Patroller"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"950"}]
Document Information
Modified date:
04 October 2021