IBM Support

IT18449: SHOULD NOT DUMP "PDDIAGREADFROMFILEINTOBUFFERBS, PROBE:25" WITH DIAGLEVEL 3

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Can see a new message that is dumped in db2diag.log every time
    PD_GET_DIAG_HIST() function is called:
    
    2016-06-16-14.31.29.896451+120 I16404886A861        LEVEL: Info
    PID     : 10289404             TID : 38609          PROC :
    db2sysc 0
    INSTANCE: db2inst1               NODE : 000           DB   :
    SAMPLE
    APPHDL  : 0-55555              APPID:
    *LOCAL.db2inst1.160616122823
    AUTHID  : DB2INST1               HOSTNAME: db2host
    EDUID   : 38609                EDUNAME: db2agent (SAMPLE) 0
    FUNCTION: DB2 UDB, RAS/PD component,
    pdDiagReadFromFileIntoBufferBS, probe:25
    MESSAGE : Initial status when binary serach :
    DATA #1 : unsigned integer, 8 bytes
    16404885
    DATA #2 : String, 53 bytes
    2016-06-15-00.00.00.000000:2016-06-16-00.00.00.000000
    DATA #3 : String, 26 bytes
    2016-06-16-00.00.00.000000
    DATA #4 : String, 0 bytes
    Object not dumped: Address: 0x000000012B28F5D4 Size: 0 Reason:
    Zero-length data
    DATA #5 : String, 53 bytes
    2016-06-15-00.00.00.000000:2016-06-16-00.00.00.000000
    
    This was intended as a serviceability request, but you can see
    these messages too many times and ask that we only log it with
    DIAGLEVEL 4.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 11.1 Mod 2 Fix Pack 2 or higher               *
    ****************************************************************
    

Problem conclusion

  • First fixed in DB2 11.1 Mod 2 Fix Pack 2
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT18449

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-12-16

  • Closed date

    2017-06-23

  • Last modified date

    2017-06-23

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

    IT16686

  • 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

[{"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":"11.1","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
29 June 2020