DB2 FOR LUW / DB2FORLUW / 970 - DB2

When rollforward command faces some missing logs it fails with 
the following error message: 
 
 
$ db2 "rollforward db test to 2012-09-19-11.51 USING LOCAL TIME 
overflow log path ('/home/db2inst4/bkp_logs')" 
 
SQL4970N  Roll-forward recovery on database "TEST" cannot reach 
the specified 
stop point (end-of-log or point-in-time) on database 
partition(s) "0". 
Roll-forward recovery processing has halted on log file 
"S0000006.LOG". 
 
This defect is to enhance the above error message to include the 
path of the log file the rollforward halted on.  The SQLCA area 
has not much room for the log file path. but we can add a 
message in db2diag.log for customer reference. it can tell 
customer which log file the recovery stops on. like below: 
 
2012-10-09-04.51.59.593520-240 E14728E488          LEVEL: Info 
PID     : 18987                TID  : 46915077007680PROC : 
db2sysc 
INSTANCE: tianq                NODE : 000          DB   : TEST 
APPHDL  : 0-11                 APPID: *LOCAL.tianq.121009085156 
AUTHID  : TIANQ<<< 
EDUID   : 326                  EDUNAME: db2shred (TEST) 
FUNCTION: DB2 UDB, recovery manager, sqlpshrEdu, probe:2196 
DATA #1 : <preformatted> 
shredder scan stopped on log file 
/home/hotel72/tianq/tmp/S0000000.LOG

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix pack 8.                       * 
****************************************************************

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
 

First fixed in DB2 Version 9.7 Fix pack 8.

not known / see Local fix

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

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

01.12.2012
01.04.2013
01.04.2013

9.7.FP8