DB2 FOR LUW / DB2FORLUW / A50 - DB2

If a locking event monitor is defined to be UNFORMATTED EVENT 
TABLE (rather than TABLE) and EVMON_FORMAT_UE_TO_TABLES is used 
to move the unformatted data into relational tables, NULL values 
are used for columns where data is not available. 
 
However a locking event monitor defined to be TABLE will use 0 
values for numeric columns, empty strings for character columns 
and a value of "0000-00-00-00.00.00.000000" for timestamp 
columns.  These timestamp column values can cause issues when 
exporting / importing the data from the event monitor table. 
 
This APAR modifies locking TABLE event monitor processing to use 
NULL values when data is not available (that is, so that it's 
data matches the data produced by EVMON_FORMAT_UE_TO_TABLES when 
run against a locking UNFORMATTED EVENT TABLE event monitor 
 
Affected columns in the lock_participants table are: 
- lock_current_mode 
- lock_mode_requested 
- lock_mode 
- lock_count 
- lock_hold_count 
- lock_rriid 
- lock_status 
- table_file_id 
- threshold_id 
- lock_wait_start_time 
- lock_wait_end_time 
- participant_no_holding_lk 
- object_requested 
- lock_name 
- lock_object_type 
- lock_object_type_id 
- lock_attributes 
- lock_release_flags 
- table_name 
- table_schema 
- tablespace_name 
- threshold_name 
- queued_agents 
- queue_start_time 
 
Affected columns in the lock_participant_activities table are: 
- stmt_first_use_time 
- stmt_last_use_tim

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 and Fix Pack 3.                  * 
* Run the EVMON_UPGRADE_TABLES stored procedure to update the  * 
* locking                                                      * 
* event monitor's target tables.                               * 
****************************************************************

DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
 DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
 

Problem was first fixed in DB2 Version 10.5 and Fix Pack 3

not known / see Local fix

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

27.08.2013
27.02.2014
27.02.2014