DB2 - Problembeschreibung
Problem IC90504 | Status: Geschlossen |
DB2HAICU MIGHT GENERATE SEVERAL DB2DIAG.LOG ERROR MESSAGES DURING DOMAIN STARTUP. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
The db2haicu utility might report several error messages in the db2diag.log that can be safely ignored. After the domain is created, db2haicu requests to bring it online. During this operation db2haicu periodically polls RSCT to determine if the cluster has been successfully brought up. With the current implementation this can cause numerous error messages to be reported in the db2diag.log, all of which can be safely ignored. Here is an example of the error messages seen in the db2diag.log : 2013-02-26-01.34.39.650836+060 E26008586E460 LEVEL: Error PID : 7653 TID : 140737352337184 PROC : db2havend (db2ha) INSTANCE: db2inst1 NODE : 000 HOSTNAME: myHost2 FUNCTION: DB2 UDB, high avail services, db2haGetObjectState, probe:4858 DATA #1 : String, 114 bytes Line # : 4858---2610-417 No response from the resource manager IBM.ConfigRM. The resource manager has terminated. DATA #2 : signed integer, 4 bytes 262156 2013-02-26-01.34.40.652256+060 E26009047E870 LEVEL: Error PID : 7653 TID : 140737352337184 PROC : db2havend (db2ha) INSTANCE: db2inst1 NODE : 000 HOSTNAME: myHost2 FUNCTION: DB2 UDB, high avail services, db2haMapResourceNameToHandle, probe:19838 MESSAGE : RM-specific error detected during query. If the affected RM is not the owner of the resource being queried then this is not a fatal error, but otherwise the operation leading to this error will fail. DATA #1 : String, 14 bytes IBM.PeerDomain DATA #2 : String, 17 bytes DWH_DB2_HA_domain DATA #3 : String, 0 bytes Object not dumped: Address: 0x0000000000000000 Size: 0 Reason: Address is NULL DATA #4 : String, 89 bytes 2610-415 Cannot execute the command. The resource manager IBM.ConfigRM is not available. DATA #5 : unsigned integer, 4 bytes 262154 2013-02-26-01.34.40.653378+060 E26009918E868 LEVEL: Error PID : 7653 TID : 140737352337184 PROC : db2havend (db2ha) INSTANCE: db2inst1 NODE : 000 HOSTNAME: myHost2 FUNCTION: DB2 UDB, high avail services, db2haMapResourceNameToHandle, probe:19838 MESSAGE : RM-specific error detected during query. If the affected RM is not the owner of the resource being queried then this is not a fatal error, but otherwise the operation leading to this error will fail. DATA #1 : String, 12 bytes IBM.PeerNode DATA #2 : String, 17 bytes DWH_DB2_HA_domain DATA #3 : String, 0 bytes Object not dumped: Address: 0x0000000000000000 Size: 0 Reason: Address is NULL DATA #4 : String, 89 bytes 2610-415 Cannot execute the command. The resource manager IBM.ConfigRM is not available. DATA #5 : unsigned integer, 4 bytes 262154 2013-02-26-01.34.46.379268+060 I26010787E469 LEVEL: Error PID : 7653 TID : 140737352337184 PROC : db2havend (db2ha) INSTANCE: db2inst1 NODE : 000 HOSTNAME: myHost2 FUNCTION: DB2 UDB, high avail services, getLastErrMsg, probe:19782 DATA #1 : signed integer, 4 bytes 11 DATA #2 : String, 132 bytes Line # : 19782--- 2610-611 The command group has been sent, but the session was interrupted before all responses could be received. 2013-02-26-01.34.46.379813+060 E26011257E599 LEVEL: Error PID : 7653 TID : 140737352337184 PROC : db2havend (db2ha) INSTANCE: db2inst1 NODE : 000 HOSTNAME: myHost2 FUNCTION: DB2 UDB, high avail services, db2haMapResourceNameToHandle, probe:200 MESSAGE : Look up for the name of resource failed. DATA #1 : DB2HA Cluster Error Code, PD_TYPE_DB2HA_CLUSTER_ERROR_CODE, 4 bytes error: Error reported from Cluster DATA #2 : String, 17 bytes DWH_DB2_HA_domain DATA #3 : String, 0 bytes Object not dumped: Address: 0x0000000000000000 Size: 0 Reason: Address is NULL 2013-02-26-01.34.46.380356+060 E26011857E436 LEVEL: Error PID : 7653 TID : 140737352337184 PROC : db2havend (db2ha) INSTANCE: db2inst1 NODE : 000 HOSTNAME: myHost2 FUNCTION: DB2 UDB, high avail services, db2haGetObjectState, probe:4809 DATA #1 : String, 48 bytes getting mapResourceNameToHandle failed, exiting DATA #2 : String, 17 bytes DWH_DB2_HA_domain DATA #3 : unsigned integer, 4 bytes 1 2013-02-26-01.34.47.381106+060 I26012294E419 LEVEL: Error PID : 7653 TID : 140737352337184 PROC : db2havend (db2ha) INSTANCE: db2inst1 NODE : 000 HOSTNAME: myHost2 FUNCTION: DB2 UDB, high avail services, getLastErrMsg, probe:19773 DATA #1 : signed integer, 4 bytes 3 DATA #2 : String, 84 bytes Line # : 19773--- 2610-603 The session with the RMC subsystem has been interrupted. 2013-02-26-01.34.47.381514+060 E26012714E599 LEVEL: Error PID : 7653 TID : 140737352337184 PROC : db2havend (db2ha) INSTANCE: db2inst1 NODE : 000 HOSTNAME: myHost2 FUNCTION: DB2 UDB, high avail services, db2haMapResourceNameToHandle, probe:100 MESSAGE : Look up for the name of resource failed. DATA #1 : DB2HA Cluster Error Code, PD_TYPE_DB2HA_CLUSTER_ERROR_CODE, 4 bytes error: Error reported from Cluster DATA #2 : String, 17 bytes DWH_DB2_HA_domain DATA #3 : String, 0 bytes Object not dumped: Address: 0x0000000000000000 Size: 0 Reason: Address is NULL 2013-02-26-01.34.47.381887+060 E26013314E436 LEVEL: Error PID : 7653 TID : 140737352337184 PROC : db2havend (db2ha) INSTANCE: db2inst1 NODE : 000 HOSTNAME: myHost2 FUNCTION: DB2 UDB, high avail services, db2haGetObjectState, probe:4809 DATA #1 : String, 48 bytes getting mapResourceNameToHandle failed, exiting DATA #2 : String, 17 bytes DWH_DB2_HA_domain DATA #3 : unsigned integer, 4 bytes 1 | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * Users configuring domain via db2haicu * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to version 10.1 fix pack 3 * **************************************************************** | |
Local-Fix: | |
N/A | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
Lösung | |
First fixed in version 10.1 fix pack 3 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 27.02.2013 27.09.2013 27.09.2013 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.3 | |
10.1.0.3 |