DB2 FOR LUW / DB2FORLUW / A10 - DB2

In purescale environment, when a member is deactivated, it tries 
to clean up all log files it retrieved from other log streams. 
This problem happens when the deactivating member incorrectly 
removed retrieved log files needed by other members. 
 
The reported Missing Log error in this APAR is merely a symptom 
of retrieved log files incorrectly removed. A missing log error 
can be caused by other errors unrelated to this APAR. 
 
 
 
Example Error Scenario: 
You receive a SQL1273 error in a online tablespace rollforward 
operation on member 0. 
 
db2 rollforward db SAMPLE to end of logs tablespace online 
SQL1273N  An operation reading the logs on database "SAMPLE" 
cannot continue 
because of a missing log file "S0003209.LOG" on database 
partition "0" and log 
stream "1". 
 
 
 
To confirm whether this reported SQL1273 is caused by this APAR, 
check the following in the db2diag.log: 
 
 
1. The member on which you performed the online tablespace 
rollforward has successfully retrieved the missing log file. 
 
2013-08-22-06.26.22.469121-240 I177554407E542        LEVEL: Info 
PID     : 722                  TID : 46915416746304  KTID : 6212 
PROC    : db2sysc 0 
INSTANCE: TEST               NODE : 000            DB   : SAMPLE 
HOSTNAME: HOST0 
EDUID   : 1043                 EDUNAME: db2logmgr.1 (SAMPLE) 0 
FUNCTION: DB2 UDB, data protection services, 
sqlpgRetrieveLogFile, probe:4148 
DATA #1 : <preformatted> 
Completed retrieve for log file S0003209.LOG on chain 0 to 
/TEST/newlogpath/NODE0000/LOGSTREAM0000/LOGSTREAM0001/. 
 
 
2. Another member was deactivated/shut down afterwards. 
 
2013-08-22-06.26.39.550214-240 I177653766E603        LEVEL: Info 
PID     : 718                  TID : 46915118950720  KTID : 8284 
PROC    : db2sysc 1 
INSTANCE: TEST               NODE : 001            DB   : SAMPLE 
APPHDL  : 0-15211              APPID: *N0.test.130822045407 
AUTHID  : TEST               HOSTNAME: HOST1 
EDUID   : 1370                 EDUNAME: db2periodic (SAMPLE) 1 
FUNCTION: DB2 UDB, data protection services, 
sqlpRemoveCFContribsAtShutdown, probe:505 
DATA #1 : <preformatted> 
Refreshed maximum groupMinBuffLSN at database shutdown to 
000000000103DA92 
from 0000000000E8D5C5. 
 
 
3. Missing log file error was reported. 
2013-08-22-13.06.40.583745-240 E220540373E678        LEVEL: 
Error 
PID     : 722                  TID : 46915924257088  KTID : 3205 
PROC    : db2sysc 0 
INSTANCE: TEST               NODE : 000            DB   : SAMPLE 
APPHDL  : 0-23173              APPID: *N0.testi.130822134717 
AUTHID  : TEST               HOSTNAME: HOST0 
EDUID   : 973                  EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, recovery manager, 
sqlpshrValidateLogStreamEndPoint, probe:1112 
MESSAGE : ADM1601E  A recovery or rollforward operation on 
database "SAMPLE" 
          cannot continue because of a missing log file 
"S0003209.LOG" on 
          database partition "0" and log stream "1".

**************************************************************** 
* USERS AFFECTED:                                              * 
* Purescale Environment                                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* See Local Fix:                                               * 
* Follow the instructions of the SQL1273N error to address     * 
* this problem.                                                * 
* If problem continues, deactivate the member you see the      * 
* error on, and re-activate the member. Then perform the       * 
* online tablespace rollforward command again.                 * 
****************************************************************

Follow the instructions of the SQL1273N error to address this 
problem. 
If problem continues, deactivate the member you see the error 
on, and re-activate the member. Then perform the online 
tablespace rollforward command again.

The deactivating member will only remove the log files it 
retrieved. It will not incorrectly remove retrieved log files 
for other members. 
This fix is included in DB2V105FP4 (CANCUN).

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

09.04.2014
15.09.2014
15.09.2014