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

DB2HAICU CANNOT HANDLE EXISTING FIXED TSA RESOURCES AND EXIT WITH ERROR.

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When using db2haicu to setup cluster resources, you may      * 
* seethefollowing error:Customer is trying to set up HADR      * 
* resources using db2haicu.Itrun fine on Standby but error out * 
* on Primary:Do you want to validate and automate HADR         * 
* failover for theHADRdatabase HADB? [1]1. Yes2. No1Adding     * 
* HADR database HADB to the domain ...There was an error with  * 
* one of the issued cluster managercommands. Refer to          * 
* db2diag.log and the DB2Information Center for                * 
* detailsdb2diag.log shows this error:FUNCTION: DB2 Common,    * 
* SQLHA APIs for DB2 HA                                        * 
* Infrastructure,sqlhaListGroupsOnlineAtNode,                  * 
* probe:1400RETCODE :                                          * 
* ECF=0x90000557=-1879046825=ECF_SQLHA_CLUSTER_ERRORError      * 
* reported from ClusterThis will happen if there are already   * 
* existing resources(IBM.Application resources with            * 
* ResourceType == 0)on the cluster that were originally        * 
* created outside ofdb2haicu.The problem is due to db2haicu    * 
* not handlingthese resources properly.                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade to version 9.5 Fp6 or later                          * 
****************************************************************
Local-Fix:
Use db2haicu to create the DB2 resources first before 
creating the fixed resources through other means.
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
first fixed in V9.5v FP6
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC66733 IC66736 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
01.03.2010
12.11.2010
12.11.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP6,
9.5.V
Problem behoben lt. FixList in der Version