DB2 - Problem description
Problem IC89693 | Status: Closed |
After executing "DB2STOP CF <ID>" command, a severe level message is printed in diaglog for rocmCAGetServerUDF | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
While "db2stop cf <ID>", a Severe level message comes from rocmCAGetServerUDF but it should be info level. -------------- "date" I4207A2098 LEVEL: Severe PID : "process pid" TID : 1 PROC : db2stop INSTANCE: "instance name" NODE : "node number" HOSTNAME: "host name" EDUID : 1 FUNCTION: DB2 UDB, high avail services, rocmCAGetServerUDF, probe:1714 RETCODE : ZRC=0x8273019A=-2106392166=HA_ZRC_PROCESS_NOT_FOUND "Process was not found." DATA #1 : String, 7 bytes pmninst DATA #2 : Database Partition Number, PD_TYPE_NODE, 2 bytes "CF #" DATA #3 : ROCM CF Server User Data Field, PD_TYPE_ROCM_CA_SERVER_UDF, 32 bytes CA Server UDF->status = INITIALIZED CA Server UDF->status = PRIMARY INITIALIZED CA Server UDF->caSequenceNumber = integer CA Server UDF->primarySequenceNumber = integer ... | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * DB2 UDB Version 10.1 * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Version 10.1 FixPack 3. * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in DB2 UDB Version 10.1 FixPack 3. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 22.01.2013 01.10.2013 01.10.2013 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.3 | |
10.1.0.3 |