DB2 - Problem description
Problem IC69912 | Status: Closed |
THE DB2DIAG.LOG LOGS "PARTIAL EVENT" MESSAGES EVEN WHEN LOG_PARTIAL_EVENTS ISN'T SPECIFIED BY EVMON_FORMAT_UE_TO_XML. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
The following message is logged in the db2diag.log even when calling EVMON_FORMAT_UE_TO_XML without the LOG_PARTIAL_EVENTS option. 2010-07-07-12.13.14.137650-300 E10870925A485 LEVEL: Warning PID : 1324962 TID : 99905 PROC : db2sysc INSTANCE: db2inst1 NODE : 000 DB : SAMPLE EDUID : 99905 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, database application extension for syste, monLockEventFormatter::LogPartialEvents, probe:908 MESSAGE : Partial (incomplete) event with XMLID 'db2LockEvent_2462_LOCKWAIT_2010-07-07-12.10.48.942788_0' exists. You will see the following message, also. SQL0443N Routine "EVMON_FORMAT_UE_TO_XML" (specific name "") has returned an error SQLSTATE with diagnostic text "Partial events exist. Check the db2diag.log". SQLSTATE=38553 This issue occurs in the UOW event monitor and the locking event monitor. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Problem Description above. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 Fix Pack 4. * **************************************************************** | |
Local Fix: | |
N/A | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows | |
Solution | |
First fixed in Version 9.7 Fix Pack 4. | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC72752 IC91695 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 14.07.2010 29.04.2011 29.04.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP4 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.4 |