DB2 - Problem description
Problem IT39945 | Status: Closed |
APPLICATION MAY HANG IN GETFASTWRITERRECORD IF THE INTERNAL POOLFOR EVENT MONITORING IS EXHAUSTED. | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
When a locking event monitor is active and a locking event occurs, the agent may hang in the following stack if the system monitor pool (the internal pool for event monitoring) is exhausted. Stack: 0x00003FEC253E5980 0x00003FFF6826C198 semtimedop + 0x0038 0x00003FEC253E5B70 0x00003FFF721E12FC sqmLockEvents::GetFastWriterRecord(sqeBsuEdu*, sqmFastWriterManager*, sqmFastWriterQueueMgr*, sqmFastWriterRecord**, unsigned short, bool) + 0x0e5c 0x00003FEC253E5DD0 0x00003FFF721E2C18 sqmLockEvents::collectLockEvent(sqeBsuEdu*, unsigned int, SQLP_LOCK_INFO*, SQLP_LRB*, sqlrw_threshold_cb*, int, unsigned int, unsigned char, sqm_dlconn_list*, long, short, bool) + 0x11a8 This problem may occur under the following conditions: 1. The application holds a large number of uncommitted statements. 2. DB2_MAX_INACT_STMTS is set to a value higher than the default value (250). 3. The configuration parameter for the event monitor (e.g. mon_locktimeout) is set to a level higher than HISTORY. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Anybody using a locking event monitor and set the reg var * * DB2_MAX_INACT_STMTS to a high value. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Code change will not be provided for V11.1. * * Please try the local fix. * **************************************************************** | |
Local Fix: | |
Deactivate the locking event monitor inactive or set DB2_MAX_INACT_STMTS to the default value. | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * Anybody using a locking event monitor and set the reg var * * DB2_MAX_INACT_STMTS to a high value. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Code change will not be provided for V11.1. * * Please try the local fix. * **************************************************************** | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 13.02.2022 18.04.2022 18.04.2022 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |