IBM Support

IC76308: LOCK TIMEOUT LOG FILES STOP BEING GENERATED WHEN DIAGPATH IS SPLIT PER HOSTNAME AND/OR HOSTNAME/NODENAME.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If lock timeout capturing is being done (db2set
    DB2_CAPTURE_LOCKTIMEOUT=YES) and lock timeout issues occur, DB2
    generates lock timeout reports in diagnostics path defined by
    DIAGPATH dbm cfg parameter which have the following format:
    
    db2locktimeout.par.AGENTID.yyyy-mm-dd-hh-mm-ss, where
    
    par is the database partition number. In non-partitioned
    database environments, par is set to 0.
    AGENTID is the agent ID.
    yyyy-mm-dd-hh-mm-ss is the time stamp, consisting of the year,
    month, day, hour, minute, and second.
    
    However, when diagnostics path is split per hostname and/or
    hostname/nodename on DPF environments, then lock timeout reports
    stop being generated thus no lock timeout information is logged.
    
    EX:
    
    db2 update dbm cfg using DIAGPATH '"<path> $h"'
    
    or
    
    db2 update dbm cfg using DIAGPATH '"<path> $h$n"'
    
    
    When lock timeout occurs, and db2 can not write to lock timeout
    report file due to having $h or $h$n in DIAGPATH value, the
    following error is logged in  db2diag.log:
    
    2011-05-03-16.45.40.808485-240 I235231A523        LEVEL: Warning
    PID     : 2199742              TID  : 5428        PROC : db2sysc
    1
    INSTANCE: db2inst1                 NODE : 001         DB   :
    SAMPLE
    APPHDL  : 0-93                 APPID: *N0.anik.110503204458
    AUTHID  : db2inst1 EDUID   : 5428                 EDUNAME:
    db2agntp (SAMPLE) 1
    FUNCTION: DB2 UDB, lock manager, sqlpLockTimeoutInfo, probe:70
    MESSAGE : ZRC=0x870F0011=-2029060079=SQLO_PATH "an invalid path"
    
    DIA8514C An invalid file path, "", was specified.
    
    With this APAR fix, the lock timeout reports will be generated
    and logged.
    

Local fix

  • As a temporary workaround before the fix for this APAR is
    applied, stop using splitting the diag path perf hostname or
    hostname/nodename.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users using split DIAGPATH per hostname and/or               *
    * hostname/nodename                                            *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * LOCK TIMEOUT LOG FILES STOP BEING GENERATED WHEN DIAGPATH IS *
    * SPLIT PER HOSTNAME AND/OR HOSTNAME/NODENAME.                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply DB2 V97 FP5                                            *
    ****************************************************************
    

Problem conclusion

  • The Problem was first fixed in db2 v97 fp5.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC76308

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-05-10

  • Closed date

    2011-12-22

  • Last modified date

    2011-12-22

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

    IC76194

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

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSN

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.7","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
22 December 2011