IC92831: LOCKING TABLE EVENT LOCKING MONITOR SHOULD USE NULL VALUES WHEN DATA IS UNAVAILABLE

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • 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
    

Local fix

Problem summary

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

Problem conclusion

  • Problem was first fixed in DB2 Version 10.1 and Fix Pack 3
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC92831

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-06-05

  • Closed date

    2013-10-18

  • Last modified date

    2013-10-18

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    IC95456

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • RA10 PSN

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

DB2 for Linux, UNIX and Windows

Software version:

10.1

Reference #:

IC92831

Modified date:

2013-10-18

Translate my page

Machine Translation

Content navigation