|
Problem IC89693
|
Status: Geschlossen |
After executing "DB2STOP CF <ID>" command, a severe level message is printed in diaglog for rocmCAGetServerUDF |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problembeschreibung: |
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-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* DB2 UDB Version 10.1 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Version 10.1 FixPack 3. *
**************************************************************** |
| Local-Fix: |
|
| verfügbare FixPacks: |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Lösung |
Problem was first fixed in DB2 UDB Version 10.1 FixPack 3. |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 22.01.2013
01.10.2013
01.10.2013 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
