IBM Support

IC73936: SEVERE SQLDREADTABLEINFO DB2DIAG.LOG FOR INTERRUPTED QUERY.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • After a query was interrupted, the db2diag.log may report :
    
    2011-01-13-04.40.25.716609+000 I1286353A7696      LEVEL: Severe
    PID     : 29229284             TID  : 22296       PROC : db2sysc
    2
    INSTANCE: db2inst1          NODE : 002         DB   : SAMPLE
    APPHDL  : 0-19566            APPID:
    9.122.128.160.57849.101213022
    AUTHID  : db2inst1
    EDUID   : 22296                EDUNAME: db2agntp (SAMPLE) 2
    FUNCTION: DB2 UDB, data management, sqldReadTableInfo,
    probe:10089
    MESSAGE : Fail positioning record within the page
    DATA #1 : Hexdump, 1424 bytes
    0x0700000115BFC720 : 0000 0000 0000 0000 0000 0000 0000 0000
    ................
    0x0700000115BFC730 : 0000 0000 2010 0000 0000 0000 0000 0000
    .... ...........
    0x0700000115BFC740 : 0000 0000 0000 0000 0000 0000 0000 0000
    ................
    0x0700000115BFC750 : 0000 0000 0000 0000 0000 0000 0000 0000
    ................
    ...
    
    The message is misleading as it does not indicate a serious
    problem and only appears if a statement is accessing a table and
    
    is interrupted whilst doing so. The problem is timing dependent
    and should not be seen very regularly.
    The db2diag.log message is the only symptom, as the interrupt is
    further handled correctly.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * all                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Misleading and incorrect severe error message raised in the  *
    * db2diag.log coming from function SQLDREADTABLEINFO           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade DB2 to V9.7 fixpak 4                                 *
    ****************************************************************
    

Problem conclusion

  • This problem was first fixed in V9.7 Fixpak 4
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC73936

  • 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-01-18

  • Closed date

    2011-05-24

  • Last modified date

    2011-05-24

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

  • 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

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.7"}]

Document Information

Modified date:
17 September 2021