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

A CLEAN HADR TAKEOVER PROCESS (WHILE THE DATABASES ARE IN PEER STATE) CAN
BE SLOW IF THE HISTORY FILE IS VERY LARGE.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
During a clean takeover process (while primary and standby 
databases are in peer sate), we make an unnecessary history 
cleanup call during rollforward recovery.  Original standby will 
call sqlprDoForwardPhase() to finish its rollforward call at the 
end of the takeover before the standby database becomes primary 
database.  During this call, we make a history cleanup call 
through sqlpCleanHistFile() for retrieved log files. 
 
In a clean takeover (while the databases are in peer state), no 
logs are really retrieved to complete the rollforward process on 
the standby before it becomes primary.  Hence, we should be able 
to skip this call to clean up the history file.  This will avoid 
performance issues during takeover for databases with large 
history files.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users using HADR on all platforms                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* HADR takeover is slow when database history file is large    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v97fp3                                        * 
****************************************************************
Local-Fix:
Prune history to make the history file smaller in size.
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
The problem is fixed in DB2 v97fp3. The performance of HADR 
takeover then has nothing to do with database history file size.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
21.06.2010
02.08.2010
02.08.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP3
Problem behoben lt. FixList in der Version
9.7.0.3 FixList
9.7.0.3 FixList