IBM Support

IC81707: RESTORE WITH TRANSPORT MAY CAUSE INSTANCE TO FAIL

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A restore with transport may cause the target database to trap
    if the target database's current log file number is more 256
    logs behind the current log file number of the source database.
    In the db2diag.log, you may see a message similar to this:
    
    2012-02-22-15.34.52.852044-300 I3857168A999      LEVEL: Error
    PID    : 18481336            TID  : 3232        PROC : db2sysc
    INSTANCE: db2inst1        NODE : 000
    EDUID  : 3232                EDUNAME: db2logts (SAMPLE)
    FUNCTION: DB2 UDB, recovery manager,
    sqlpMarkDirtyPoolsInExtents, probe:1054
    MESSAGE : infoForLog:
    DATA #1 : Hexdump, 120 bytes
    0x0A000200100299E8 : 0000 0137 0000 0000 0000 0001 3932 8001
    ...7........92..
    0x0A000200100299F8 : 0000 0001 3A33 C000 0000 0001 4F44 FAE4
    ....:3......OD..
    0x0A00020010029A08 : 4F45 150C 0000 0000 0000 0000 0167 0000
    OE...........g..
    0x0A00020010029A18 : 1002 9A18 0000 0000 0000 0000 0000 0000
    ................
    0x0A00020010029A28 : 0000 0000 0000 0000 0000 0000 0000 0000
    ................
    0x0A00020010029A38 : 0000 0000 0000 0000 0000 0000 0000 0000
    ................
    0x0A00020010029A48 : 0000 0000 0000 0000 0000 0000 0000 0000
    ................
    0x0A00020010029A58 : 0000 0000 0000 0000
    ........
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * User of RESTORE WITH TRANSPORT                               *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * A restore with transport may cause the target database to    *
    * trap                                                         *
    * if the target database's current log file number is more 256 *
    * logs behind the current log file number of the source        *
    * database.                                                    *
    * In the db2diag.log, you may see a message similar to this:   *
    *                                                              *
    * 2012-02-22-15.34.52.852044-300 I3857168A999      LEVEL:      *
    * Error                                                        *
    * PID    : 18481336            TID  : 3232        PROC :       *
    * db2sysc                                                      *
    * INSTANCE: db2inst1        NODE : 000                         *
    * EDUID  : 3232                EDUNAME: db2logts (SAMPLE)      *
    * FUNCTION: DB2 UDB, recovery manager,                         *
    * sqlpMarkDirtyPoolsInExtents, probe:1054                      *
    * MESSAGE : infoForLog:                                        *
    * DATA #1 : Hexdump, 120 bytes                                 *
    * 0x0A000200100299E8 : 0000 0137 0000 0000 0000 0001 3932 8001 *
    * ...7........92..                                             *
    * 0x0A000200100299F8 : 0000 0001 3A33 C000 0000 0001 4F44 FAE4 *
    * ....:3......OD..                                             *
    * 0x0A00020010029A08 : 4F45 150C 0000 0000 0000 0000 0167 0000 *
    * OE...........g..                                             *
    * 0x0A00020010029A18 : 1002 9A18 0000 0000 0000 0000 0000 0000 *
    * ................                                             *
    * 0x0A00020010029A28 : 0000 0000 0000 0000 0000 0000 0000 0000 *
    * ................                                             *
    * 0x0A00020010029A38 : 0000 0000 0000 0000 0000 0000 0000 0000 *
    * ................                                             *
    * 0x0A00020010029A48 : 0000 0000 0000 0000 0000 0000 0000 0000 *
    * ................                                             *
    * 0x0A00020010029A58 : 0000 0000 0000 0000                     *
    * ........                                                     *
    * Error Description                                            *
    * none                                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply DB2 Versoin 9.7 Fixpack 6                              *
    ****************************************************************
    

Problem conclusion

  • Apply DB2 Versoin 9.7 Fixpack 6
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC81707

  • 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

    2012-02-28

  • Closed date

    2012-06-05

  • Last modified date

    2012-06-05

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

       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:
05 June 2012