DB2 FOR LUW / DB2FORLUW / 950 - DB2

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 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 on the 2nd RFWD will only occur when the 
lowtranlsn / minbufflsn / headlsn values in the LFH in the 
database backup image are all pointing to the start of a new log 
file. 
 
For example, if softmax=500 is set in the case of performing 
"archive log" command three times or if a transaction record is 
inserted before set write suspend, this error SQL1265N is not 
made on the 2nd rollforward command.

**************************************************************** 
* USERS AFFECTED:                                              * 
* db2inidb user                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The rollforward command fails with SQL1265N "not             * 
* associatedwith the current log sequence" error even if the   * 
* 1strollforward command completes successfully with the       * 
* samedatabase image after after archive log and db2inidb.     * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2 Version 9.5 FixPak 6                          * 
****************************************************************

DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
 DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
 

Problem was first fixed in Version 9.5 FixPak 6

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC68251 IC68252 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

25.03.2010
27.07.2010
27.07.2010

9.5.