Under rare circumstances, the server may become unresponsive in an MPX environment under aggressive DML operation. Stacktraces taken minutes apart will be identical and will indicate that three separate threads are blocked inside functions: hos_dualmutex::LockAndPromote, s_VersioningBlockmap::LockRFRB, s_bufman::FindBlockMap1. This has been fixed.
- One thread is holding the _blockmapsHTMutex (inside s_blockmap::Unlock) while trying to get the blockmap _Mutex;
- A second thread is holding the blockmap _Mutex (inside s_blockmap::RegisterPhysicalBlockId) while trying to get the rollback lock; and
- A third thread is holding the rollback lock (inside s_VersioningBlockmap::Allocate) while trying to get the _blockmapsHTMutex,
hence, the deadlock.
SAP IQ 16
deadlock, hang, unresponsive, 814876, CR#814876, , KBA , BC-SYB-IQ , Sybase IQ , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.