|
Problem IC64007
|
Status: Closed |
IMPROVE DIAGNOSTICS OF DIA8425C INVALID TIMESTAMP WAS FOUND IN A LOG FILE DURING RECOVERY MESSAGE. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
2009-03-18-16.53.14.395065-240 I11757A493 LEVEL: Error
PID : 2535588 TID : 1 PROC :
db2agntp (SAMPLE) 0
INSTANCE: db2inst1 NODE : 000
APPHDL : 0-56 APPID: *N0.db2inst1.090318205315
AUTHID : DB2INST1
FUNCTION: DB2 UDB, recovery manager, sqlpInitForwardRecovery,
probe:370
RETCODE : ZRC=0x86100018=-2045771752=SQLPR_BACK_IN_TIME "Time
prior to recovery"
DIA8425C Invalid timestamp was found in a log file
during recovery.
DIA8425C can occur under the following conditions
1) create online backup of node 0, and record time as
timestamp1
2) insert rows into a table on both nodes to generate
additional log records, and record time as timestamp2
3) create online backup of node 1, and record time as
timestamp3
4) restore nodes 0 and 1
5) db2 rollforward db sample complete
6) db2 rollforward db sample to <timestamp2>, note that
timestamp2 is after the backup of node 0 and before the backup
of node 1
The message indicates that there is a problem with a timestamp
stored in one of the log files used by rollfoward recovery.
This is not the problem. The problem is that the timestamp
specified in the rollforward command is not sufficient to
complete rollfoward recovery.
Rollforward recovery can be completed successfully by executing
'db2 rollforward db sample to <timestamp3>'
This APAR will improve the diagnostics information necessary to
resolve the DIA8425C message. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* rollforward *
****************************************************************
* PROBLEM DESCRIPTION: *
* DIA8425C can occur under the following conditions *
* *
* 1) create online backup of node 0, and record time as *
* timestamp1 *
* 2) insert rows into a table on both nodes to generate *
* additional log records, and record time as timestamp2 *
* 3) create online backup of node 1, and record time as *
* timestamp3 *
* 4) restore nodes 0 and 1 *
* 5) db2 rollforward db sample complete *
* 6) db2 rollforward db sample to <timestamp2>, note that *
* timestamp2 is after the backup of node 0 and before the *
* backup of node 1 *
* *
* The message indicates that there is a problem with a *
* timestamp *
* stored in one of the log files used by rollfoward recovery. *
* *
* This is not the problem. The problem is that the timestamp *
* specified in the rollforward command is not sufficient to *
* complete rollfoward recovery. *
* *
* Rollforward recovery can be completed successfully by *
* executing *
* 'db2 rollforward db sample to <timestamp3>' *
* This APAR will improve the diagnostics information necessary *
* to *
* resolve the DIA8425C message. *
* *
* 2009-03-18-16.53.14.395065-240 I11757A493 LEVEL:Error *
* PID : 2535588 TID : 1 PROC *
* :db2agntp (SAMPLE) 0 *
* INSTANCE: db2inst1 NODE : 000 APPHDL : 0-56 *
* APPID:*N0.db2inst1.090318205315 AUTHID : DB2INST1 *
* FUNCTION: DB2 UDB, recovery manager, *
* sqlpInitForwardRecovery, probe:370 *
* RETCODE : ZRC=0x86100018=-2045771752=SQLPR_BACK_IN_TIME *
* "Time prior to recovery" *
* DIA8425C Invalid timestamp was found in a log file *
* during recovery. *
****************************************************************
* RECOMMENDATION: *
* apply v9.7.2 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows
|
| Solution |
Problem is first fixed in DB2 UDB version 9.7 fix pack 2. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.10.2009
18.02.2010
18.02.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.2,
9.7.FP2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
