ALL_ASSERTION_LOCK_MATRIX

ALL_ASSERTION_LOCK_MATRIX displays enqueues acquired to manage concurrent DMLs for assertions accessible to the current user.

This view displays assertions owned by the current user, as well as assertions owned by other users that involve at least one table on which the current user has at least one of the following object privileges: SELECT, INSERT, UPDATE, or DELETE.

DBA_ASSERTION_LOCK_MATRIX displays enqueues acquired to manage concurrent DMLs for all assertions in the database.
USER_ASSERTION_LOCK_MATRIX displays enqueues acquired to manage concurrent DMLs for assertions owned by the current user. This view does not display the OWNER column.

Column	Datatype	Description
`OWNER`	`VARCHAR2(128)`	Owner of the assertion
`ASSERTION_NAME`	`VARCHAR2(128)`	Name of the assertion
`TABLE_ID`	`NUMBER`	Unique identifier of the table in the assertion You can join this column with the `REFERENCE_ID` column of the `DBA_ASSERTION_DEPENDENCIES` view to obtain more information about the table.
`TABLE_OWNER`	`VARCHAR2(128)`	Owner of the table
`TABLE_NAME`	`VARCHAR2(128)`	Name of the table
`ADJ_TABLE_ID`	`NUMBER`	Unique identifier of the adjacent table in the assertion You can join this column with the `REFERENCE_ID` column of the `DBA_ASSERTION_DEPENDENCIES` view to obtain more information about the adjacent table.
`ADJ_TABLE_OWNER`	`VARCHAR2(128)`	Owner of the adjacent table
`ADJ_TABLE_NAME`	`VARCHAR2(128)`	Name of the adjacent table
`LOCK_SCOPE`	`VARCHAR2(18)`	Scope of the lock: `TABLE` - The enqueue is taken at the table-level `JOIN_COLUMN_VALUES` - The enqueue(s) are taken against the join-column values of the affected rows
`JOIN_COLUMNS`	`VARCHAR2(4000)`	Join columns involved in the lock
`LOCK_MODE`	`VARCHAR2(8)`	Mode of the lock: `S` `SSX` `SX` `X`
`LOCK_TEXT`	`VARCHAR2(4000)`	Text of the lock specification

Notes:

For a given assertion that has n table references in its definition, this view will have n^{^2} (n-squared) rows.
When a DML statement is executed against a TABLE_ID, there will be n types of enqueues acquired to manage concurrent DMLs.
When LOCK_SCOPE = TABLE, only one enqueue is acquired in the given LOCK_MODE.
When LOCK_SCOPE = JOIN_COLUMN_VALUES, an enqueue is acquired in the given LOCK_MODE for each (distinct) join-column value of the rows that were affected by the DML statement.

Note: This view is available starting with Oracle AI Database 26ai, Release Update 23.26.1.

See Also:

“DBA_ASSERTION_LOCK_MATRIX”
“USER_ASSERTION_LOCK_MATRIX”

ALL_ASSERTION_LOCK_MATRIX

Related Views