DB2 - Problem description
Problem IC69352 | Status: Closed |
A CLEAN HADR TAKEOVER PROCESS (WHILE THE DATABASES ARE IN PEER STATE) CAN BE SLOW IF THE HISTORY FILE IS VERY LARGE. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
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 Summary: | |
**************************************************************** * 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. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
The problem is fixed in DB2 v97fp3. The performance of HADR takeover then has nothing to do with database history file size. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 21.06.2010 02.08.2010 02.08.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP3 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.3 | |
9.7.0.3 |