IBM Support

IC69295: SQL0964 LOGFULL DURING INDEX REBUILD IF DB CONFIG INDEXREC RESTART SET TO SYSTEM

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Generally, a firstly connecting agent (in this case it is STMM,
    db2stmm) reads SYSIBM.SYSVERSIONS and it may read an index of
    SYSIBM.SYSVERSIONS.  At that timing, if the index is marked as
    needed to be rebuilt, will do so and writes logical log records.
     But DB2 does not make a "commit" at the end so it may cause
    SQL0964 Logfull.
    
    Here is an example problem reproducible scenario:
    =================================================
    mkdir /backup
    mkdir /logs
    mkdir /DB
    
    db2start
    db2 drop db sample
    db2sampl
    db2 connect to sample
    db2 update db cfg for sample using LOGARCHMETH1 disk:/logs
    db2 terminate
    db2 backup database sample to /dev/null
    
    ### test
    
    db2 deactivate db sample
    db2 backup db sample to /backup compress
    db2 activate db sample
    db2 connect to sample
    db2 reorg table sysibm.sysversions use tempspace1
    db2 terminate
    db2 deactivate db sample
    db2 restore db sample from /backup to /DB without prompting
    db2 "rollforward db sample to end of logs and stop"
    db2 activate db sample
    
    ### now look at the db by follows
    
    db2 list applications show detail
    db2 get snapshot for all databases global
    
    ### Appl id holding the oldest transaction = stmm
    =================================================
    
    In the above scenario, "reorg table sysibm.sysversions" may need
    to rebuild an index.  If you restore the database with a backup
    image which is taken before the "reorg table" and rollforward to
    end of logs, DB2 should rebuild the index.  There are two ways
    to rebuilt it, 1) write a rebuild index required logcal log, set
    the index as invalid state at rollforwad and then rebuld it when
    an agent finds the index is needed to rebuild.
    2) write all index rebuld logical logs then apply and reply all
    those logs to rebuld the index.  Default db cfg LOGINDEXBUILD
    OFF setting works as 1).  Based on these, users may work around
    by setting LOGINDEXBUILD ON.
    
    Potentially below agents may cause this problem as same as STMM:
    ABP task daemon, WLM stats collector daemon, event monitors,
    online reorg, redistribute, HADR.
    We will fix as well.
    

Local fix

  • Users may work around by:
    db2 update db cfg for DBNAME using LOGINDEXBUILD ON
    
    and
    
    (
      db2 update db cfg for DBNAME using INDEXREC RESTART
    or
     (db2 update db cfg for DBNAME using INDEXREC SYSTEM
    
      and
    
      db2 update dbm cfg using INDEXREC RESTART )
    )
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * DB2 UDB Version 9.7                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error description field for more information.            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Version 9.7 FixPack 4.                            *
    ****************************************************************
    

Problem conclusion

  • Problem was first fixed in DB2 UDB Version 9.7 FixPack 4.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC69295

  • 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

    2010-06-16

  • Closed date

    2011-05-03

  • Last modified date

    2011-05-03

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

    IC69258

  • 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

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

Document Information

Modified date:
03 May 2011