|
Problem IT28323
|
Status: Closed |
SQL2038N ERROR RETURNED BY DB2READLOG() WHEN COMPRESSED LOG FILEIS MANUALLY COPIED FROM ARCHIVE TO OVERFLOW LOG PATH.
|
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
This issue occurs when:
the database is configured to compress the log files stored in
archive via logarchcompr1/2 database configuration parameter
the database is also configured with an overflow log path
(overflowlogpath database configuration parameter);
the database is also the source database for replication (via
Qrep or CDC);
the user is manually copying compressed log files from the
archive location to the overflow log path (possibly via a cron
job).
In such environment, it is possible to receive an SQL2038N error
from db2ReadLog() saying the needed log file is not found. This
may occur if a file is retrieved by DB2 from the archive into
the overflow log path around the same time that the same file is
being manually copied from the archive location to the overflow
log path by the user. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* First noticed in DB2 v10.5.0.10 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 UDB V11.5. *
**************************************************************** |
| Local Fix: |
Stop the process of manually copying log files from the archive
location to the overflow log path. |
| Solution |
|
| Workaround |
Stop the process of manually copying log files from the archive
location to the overflow log path. |
| BUG-Tracking |
forerunner :
follow-up : IT28398 |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 06.03.2019
12.03.2019
12.03.2019 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
