Fixes are available
APAR status
Closed as fixed if next.
Error description
This problem only occurs when the HADR_SPOOL_LIMIT database configuration parameter is set to -1. 1) Incorrect reporting of the HADR_SPOOL_LIMIT database configuration parameter from "db2pd -dbcfg": the value reported is 4294967295, instead of -1. 2) Incorrect reporting of STANDBY_SPOOL_PERCENT monitor element from "db2pd -hadr" or HADR monitor table function: the value reported might not match real usage on of the space in the file system. This might generate false alarm alert for log spool usage exceeding threshold.
Local fix
We can avoid the problems by setting STANDBY_SPOOL_LIMIT database configuration parameter is set to a fixed value.
Problem summary
**************************************************************** * USERS AFFECTED: * * AIX/Linux * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to v11.1 4.6 * ****************************************************************
Problem conclusion
Temporary fix
Comments
APAR Information
APAR number
IT31103
Reported component name
DB2 FOR LUW
Reported component ID
DB2FORLUW
Reported release
B10
Status
CLOSED FIN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-11-28
Closed date
2021-03-13
Last modified date
2021-03-13
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
RB10 PSY
UP
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
04 May 2022