|
Problem IT10707
|
Status: Closed |
WITH MULTIPLE DB2READLOG API CALLERS (HADR, CDC, ETC), LOG FILES MAY NOT BE RENAMED RESULTING IN PRIMARY LOG PATH TO FILL UP |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
Similar to IT07968, and found predominantly when HADR and
another db2readlog caller are used together, 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 Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.5 Fix Pack 7. *
**************************************************************** |
| Local Fix: |
|
| Solution |
First fixed in DB2 Version 10.5 Fix Pack 7. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 14.08.2015
22.01.2016
22.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
|
 |
