Symptom
- Quiesce all the databases and sybsecurity is the first db to quiesce.
- Observe "QUIESCE PREPARE AGENT" in ASE
1> sp_who '2407'
2> go
fid spid status loginame origname hostname blk_spid dbname tempdbname cmd block_xloid threadpool
--- ---- ---------- -------- -------- -------- -------- ------ ---------- --------------------- ----------- ----------
0 2407 background NULL NULL NULL 14 master tempdb QUIESCE PREPARE AGENT 0 NULL -
From ASE error log, sybsecurity db is in quiesced state and QUIESCE/PREPARE DATABASE: cannot acquire audit lock.
19:19:26.52 server AUDPROC: Audit lock has been granted.
19:19:26.52 server Processes trying to issue an I/O operation on the quiesced database(s) will be suspended until the user executes a QUIESCE DATABASE command with the RELEASE option.
19:19:26.52 server Your query is blocked because it tried to write and database 'sybsecurity' is in a quiesced state. Your query will proceed after the DBA performs QUIESCE/PREPARE DATABASE RELEASE.
19:28:50.61 server QUIESCE DATABASE command with tag all_tag is being executed by process 2407.
19:28:50.61 server QUIESCE/PREPARE DATABASE: Could not acquire audit lock. Lock status is DIDNTQUEUE..
Read more...
Environment
- SAP Adaptive Server Enterprise (ASE) 16.0
- SAP Adaptive Server Enterprise (ASE) 15.7
- SAP Adaptive Server Enterprise (ASE) 15.7 for Business Suite
- SAP Adaptive Server Enterprise (ASE) 16.0 for Business Suite
- SAP NetWeaver (NW) - All versions
Product
Keywords
deadlock,hang , KBA , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , 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.