|
Problem IC63176
|
Status: Closed |
DB2DIAG.LOG SHOWS FAILED TO ARCHIVE LOG ERROR MESSAGE AFTER REDO/FORWARD PHASE OF ROLLFORWARD RECOVERY |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
DB2 can attempt to archive a log that has already been archived
and deleted. The db2diag.log will show a failed to archive log
error message due to file not found (SQLO_FNEX error). This can
occur right after the redo/forward phase of recovery, when log
manager is first activated and begins to archive logs. The
message should in fact be a warning, not an error, since there
are documented scenarios where DB2 cannot know that it has
already archived a log. So it does the safe thing and tries to
archive the log again.
DB2 will continue after these error messages and the system will
not be negatively affected.
Errors in the db2diag.log include:
FUNCTION: DB2 UDB, data protection services,
sqlpgArchiveLogFile, probe:3160
MESSAGE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found."
DIA8411C A file "" could not be found.
DATA #1 : <preformatted>
Failed to archive log file S0001347.LOG to
/db2_storage/LA5/log_arch/db2la5/LA5/NODE0000/C0000002/ from
/db2/db2la5/db2la5/NODE0000/SQL00001/SQLOGDIR/.
FUNCTION: DB2 UDB, data protection services,
sqlpgArchivePendingLogs, probe:1500
MESSAGE : Log archive failed with rc -2045837302 for
LOGARCHMETH1. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* users of log archiving *
****************************************************************
* PROBLEM DESCRIPTION: *
* DB2 can attempt to archive a log that has already been *
* archived *
* and deleted. The db2diag.log will show a failed to archive *
* log *
* error message due to file not found (SQLO_FNEX error). This *
* can *
* occur right after the redo/forward phase of recovery, when *
* log *
* manager is first activated and begins to archive logs. The *
* *
* message should in fact be a warning, not an error, since *
* there *
* are documented scenarios where DB2 cannot know that it has *
* *
* already archived a log. So it does the safe thing and tries *
* to *
* archive the log again. *
* *
* *
* *
* DB2 will continue after these error messages and the system *
* will *
* not be negatively affected. *
* *
* *
* *
* Errors in the db2diag.log include: *
* *
* *
* *
* FUNCTION: DB2 UDB, data protection services, *
* *
* sqlpgArchiveLogFile, probe:3160 *
* *
* MESSAGE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not *
* found." *
* DIA8411C A file "" could not be found. *
* *
* DATA #1 : <preformatted> *
* *
* Failed to archive log file S0001347.LOG to *
* *
* /db2_storage/LA5/log_arch/db2la5/LA5/NODE0000/C0000002/ from *
* *
* /db2/db2la5/db2la5/NODE0000/SQL00001/SQLOGDIR/. *
* *
* *
* *
* FUNCTION: DB2 UDB, data protection services, *
* *
* sqlpgArchivePendingLogs, probe:1500 *
* *
* MESSAGE : Log archive failed with rc -2045837302 for *
* *
* LOGARCHMETH1. *
****************************************************************
* RECOMMENDATION: *
* apply v9.7.2 *
**************************************************************** |
| Local Fix: |
User should verify that the failed archive log already exists in
the archive path/device |
| 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 |
Apply v9.7.2 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 14.09.2009
19.02.2010
19.02.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
