Symptom
- After executed system procedure sa_flush_cache Server became non-responsive
- Srvlog file contains messages:
W. ** Task 0x71cb30(Request task 319) is trying get forbid mutex held by task 0x71b6c0(Request task 314) for more than 60000 ms
W. ** Task 0x71b6c0(Request task 314) state: OS thread id=0x7f76bffff700
W. ** Task 0x71b6c0(Request task 314) state: worker=0x7f76b4000930 wakend=1 waiting=40
W. ** Worker 0x7f76b4000930 state: wakend=0 waiting=0 in_atomic=0 is_dedicated=0 in_critical_section=0 allow_forbid=0
.....
W. ** Worker 0x7f76b4000930 state: wakend=0 waiting=0 in_atomic=0 is_dedicated=0 in_critical_section=0 allow_forbid=0
- Manual Stacktrace generated during server hanging
pthread_cond_wait@@GLIBC_2.3.2
UnixTask::wait
BaseRWLatch::wait
BaseRWLatch::get_exclusive
CacheInfo::Latch
CacheImpl::FlushPages
CacheImpl::Flush
CacheImpl::sa_flush_cache(Database*)
sa_flush_cache(InternalProcCall&)
RunInternalProcedure
Read more...
Environment
SAP IQ 16.1
Product
SAP IQ 16.1
Keywords
sybase, CR829445, CR#829445, 829445 , KBA , BC-SYB-IQ , Sybase IQ , Product Enhancement
About this page
This 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.