|
Problem IT07968
|
Status: Closed |
IN SPECIFIC TIMING CONDITIONS, DB2READLOG API CALLS (USED E.G BY CDC) MIGHT RESULT IN LOGS BEING LEFT IN ACTIVE LOG PATH. |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
In specific timing condition, when db2ReadLog API is called to
read last page of current log, given log will never be re-used
and will stay in active log path until database is deactivated.
This might result in multiple logs being left in active log path
filling up the disk space. db2ReadLog is mainly used by
replication solutions like IBM Q Replication or IBM InfoSphere
Change Data Capture
Problem is specific to DB2 version 10.5 Fix Pack 5. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 10.5 Fix Pack 6 or higher. *
**************************************************************** |
| Local Fix: |
Deactivate the database |
| Solution |
Problem first fixed in DB2 version 10.5 Fix Pack 6. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.03.2015
02.09.2015
02.09.2015 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.6
|
 |
