Symptom
- One DUMP process of a database is blocking all of other DUMP processes.
The DUMP processes which are being blocked go into lock sleep status.
1> sp_who
2> go
fid spid status loginame origname hostname blk_spid
dbname tempdbname cmd block_xloid
threadpool
--- ---- ---------- ------------ ------------ ------------ --------
------------ ---------- -------------------- -----------
----------------
0 111 sleeping sa sa hostnames*** 0
dbname****** tempdb DUMP TRANSACTION 0
syb_default_pool
0 112 lock sleep sa sa hostnames*** 111
dbname****** tempdb DUMP TRANSACTION 0
syb_default_pool
0 113 lock sleep sa sa hostnames*** 111
dbname****** tempdb DUMP TRANSACTION 0
syb_default_pool
0 114 lock sleep sa sa hostnames*** 111
dbname****** tempdb DUMP TRANSACTION 0
syb_default_pool
0 115 lock sleep sa sa hostnames*** 111
dbname****** tempdb DUMP DATABASE 0
syb_default_pool
...... - You have 'enable concurrent dump tran' or 'enable functionality group' configured to 1.
Read more...
Environment
SAP Adaptive Server Enterprise (ASE) 16.0
Product
SAP Adaptive Server Enterprise 16.0
Keywords
dump, sp_who, block, blocking, blk_spid , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Problem
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.