|
Problem IC68251
|
Status: Closed |
ROLLFORWARD FAILS WITH SQL1265N "NOT ASSOCIATED WITH THE CURRENT LOG SEQUENCE" AFTER DB2INIDB |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem 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. |
| 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 *
**************************************************************** |
| Local Fix: |
Setting SOFTMAX = 500 may avoid this problem. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in Version 9.7 FixPak 6 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 28.04.2010
06.03.2012
06.03.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.3
|
 |
| 9.7.0.3
|
|
| 9.7.0.6
|
|
