|
Problem IC68546
|
Status: Closed |
ROLLFORWARD COMMAND FAILED WITH SQL4970N ERROR |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
When DB2 rollforward command with stop option is issued the
requried log file was not found. Rollforwad command can't make
the database consistent. failed with SQL4970N error. There is
extra logic involved that ends up creating a new copy of
required log file. The following messsgae could be db2diag.log
file
2010-03-23-23.15.34.375576-240 I4028087E420 LEVEL: Info
PID : 12262 TID : 183278496096 PROC :
db2sysc 3
INSTANCE: DB2INST1 NODE : 003 DB : SAMPLE
EDUID : 34412 EDUNAME: db2loggr (RAVESTAG) 3
FUNCTION: DB2 UDB, data protection services, sqlpgCallGIFL,
probe:1250
DATA #1 : <preformatted>
New log extent 50800, PId 1269236666, StartLsn 000008D5F5014000 |
| Problem Summary: |
When DB2 rollforward command with stop option is issued the
requried log file was not found. Rollforwad command can't make
the database consistent. failed with SQL4970N error. There is
extra logic involved that ends up creating a new copy of
required log file. The following messsgae could be db2diag.log
file
2010-03-23-23.15.34.375576-240 I4028087E420 LEVEL: Info
PID : 12262 TID : 183278496096 PROC :
db2sysc 3
INSTANCE: DB2INST1 NODE : 003 DB : SAMPLE
EDUID : 34412 EDUNAME: db2loggr (RAVESTAG) 3
FUNCTION: DB2 UDB, data protection services, sqlpgCallGIFL,
probe:1250
DATA #1 : <preformatted>
New log extent 50800, PId 1269236666, StartLsn 000008D5F5014000 |
| Local Fix: |
Make sure all the requried log file available. Especially when
the overflow log path is used for rollward. The following
command is recommened: rollforward db <dbname> stop overflow log
path (xxXX) |
| 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 |
The APAR is first fixed in DB2 v9.7fp3 |
| Workaround |
Make sure all the requried log file available. Especially when
the overflow log path is used for rollward. The following
command is recommened: rollforward db <dbname> stop overflow log
path (xxXX) |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 12.05.2010
23.09.2010
23.09.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP3
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.3
|
 |
| 9.7.0.3
|
|
