home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT07968 Status: Geschlossen

IN SPECIFIC TIMING CONDITIONS, DB2READLOG API CALLS (USED E.G BY CDC) MIGHT
RESULT IN LOGS BEING LEFT IN ACTIVE LOG PATH.

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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
Lösung
Problem first fixed in DB2 version 10.5 Fix Pack 6.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
27.03.2015
02.09.2015
02.09.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.6 FixList