ORA-00054 SQL Origin: Data OSI layer 7 · Application Last updated 13 Oct 2026

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

  1. Find and finish the blocking session
  2. Use DDL_LOCK_TIMEOUT to wait
  3. Schedule DDL off-peak

Detailed fix by platform

SQL

  1. ALTER SESSION SET DDL_LOCK_TIMEOUT = 60;

How to diagnose

  1. Blocker — v$locked_object / v$session
  2. 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:

Where this error sits

Origin: Data. Errors that are often confused with or caused by this one (click to open):

1205 — SQL Server Msg 1205: Transaction was deadlocked on lock resources and has been chosen as the deadlock victim (SQL)12051213 — MySQL ERROR 1213 (40001): Deadlock found when trying to get lock; try restarting transaction (MySQL)12131222 — SQL Server Msg 1222: Lock request time out period exceeded (SQL)1222Deadlock — Deadlock found when trying to get lock; try restarting transaction (SQL)DeadlockError acquiring the state lock — Terraform: Error: Error acquiring the state lock — ConditionalCheckFailedException / state blob is already locked (Terraform)Error acquiring the s…Lock wait timeout — Lock wait timeout exceeded; try restarting transaction (MySQL 1205) (SQL)Lock wait timeoutORA-00001 — ORA-00001: unique constraint (SCHEMA.PK_X) violated (SQL)ORA-00001ORA-00018 — ORA-00018: maximum number of sessions exceeded (SQL)ORA-00018ORA-00054

Explore the map of this error Full error map →

🧠 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.