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 IC75448 Status: Geschlossen

TOO MANY LOGFILES REMAIN IN THE ACTIVE PATH ALTHOUGH THEY ALREADY GOT
ARCHIVED

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
In HADR context, it is possible that after performing an HADR 
TAKEOVER, some log files will not be reused on the new HADR 
Primary and thus will stay in the active log files directory. 
This will have for effect to increase the number of log files in 
this directory beyond the configured number in LOGPRIMARY 
database configuration parameter.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Using HADR feature                                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See error description above                                  * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to version 9.5 fixpack 9 or above                    * 
****************************************************************
Local-Fix:
You may use the "PRUNE LOGFILE" command to remove the orphaned 
log files from the primary log path. 
Please refer to the <A 
HREF=http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/index. 
jsp?topic=/com.ibm.db2.luw.admin.cmd.doc/doc/r0001992.html>PRUNE 
</A> 
command.
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
This fix improve log file management in HADR take over situation 
in order to avoid orphaned log files in the primary log path. 
First fixed in version 9.5 fixpack 9
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC75495 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
31.03.2011
07.03.2012
07.03.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP9
Problem behoben lt. FixList in der Version
9.5.0.9 FixList