|
Problem IT03449
|
Status: Closed |
THE ROLLFORWARD DB COMMAND PRINTED INCORRECT RESULT FOR LOG FILES PROCESSED. |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
The proceeding rollforward database command printed the
incorrect log file name for Log files processed.
In the following example, S0000013.LOG is no longer necessary
after the rolloforward database command.
However, the succeeding rollforward database command needed
S0000013.LOG.
example)
1.
$ db2 rollforward db t27761 to end of logs
Rollforward Status
Input database alias = t27761
Number of members have returned status = 1
Member ID = 0
Rollforward status = DB working
Next log file to be read = S0000014.LOG
Log files processed = S0000013.LOG -
S0000013.LOG
Last committed transaction =
2014-07-11-06.52.00.000000 UTC
2.
Deleting S0000013.LOG.
3.
$ db2 rollforward db t27761 to end of logs
SQL1273N An operation reading the logs on database "T27761"
cannot continue
because of a missing log file "S0000013.LOG" on database
partition "0" and log
stream "0". |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All user. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 10.5.0.7. *
**************************************************************** |
| Local Fix: |
Do not remove SYYYYYYY.LOG printed at Log files processed.
Log files processed = SXXXXXXX.LOG -
SYYYYYYY.LOG |
| Solution |
The problem is first fixed in DB2 version 10.5.0.7. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 29.07.2014
28.01.2016
28.01.2016 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.7
|
 |
