|
Problem IT10544
|
Status: Closed |
DATABASE UPGRADE FAILS TO RENAME OR DELETE UNARCHIVED LOGS AND LOGS WITHIN PRIMARY/MIRROR PATH |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
When databases is upgraded from 10.1 to 10.5, the log files are
not renamed from Sxxxxxxx.LOG to Sxxxxxxx.MIG file.
This may cause issues with new log archivals because the logs
are still found by DB2. Then DB2 attempts to start archive
requests for these logs, but fails because those are
pre-versioned (10.5) db2 log files.
Before a database upgrade is performed DB2 might still have
unarchived logs (log that have not yet been archived). Those are
located in the active log directory and in the mirror log
directory if dual logging via MIRRORLOGPATH is configured. If a
database is upgraded (UPGRADE DATABASE) to a new release, then
the old version log files in the active log directory are
renamed. This does NOT happen for the log files in either path
currently. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Apply DB2 UDB V10.5 Fixpack 7 *
**************************************************************** |
| Local Fix: |
|
| Solution |
Apply DB2 UDB V10.5 Fixpack 7 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 06.08.2015
25.01.2016
25.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
|
 |
