IBM Support

LI74528: Possible tablespace file corruption during backup / restore when DB2 is unable to create containers in original path

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • <scenario #1>
    After restoring the database from backup, rollforward query
    status could fail with SQL0980 disk error and db2diag.log shows
    SQLB_CSUM "Bad Page, Checksum" error
    
    For example,
    
    db2 rollforward db PROD query status
    
    SQL0980C  A disk error occurred.  Subsequent SQL statements
    cannot be processed.  SQLSTATE=58005
    
    db2diag.log entry -
    
    2009-xx-xx-xx.xx.xx.xxxxxx-xxx xxxxxxxxxxxx       LEVEL: Error
    PID     : xxxxxx               TID  : 1           PROC :
    db2agent (PROD) 0
    INSTANCE: xxxxxxxx             NODE : 000         DB   : PROD
    APPHDL  : 0-473                APPID:
    *LOCAL.xxxxxxxx.xxxxxxxxxxxx
    FUNCTION: DB2 UDB, buffer pool services, sqlbReadPoolTable,
    probe:910
    RETCODE : ZRC=0x86020019=-2046689255=SQLB_CSUM "Bad Page,
    Checksum
    
    If restoring the same database backup the second time and issue
    the rollforward query status again, it will complete
    successfully.
    
    <scenario #2>
    If users changes permissions to /tmp readable only for instance
    owner, backup of database would fail with SQL2048 Error and
    corrupt SQLSPCS file. This would result in SQL0980C error while
    connecting to database and users will not be able to connect to
    database.
    
    Steps to recreate issue :
    ***********************************************************
    1. db2 "create database TEST"
    
    2. db2 connect to TEST
    
    3. As root ,CHANGE permissions ON /tmp [root@lenexa /]# chmod
    000 tmp
     d---------   26 root root         4096 Aug 27 11:40 tmp
    4. db2 backup db TEST
        SQL2048N  An error occurred while accessing object "1".
    Reason code: "6".
    
    5. db2 connect to TEST
        SQL0980C  A disk error occurred.  Subsequent SQL statements
    cannot be processed.  SQLSTATE=58005
    

Local fix

  • <for scenario #1>
    The workaround is to restore the database again and rollforward
    the second time.
    
    <for scenario #2>
    Contact db2 technical support
    

Problem summary

  • This will be fixed in V9.1 FP7 and higher.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    LI74528

  • Reported component name

    DB2 UDE ESE LIN

  • Reported component ID

    5765F4104

  • Reported release

    820

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-05-21

  • Closed date

    2009-05-21

  • Last modified date

    2009-05-26

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

    LI73822

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

Fix information

Applicable component levels

  • R910 PSY

       UP

  • R950 PSY

       UP

  • R810 PSN

       UP

  • R820 PSN

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"820","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
26 May 2009