SAVEPOINT statement names and marks the current point in the processing of a transaction. With the
TO statement, savepoints undo parts of a transaction instead of the whole transaction. For more information, see "Overview of Transaction Processing in PL/SQL".
SAVEPOINT statement can be embedded as static SQL in PL/SQL. For syntax details on the SQL
SAVEPOINT statement, see Oracle Database SQL Reference.
A simple rollback or commit erases all savepoints. When you roll back to a savepoint, any savepoints marked after that savepoint are erased. The savepoint to which you roll back remains.
You can reuse savepoint names within a transaction. The savepoint moves from its old position to the current point in the transaction.
If you mark a savepoint within a recursive subprogram, new instances of the
SAVEPOINT statement are executed at each level in the recursive descent. You can only roll back to the most recently marked savepoint.
An implicit savepoint is marked before executing an
DELETE statement. If the statement fails, a rollback to the implicit savepoint is done. Normally, just the failed SQL statement is rolled back, not the whole transaction; if the statement raises an unhandled exception, the host environment (such as SQL*Plus) determines what is rolled back.
For examples, see the following: