|
Problem IC78068
|
Status: Closed |
TABLESPACE ROLLFORWARD COMPLETE MAY RETRIEVE TOO MANY LOG FILES |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
A tablespace restore followed by a ROLLFORWARD to Point in Time
may retrieve too many log files if the rollforward command is
issued in two seperate steps.
The 1. Step:
ROLLFORWARD DB <DBNAME> TO <POINT IN TIME> TABLESPACE
(<TBSPNAME>, ...)
works like expected and DB2 will request only those log files
needed for the rollforward, i.e. only the log files that contain
transactions that apply to the tablespaces being rollfowarded.
You may see the following in db2diag.log which indicate that log
files were skipped :
2011-07-14-20.00.58.000750+120 I31648811A679 LEVEL: Warning
PID : 22741502 TID : 44652 PROC : db2sysc
32
INSTANCE: db2inst1 NODE : 032 DB : SAMPLE
APPHDL : 1-4120 APPID: *N1.db2inst1.110714175100
AUTHID : db2inst1
EDUID : 44652 EDUNAME: db2agntp (SAMPLE) 32
FUNCTION: DB2 UDB, recovery manager,
sqlpSetNextDirtyExtentToProcess, probe:1111
DATA #1 : String, 231 bytes
Starting with Log file 230985, some records do
not contain information that apply to the
tablespace(s) being rolled forward. Rolling
forward continues with log 231706.
LSN changed from 158334F8800C
to 159465A3171D
The 2. Step:
ROLLFORWARD DB <DBNAME> COMPLETE TABLESPACE (<TBSPNAME>, ...)
is expected to run very short to just complete the RFWD. Instead
it goes ahead and retrieves ALL log files since the last backup.
This can take a very long time and causes additional delay in
the rollforward recovery. The ROLLFORWARD COMPLETE command
should not retrieve these logs. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Problem Description above. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 Fix Pack 5. *
**************************************************************** |
| Local Fix: |
Run the rollforward command in one single comannd, i.e.:
ROLLFORWARD DB <DBNAME> TO <POINT IN TIME> AND COMPLETE
TABLESPACE (<TBSPNAME>, ...) |
| available fix packs: |
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 |
First fixed in Version 9.7 Fix Pack 5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 11.08.2011
18.12.2011
18.12.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
