IBM Support

IC78465: ROLLFORWARD FROM LOGS AFTER TRUNCATE ON XML TABLE MAY FAIL WITH DB MARKED BAD

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • While doing a Restore->Rollforward from logs, if there is a
    Truncate on XML Table as part of those logs a user may encounter
    Database MARKED BAD due to missing XML Dictionary.
    
    This will typically result in similar db2diag info (below) if
    the logs which we are recovering from include the TRUNCATE log
    record and either an INSERT, IMPORT, LOAD record which was
    executed afterwards.
    
    
    2011-02-02-00.14.59.911000+540 I5597490F522       LEVEL: Severe
    PID     : 4264                 TID  : 4680        PROC :
    db2syscs.exe
    INSTANCE: DB2                  NODE : 000         DB   : SAMPLE
    APPHDL  : 0-4025               APPID: *LOCAL.DB2.101031134609
    EDUID   : 4680                 EDUNAME: db2redow (SAMPLE)
    FUNCTION: DB2 UDB, Common Storage Layer,
    sqldcsl_redoMultiRowInsert,
    probe:89
    MESSAGE : Update count (probeID = current update count)
    incorrect duirng
    redo!
    DATA #1 : unsigned integer, 4 bytes
    0
    
    2011-02-02-00.15.00.004000+540 I5600304F500       LEVEL: Severe
    
    PID     : 4264                 TID  : 4680        PROC :
    db2syscs.exe
    INSTANCE: DB2                  NODE : 000         DB   : SAMPLE
    
    APPHDL  : 0-4025               APPID: *LOCAL.DB2.101031134609
    
    EDUID   : 4680                 EDUNAME: db2redow (SAMPLE)
    
    FUNCTION: DB2 UDB, trace services, sqlt_logerr_string (secondary
    logging
    fu, probe:0
    
    MESSAGE : SQLD_TCB:
    
    DATA #1 : String, 39 bytes
    
    Perm Table(3:12)=TBSPACEID=3.TABLEID=12
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * DB2 LUW V97 and Newer Releases                               *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See APAR Description                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to v97 FP5 or newer.                                 *
    ****************************************************************
    

Problem conclusion

  • Fix provided in v97 FP5 and newer releases.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC78465

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

  • Closed date

    2012-01-17

  • Last modified date

    2012-01-17

  • 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



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IC78465

Modified date: 17 January 2012