A fix is available
APAR status
Closed as program error.
Error description
This problem only occurs when the avoid replay only window feature enabled(via DB2_HADR_ROS_AVOID_REPLAY_ONLY_WINDOW register variable). The problem is due to lack of proper serialization when replaying log records. This can result in Db2 hitting a trap on the standby instance, or encountering a fatal or non fatal FODC_IndexError. In the non fatal case the error is tolerated by marking the index as requiring rebuild. In the non fatal case and you see a various error probes from sqliRedo and a message like: FUNCTION: DB2 UDB, index manager, sqliMarkInxBadDuringUndoRedo, probe:2037 MESSAGE : ZRC=0x82090001=-2113339391=SQLI_NONSEVERE_PRGERR "Non severe index programming error" DIA8532C An internal processing error has occurred. Below is an example of the trap that can occur. Note the exact stack might vary depending on timing of execution, but may include sqliRedo or sqldRedo. _Z7sqlbfixP11SQLB_FIX_CB + 0x039e _Z7sqlifixP7SQLI_CBP14SQLI_PAGE_DESCjiPm + 0x006f address: 0x00007F9B0B4BB1E7 ; dladdress: 0x00007F9B0263F000 ; offset in lib: 0x0000000008E7C1E7 ; _Z8sqliRedoP8sqeAgentPctP9SQLP_LSN8mmP32SQLP_RECOVERY_EVENT_REAS ON_CODES + 0x4c11 _Z8sqldmrdoP8sqeAgenttP9SQLP_LSN8PcmmmmP8SQLP_TIDP15SQLD_RECOV_I NFO + 0x0c8e _Z13sqlpRecDbRedoP8sqeAgentP8SQLP_ACBP14sqlpMasterDbcbP10SQLP_FR APPP11SQLP_TENTRYP16SQLPR_LOGREC_DISP10REDO_INPUT + 0x27c4 _Z15sqlpPRecProcLogP8sqeAgentP8SQLP_ACBP14sqlpMasterDbcb + 0x15a8 _Z20sqlpParallelRecoveryP8sqeAgentP5sqlca + 0x0f6e _Z26sqleSubCoordProcessRequestP8sqeAgent + 0x017c
Local fix
Turn off DB2_HADR_ROS_AVOID_REPLAY_ONLY_WINDOW to avoid this issue.
Problem summary
**************************************************************** * USERS AFFECTED: * * The users running Db2 HADR with avoid replay only window * * feature enabled. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 v11.1.4.7 or later versions. * ****************************************************************
Problem conclusion
The problem is firstly fixed on Db2 v11.1.4.7.
Temporary fix
Comments
APAR Information
APAR number
IT35472
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
2021-01-10
Closed date
2022-04-17
Last modified date
2022-04-17
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 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