Oracle Database / Sessions, Locks & Transactions
ORA-30006: investigate a bounded lock wait that expired
A WAIT-based operation can time out while another transaction holds the required resource. Preserve the timeout and transaction context.
Environment and inputs: Oracle Database 19c baseline · SQL*Plus-compatible SQL unless RMAN, DGMGRL, ADRCI or a host shell is specified. Check release, patch level, edition and container first.
Start with this diagnostic
Use the stated SQL, RMAN, DGMGRL or host shell and replace sample names with approved targets. DBA and V$ views need authorized catalog access in the correct container. Do not grant broad privileges for an example.
SELECT sid, serial#, event, seconds_in_wait, blocking_session FROM v$session WHERE wait_class <> 'Idle' AND type = 'USER';Read the result
The snapshot can identify active waits if the contention still exists. After timeout, the original waiter may no longer be waiting.
Resolve and verify
Find the holding transaction and its business operation. Reduce lock duration or coordinate retry with a safe transaction policy instead of only lengthening the wait.
Operational precautions
Blind retries can amplify contention. Confirm whether earlier work in the transaction must be rolled back.