ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired
DDL or a NOWAIT lock couldn’t get the lock because another session holds it.
Exact message you may see
resource busy and acquire with NOWAIT specified
Seen on:
SQL
Meaning
ALTER/DROP on a table with active transactions, or SELECT … FOR UPDATE NOWAIT on locked rows.
Common causes
- Uncommitted transactions on the table
- DDL during busy hours
- NOWAIT locks on rows in use
⚡ Quick fix
- Find and finish the blocking session
- Use DDL_LOCK_TIMEOUT to wait
- Schedule DDL off-peak
Detailed fix by platform
SQL
ALTER SESSION SET DDL_LOCK_TIMEOUT = 60;
How to diagnose
- Blocker — v$locked_object / v$session
- Recent change — Did it start after a deploy, upgrade, or configuration change? Compare with the last working version.
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in SQL
Other ways to find it
Where this error sits
Origin: Data. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Did this fix work for you?
Report a correction or suggest an improvement
Last updated 13 Oct 2026