|
Problem IC66736
|
Status: Closed |
DB2HAICU CANNOT HANDLE EXISTING FIXED TSA RESOURCES AND EXIT WITH ERROR. |
| product: |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 |
| Problem description: |
When using db2haicu to setup cluster resources, you may see the
following error:
Customer is trying to set up HADR resources using db2haicu. It
run fine on Standby but error out on Primary:
Do you want to validate and automate HADR failover for the HADR
database HADB? [1]
1. Yes
2. No
1
Adding HADR database HADB to the domain ...
There was an error with one of the issued cluster manager
commands. Refer to db2diag.log and the DB2
Information Center for details
db2diag.log shows this error:
FUNCTION: DB2 Common, SQLHA APIs for DB2 HA Infrastructure,
sqlhaListGroupsOnlineAtNode, probe:1400
RETCODE : ECF=0x90000557=-1879046825=ECF_SQLHA_CLUSTER_ERROR
Error reported from Cluster
This will happen if there are already existing resources
(IBM.Application resources with ResourceType == 0)
on the cluster that were originally created outside of db2haicu.
The problem is due to db2haicu not handling
these resources properly. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All db2haicu users with existing SA MP resources *
****************************************************************
* PROBLEM DESCRIPTION: *
* Same as Error description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to V9.8.0.3 *
**************************************************************** |
| Local Fix: |
Use db2haicu to create the DB2 resources first before
creating the fixed resources through other means. |
| available fix packs: |
DB2 Version 9.8 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.8 Fix Pack 4 for AIX and Linux
DB2 Version 9.8 Fix Pack 5 for AIX and Linux
|
| Solution |
Fixed in V9.8.0.3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 01.03.2010
17.01.2011
17.01.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.8.0.3
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.8.0.3
|
 |
