IBM Support

IT30189: UPGRADE DB MAY CORRUPT SQLSPCS FILES AND RESULT IN CHECKSUM ERROR WHEN DB IS ACTIVATED

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • db2 upgrade db completed successfully but activation of the
    database afterward failed with the following message:
    SQL0980C  A disk error occurred.  Subsequent SQL statements
    cannot be processed.  SQLSTATE=58005
    
    During the upgrade, a container name in SPCS files is compressed
    from an
    absolute path to a relative path but the 'Container memory used'
    is not updated accordingly, the wrong size is then written to
    disk into SQLSPCS.1 and SQLSPCS.2 files, it results in bad
    container checksum calculated when the db is activated
    afterward.
    Note that the absolute path has to be in /db
    path/your_instance/NODExxxx/SQLxxxxx to trigger this problem.
    
    Errors will be similar to this in db2diag.log:
    
    FUNCTION: DB2 UDB, buffer pool services, sqlbReadPoolOneFile,
    probe:1681
    MESSAGE : ZRC=0x86020019=-2046689255=SQLB_CSUM "Bad Page,
    Checksum Error"
             DIA8426C A invalid page checksum was found for page "".
    DATA #1 : Pool control block, PD_TYPE_SQLB_POOL_CB, 54160 bytes
    name:                  USERSPACE1
    poolID:                                 2
    flags:                                101
    flags2:                                20
    local flags:                            0
    

Local fix

  • Asking Db2 support to format SPCS files, verify it is the APAR
    and patch the container name using the absolute path.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher                *
    ****************************************************************
    

Problem conclusion

  • First fixed in Db2 11.1 Mod 4 Fixpack 5
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT30189

  • 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

    2019-09-04

  • Closed date

    2020-01-16

  • Last modified date

    2020-01-16

  • 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

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

Document Information

Modified date:
16 January 2020