To return the values changed by a transaction to their original state.
Undo any changes to data that have been performed by SQL statements within an uncommitted transaction. After a transaction has been committed, it cannot be rolled back. Oracle uses rollback segments to store old values. The redo log contains a record of changes. See Also: commit, transaction, rollback segment
The process of restoring data changed by SQL statements to the state at its last commit point.
With unit of work support, the application program can also roll back changes to a unit of work. If a unit of work is rolled back, the changes made since the last commit or rollback operation are not applied. Thus, the application program treats the set of requests to a database as a unit.
The act of undoing the changes made to a database in a database transaction. Contrast with commit.
To cancel all the database actions within one transaction.
To remove the updates performed by one or more partially completed transactions. Rollbacks are required to restore the integrity of a database after an application, database, or system failure.
To cancel changes to a database since the point at which changes were last committed.
You can roll back a view to a past state based on a label, promotion state, or a point in time. For example, you might want to: Ø Take a quick look at how things were when the Beta3 label was applied Ø Recover an item that has been deleted by rolling back the view to a date before the item was deleted However, this “freezes” the view until you change its configuration back to current or close the project (which automatically changes the configuration back to current). You cannot check in files, update change requests, etc. because you cannot change the past.
To cancel any changes to a database made during the current transaction. Compare with commit.
