IC81096: ROLLFORWARD FAILS - SQL1042, CRASH RECOVERY FAILS - DIA8709E, or SMS TABLE - SQL1236N

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as fixed if next.

Error description

  • Rollforward fails with the following errors:
    
    2012-01-30-02.44.56.187000-300 I14045169F575      LEVEL: Error
    PID     : 4640                 TID  : 6240        PROC :
    db2syscs.exe
    INSTANCE: DB2                  NODE : 000         DB   : TEST
    APPHDL  : 0-7                  APPID: *LOCAL.DB2.120130074445
    AUTHID  : TEST
    EDUID   : 6240                 EDUNAME: db2agent (TEST)
    FUNCTION: DB2 UDB, recovery manager, sqlpresr, probe:640
    DATA #1 : String, 142 bytes
    Crash recovery failed with rc -2080243703
    LowtranLSN 0000062005C2C320 MinbuffLSN 0000062005C2C320
    Recovery started on log file S0345262.LOG.
    .
    .
    .
    .
    2012-01-30-02.44.56.187000-300 E14046803F497      LEVEL: Error
    PID     : 4640                 TID  : 6240        PROC :
    db2syscs.exe
    INSTANCE: DB2                  NODE : 000         DB   : TEST
    APPHDL  : 0-7                  APPID: *LOCAL.DB2.120130074445
    AUTHID  : TEST
    EDUID   : 6240                 EDUNAME: db2agent (TEST)
    FUNCTION: DB2 UDB, base sys utilities,
    sqeLocalDatabase::RecoverDatabase, probe:60
    MESSAGE : ADM1532E  Crash recovery has failed with SQLCODE
    "-1042".
    .
    .
    .
    .
    2012-01-30-03.21.06.437000-300 I14105503F563      LEVEL: Error
    PID     : 4444                 TID  : 8356        PROC :
    db2syscs.exe
    INSTANCE: DB2                  NODE : 000         DB   : TEST
    APPHDL  : 0-7                  APPID: *LOCAL.DB2.120130082047
    AUTHID  : TEST
    EDUID   : 8356                 EDUNAME: db2redow (TEST)
    FUNCTION: DB2 UDB, Common Trace API, sqlbfix, probe:621
    MESSAGE : ZRC=0x84020009=-2080243703=SQLB_RC_PG_NUM_ERR
              "Page number exceeds max -8100"
              DIA8709E Segmented table page number was too high.
    
    Reference: v9.5 APAR IZ35046
    
    * * * Additional symptom
    
    Inserting data into a SMS table can generate a SQL1236N.
    Upgrading to avoid this APAR, the new error that will be
    returned will be SQL0659N, which is the correct error.
    

Local fix

  • Roll Forward to a point in time before the transaction log entry
    is replayed.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * During CRASH RECOVERY fails with DB2DIAG.LOG entry DIA8709E. *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 LUW version 97fp6                             *
    ****************************************************************
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IC81096

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-01-30

  • Closed date

    2012-06-13

  • Last modified date

    2013-03-28

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

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

    IC84300

Fix information

Applicable component levels

  • R970 PSN

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

DB2 for Linux, UNIX and Windows

Software version:

9.7

Reference #:

IC81096

Modified date:

2013-03-28

Translate my page

Machine Translation

Content navigation