Fixes are available
APAR status
Closed as program error.
Error description
When online recovery feature is enabled (via DB2_ONLINERECOVERY registry variable), the rolling back of inflight transaction might be deferred during synchronous phase of database recovery. Insufficient log space was reserved for the deferred transaction, which can result in a failure to process the deferred rollback (due to log space being consumed by new transactions). You may see db2diag.log message similar to these: 2018-12-18-16.52.58.264139-300 I282863E534 LEVEL: Error PID : 9937 TID : 140318821312256 PROC : db2sysc INSTANCE: db2ins NODE : 000 DB : X APPHDL : 0-50 APPID: *LOCAL.DB2.181218215312 HOSTNAME: hotel EDUID : 117 EDUNAME: db2agent (X) FUNCTION: DB2 UDB, recovery manager, sqlprudm, probe:15550 MESSAGE : ZRC=0x85100009=-2062548983=SQLP_NOSPACE "Log File has reached its saturation point" DIA8309C Log file was full. 2018-12-18-16.52.58.264390-300 I283398E729 LEVEL: Error PID : 9937 TID : 140318821312256 PROC : db2sysc INSTANCE: db2ins NODE : 000 DB : X APPHDL : 0-50 APPID: *LOCAL.DB2.181218215312 HOSTNAME: hotel EDUID : 117 EDUNAME: db2agent (X) FUNCTION: DB2 UDB, recovery manager, sqlprAsyncUndo, probe:1550 MESSAGE : ZRC=0x85100009=-2062548983=SQLP_NOSPACE "Log File has reached its saturation point" DIA8309C Log file was full. DATA #1 : unsigned integer, 2 bytes 0 DATA #2 : unsigned integer, 2 bytes 0 DATA #3 : unsigned integer, 2 bytes 0 DATA #4 : unsigned integer, 2 bytes 0 DATA #5 : unsigned integer, 2 bytes 0 2018-12-18-16.52.58.264805-300 I284128E698 LEVEL: Error PID : 9937 TID : 140318821312256 PROC : db2sysc INSTANCE: db2ins NODE : 000 DB : X APPHDL : 0-50 APPID: *LOCAL.DB2.181218215312 HOSTNAME: hotel EDUID : 117 EDUNAME: db2agent (X) FUNCTION: DB2 UDB, recovery manager, sqlprAsyncUndo, probe:27110 MESSAGE : ZRC=0x85100009=-2062548983=SQLP_NOSPACE "Log File has reached its saturation point" DIA8309C Log file was full. DATA #1 : <preformatted> Force shutdown of database due to error during rollback processing. Asynchronous Undo will be disabled for the next crash recovery. If you see the message above, this indicates that a subsequent attempt for crash recovery will not use the ONLINE RECOVERY feature which will avoid this problem. To prevent future occurrences of this problem, you can disable the ONLINERECOVERY feature: db2set DB2_ONLINERECOVERY=0
Local fix
db2set DB2_ONLINERECOVERY=NO
Problem summary
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher * ****************************************************************
Problem conclusion
First fixed in Db2 11.1 Mod 4 Fixpack 5
Temporary fix
Comments
APAR Information
APAR number
IT27424
Reported component name
DB2 FOR LUW
Reported component ID
DB2FORLUW
Reported release
B10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-12-18
Closed date
2020-01-16
Last modified date
2020-01-16
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 FOR LUW
Fixed component ID
DB2FORLUW
Applicable component levels
RB10 PSN
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