IBM Support

IC68251: ROLLFORWARD FAILS WITH SQL1265N "NOT ASSOCIATED WITH THE CURRENT LOG SEQUENCE" AFTER DB2INIDB

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • The problem is the rollforward command fails with SQL1265N
    "not associated with the current log sequence" error even if the
    1st rollforward command completes successfully with the same
    database image after archive log and db2inidb.
    
      The following is a sample reproduction flow
    
      1.  setup a database with softmax=100, newlogpath, and
    logarchmeth1
      2.  backup database
      3.  activate db
      4.  connect to db and issue some transactions, then terminate
      5.  archive log several times
      6.  connect to db and set write suspend
      7.  take on-line database snapshot copy by cp command or
    flashcopy
      8.  set write resume and terminate
    
      9.  deactivate db and db2stop
      10. restore the database image by cp command or flashcopy
      11. db2start and db2inidb as mirror
      12. rollforward db to end of logs and stop
      13. connect to db and issue some transactions, then terminate
    
      14. db2stop
      15. restore the same database image by cp command or flashcopy
      16. db2start and db2inidb as mirror
      17. rollforward db to end of logs and stop ==> SQL1265N error
    
      Error SQL1265N may occur the 2nd RFWD command, but it should
    be successful.
    

Local fix

  • Setting SOFTMAX = 500 may avoid this problem.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * db2inidb user                                                *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * The rollforward command fails with SQL1265N "not associated  *
    * with the current log sequence" error even if the 1st         *
    * rollforward command completes successfully with the same     *
    * database image after archive log and db2inidb.               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to db2 Version 9.7 FixPak 6                          *
    ****************************************************************
    

Problem conclusion

  • Problem was first fixed in Version 9.7 FixPak 6
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC68251

  • 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-04-28

  • Closed date

    2012-03-06

  • Last modified date

    2012-03-06

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

    IC67438

  • 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 #: IC68251

Modified date: 06 March 2012