Fixes are available
DB2 Version 9.1 Fix Pack 4a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 4 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 7 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 5 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 6 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 3a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 6a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 7a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 8 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 9 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12 for Linux, UNIX and Windows
APAR status
Closed as program error.
Error description
APAR IY85138 addressed the fact that the "First Active Log File" was not being updated correctly on the Standby server. The fix lowers the maximal number of log files the standby needs. However, the log file set never shrinks on standby database. After creating a large number of files, the standby does not shrink the set by deleting unneeded files. Causes for large number of files include slow or blocked log archiving on primary. Once the set grows, it does not shrink even after the cause of the growth goes away (ie. log archiving works again or first active log file moves again). This affects only the HADR Standby server, not the HADR primary server.
Local fix
1. Deactivate standby database. 2. Find out the last log file archived on the primary (check the recovery history file on primary) and the current "first active log file" on STANDBY. 3. Remove standby log files prior to (excluding) Min(last log file archived on primary, "first active log file" on standby) NOTE: For best performance, remove fewer files. It is recommended to keep logprimary + logsecond log files on standby. Should the standby need more log files later, if old files are still around, they can be quickly renamed to new log files. Otherwise, the standby would have to recreate the needed log files.
Problem summary
Users Affected: All Problem Description: HADR standby database log file set does not shrink Problem Summary: HADR standby database log file set does not shrink APAR IY85138 addressed the fact that the "First Active Log File" was not being updated correctly on the Standby server. The fix lowers the maximal number of log files the standby needs. However, the log file set never shrinks on standby database. After creating a large number of files, the standby does not shrink the set by deleting unneeded files. Causes for large number of files include slow or blocked log archiving on primary. Once the set grows, it does not shrink even after the cause of the growth goes away (ie. log archiving works again or first active log file moves again). This affects only the HADR Standby server, not the HADR primary server.
Problem conclusion
Problem was first fixed in version 9 fixpack 3a (s070914)
Temporary fix
Comments
APAR Information
APAR number
IY94994
Reported component name
DB2 UDB ESE SOL
Reported component ID
5765F4102
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2007-02-16
Closed date
2008-02-20
Last modified date
2008-02-20
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
DB2 UDB ESE SOL
Fixed component ID
5765F4102
Applicable component levels
R810 PSN
UP
R820 PSN
UP
R910 PSN
UP
R950 PSN
UP
Document Information
Modified date:
07 January 2022