DB2 FOR LUW / DB2FORLUW / A10 - DB2

If partial or incomplete events exist in an event monitor 
Unformatted Event (UE) table, a message (SQL443N) is returned 
when EVMON_FORMAT_UE_TO_XML is run, whether or not the 
LOG_PARTIAL_EVENTS option is specified. Incomplete events can 
occur when an agent finishes processing before the entire event 
record can be inserted in to the UE table. This situation can 
sometimes arise with LOCKING or UNIT OF WORK event monitors, 
particularly in partitioned database environments. 
 
Whenever EVMON_FORMAT_UE_TO_XML is run directly or if the 
EVMON_FORMAT_UE_TO_TABLES procedure is called (which runs 
EVMON_FORMAT_UE_TO_XML) and partial events are detected, the 
following db2diag.log warning probe is written out and may cause 
unwanted clutter in the db2diag.log: 
 
2012-04-20-08.39.56.284237-300 E1808342A856       LEVEL: Warning 
PID     : 43253948             TID  : 17550       PROC : db2sysc 
0 
INSTANCE: <inst-name>             NODE : 000         DB   : 
<db-name> 
APPHDL  : 0-20978              APPID: <app-id> 
AUTHID  : <auth-id> 
EDUID   : 17550                EDUNAME: db2agent (<db-name>) 0 
FUNCTION: DB2 UDB, runtime interpreter, 
sqlriTrustedTruncateTokensUserSqlState, probe:100 
DATA #1 : signed integer, 4 bytes 
-443 
DATA #2 : String with size, 5 bytes 
38553 
DATA #3 : String with size, 30 bytes 
SYSPROC.EVMON_FORMAT_UE_TO_XML 
DATA #4 : String with size, 22 bytes 
EVMON_FORMAT_UE_TO_XML 
DATA #5 : String with size, 21 bytes 
Partial events exist. 
DATA #6 : signed integer, 4 bytes 
68 
DATA #7 : signed integer, 4 bytes 
22 
DATA #8 : signed integer, 4 bytes 
22 
DATA #9 : signed integer, 4 bytes 
21

**************************************************************** 
* USERS AFFECTED:                                              * 
* Users using EVMON_FORMAT_UE_TO_XML table function            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* This  messages  showing up in db2diag.log  due the  issue    * 
* described in  Error Description section are not incorrect.   * 
* But,  those unnecessarily increase the size of the           * 
* db2diag.log.   As those messages are not really  needed to   * 
* be logged in the db2diag.log  the similar message logging    * 
* is removed as part of this APAR  fix                         * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 2 or higher to avoid    * 
* experiencing this issue.                                     * 
****************************************************************

DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
 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
 

First fixed in DB2 Version 10.1 Fix Pack 2

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

28.11.2012
31.12.2012
31.12.2012