Oracle Database / Sessions, Locks & Transactions
Map transaction locks to Oracle objects
An object-level view helps identify which tables are involved in current transactions. It does not by itself show a complete row-level blocking chain.
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 l.session_id, o.owner, o.object_name, o.object_type, l.locked_mode FROM v$locked_object l JOIN dba_objects o ON l.object_id = o.object_id;Read the result
The rows show transactional object locks and modes. Several sessions can hold compatible locks on the same object without blocking one another.
Resolve and verify
Combine the object list with session wait and transaction evidence. Identify the conflicting business operations and reduce unnecessarily long transactions.
Operational precautions
Do not terminate every session returned by this query. In a CDB, query the intended container and interpret object IDs in that context.