COMMIT

1.   COMMIT makes all DML changes permanent. Once a commit is issued, the changes done using INSERT, UPDATE, DELETE, or MERGE are permanently saved in the database.

2.   After COMMIT, the changes become visible to all other database sessions. Before commit, only the current session can see its own changes.

3.   COMMIT releases all row-level locks held by the transaction, allowing other users to access and modify the affected rows.

4.   Once changes are committed, they cannot be undone. ROLLBACK cannot reverse a committed transaction.

5.   If a COMMIT is not issued, the changes remain uncommitted and are not permanently saved in the database.

6.   Uncommitted changes can be undone using ROLLBACK, which restores the data to its previous committed state.

7.   Oracle does not auto-commit after DML statements. A manual COMMIT is required to save changes.

8.   Oracle performs an implicit commit before and after executing DDL statements such as CREATE, ALTER, and DROP.

9.   SELECT statements are read-only operations and do not require a COMMIT because they do not modify data.

10.  Each COMMIT ends the current transaction, and Oracle automatically starts a new transaction for subsequent DML operations.