IBM Support

IC74923: db2dart does not print out sufficient details when it encounters a non-corruption read errors.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Currently, db2dart only returns general error message when it
    encounters a non-corruption related error i.e.
    
      Error: Unable to read pool page XXXXXXX, object page XXXX,
    from pool X,
      Error: parent pool X, object ID X, object type Index.
      Error: extent map anchor page of object is XX.
    
    
    For example, db2dart could encounter a non-corruption error due
    to insufficient system resource (i.e. SQLO_NORES).
    
    db2diag.log will return the following entry, e.g.
    
    XXXX-0X-XX-XX.XX.XX.XXX000-XXX XXXXXXXXXXXXX      LEVEL: Error
    PID     : XXXX                 TID  : XXXX        PROC : db2dart
    INSTANCE: DB2                  NODE : 000
    FUNCTION: DB2 UDB, buffer pool services, sqlbFixDataEMP,
    probe:820
    MESSAGE : ZRC=0x870F00F2=-2029059854=SQLO_NORES
              "no resources to create process or thread"
    
    and db2dart returns the following errors, e.g.
    
      Data inspection phase start. Data obj: XXX  In pool: X
      Error: Unable to determine pool relative page number for obj
    rel page 0 (Obj ID:XXX, Pool ID:X)
      Error: Unable to read pool page XXXXXXXXXX, object page X,
    from pool X,
      Error: parent pool X, object ID XXX, object type Data.
      Error: extent map anchor page of object is XXXXXX.
      Error: This object page does not exist.
    
    Instead of returning a general error message, db2dart will
    include the return code (RC) of the error (in hex value).
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * db2dart users.                                               *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Without this APAR, customer is exposed to the issue as       *
    * described in the "ERROR DESCRIPTION" section.                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 Version 9.7, Fixpack 5.                       *
    ****************************************************************
    

Problem conclusion

  • First fixed in DB2 Version 9.7, Fixpack 5.
    

Temporary fix

  • n/a
    

Comments

APAR Information

  • APAR number

    IC74923

  • 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-03-08

  • Closed date

    2012-01-03

  • Last modified date

    2012-01-03

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

    IC74607

  • 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 PSY

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IC74923

Modified date: 03 January 2012