First page Back Continue Last page Graphics
DDL Locks
Exclusive lock taken during DDL operation
Released after DDL completion via implicit COMMIT
DDL call process includes:
Commits your transaction even if DDL fails!
Notes:
DDL operations include CREATE, DROP, ALTER and TRUNCATE. A lock is taken to prevent multiple transactions from changing or dropping the object at the same time, i.e. to serialize the operations.
Carefully review the COMMITs executed automatically for each DDL statement. Notice that a COMMIT is executed before the DDL statement. This is done to prevent the ROLLBACK from undoing outstanding updates if the DDL fails. However, the consequence is that the DDL statement commits outstanding updates – even if the DDL statement fails.