DB2 - Problem description
Problem IC65073 | Status: Closed |
SET WRITE SUSPEND AND RESUME CAN DEADLOCK WITH A BLOCKED TABLE EVENT MONITOR | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
SET WRITE RESUME will hang forever in the following stack, waiting on dblatch: sqloXlatchConflict - 0x70 sqlbSetWriteResume__FP12SQLB_GLOBALSbP5sqlcaiPUs + 0x920 sqlbSetWriteAction__FP12SQLB_GLOBALSClCbP5sqlcaCiPUs + 0xDC sqlbSetPoolChange__FP5sqldaT1P5sqlca + 0x460 sqlerKnownProcedure__FiPcPiP5sqldaT4P13sqlerFmpTable + 0x3EC sqlerCallDL__FP14db2UCinterfaceP9UCstpInfo + 0x64C sqljs_ddm_excsqlstt__FP14db2UCinterfaceP13sqljDDMObject + 0xA8 ... The dblatch is held by an agent doing a flush event monitor, waiting on em_list_latch: sqloXlatchConflict - 0x70 sqloXlatchConflict@glue15D + 0x74 flush_monitor__13sqm_evmon_mgrFPC9sqlm_empdCUc + 0x474 flush_event_monitor__13sqm_evmon_mgrFPC9sqlm_empdCUi + 0x130 sqlrlfem__FP8sqlrr_cbPUcUsUc + 0x260 sqlnq_flush_evmon_stmt__FPP8stknode_i10actiontypePU + 0x168 ... The em_list_latch is held by an agent trying to write an event to a buffer. The event monitor itself is not able to write out a full buffer to the database, because of the write suspend state. | |
Problem Summary: | |
USERS AFFECTED: All PROBLEM DESCRIPTION: See ERROR DESCRIPTION PROBLEM SUMMARY: See ERROR DESCRIPTION | |
Local Fix: | |
* Modify table event monitor from BLOCKED to NONBLOCKED * Deactivate table event monitor before a WRITE SUSPEND * Use file event monitor instead of table event monitor | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in Version 9.7 Fix Pack 2 | |
Workaround | |
See LOCAL FIX. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 10.12.2009 08.06.2010 08.06.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP2 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.2 |