IBM Support

IT17287: A LOCKING EVENT MONITOR CAN INCORRECTLY CAPTURE STATIC STMT TEXTAND REPORT INCORRECT NUMBER OF INPUT VARIABLES

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When a LOCKING event monitor captures events that involve STATIC
    sql, the stmt_text may not be properly captured.
    Furthermore, when that statement includes parameter markers the
    event monitor output can show a mismatching number of parameter
    markers to the stmt text.
    
    For example here is an output snippet from the output of the
    db2evmonfmt tool illustrating the problem:
    
    ...
    Stmt text          : declare TESTCURSOR cursor for select
    t1.COL1, t1.COL2, t1.COL3, t1.TS from MYTAB t1 where COL2 =
    :H00058 and COL3 = :H00059 order by t1.COL1 ASC
    Input variable 1
    Type              : INTEGER
    Data              : 3
    Reopt             : no
    Null              : no
    Input variable 2
    Type              : VARCHAR
    Data              : 2015-12-11
    Reopt             : no
    Null              : no
    Input variable 3
    Type              : INTEGER
    Data              : 7
    Reopt             : no
    Null              : no
    Input variable 4
    Type              : INTEGER
    Data              : 4
    Reopt             : no
    Null              : no
    ...
    
    In the snippet above we see that statement has 2 input
    variables, while later on we list 4.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 10.5 Fix Pack 9 or higher                     *
    ****************************************************************
    

Problem conclusion

  • First fixed in Db2 10.5 Fix Pack 9
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT17287

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    A50

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-09-30

  • Closed date

    2017-09-29

  • Last modified date

    2017-09-29

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

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

    IT22606

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.5","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
29 June 2020