Symptom
- A QUIESCE DATABASE fails
- After several warnings "Waiting for multi-database prepared transactions to complete" are printed in the ASE error log
- Followed by error 2236 indicating the quiesce timed out
- ASE log entries show:
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.
QUIESCE DATABASE command with tag dbname_tagname is being executed by process 538.
QUIESCE DATABASE: Waiting for multi-database prepared transactions to complete. Retry count: 1.
QUIESCE DATABASE: Waiting for multi-database prepared transactions to complete. Retry count: 2.
...
QUIESCE DATABASE: Waiting for multi-database prepared transactions to complete. Retry count: 17.
Error: 2236, Severity: 16, State: 1
Process 538 is aborted by QUIESCE DATABASE, as transactions in a prepare state did not finish within the prescribed time limit. - In Business Suite systems it may be followed by error 12205:
Error: 12205, Severity: 17, State: 2
Could not acquire a lock within the specified wait period. SERVER level wait period=1800 seconds, spid=16, lock type=shared
Read more...
Environment
- SAP Adaptive Server Enterprise (ASE)
- SAP Adaptive Server Enterprise (ASE) for Business Suite
Product
SAP Adaptive Server Enterprise 15.7 ; SAP Adaptive Server Enterprise 16.0 ; SAP NetWeaver 7.4
Keywords
QUIESCE fails, deadlock , 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.