Transaction control and isolation levels in Oracle. Evgeniya Kotzeva. Vereo Technologies www.vereo.bg. academy . devbg . org. www.devbg.org. Contents. Transaction control Data Concurrency and Consistency in a Multiuser Environment Locking. Database Transaction.
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
A database transaction consists of one of thefollowing:
A transaction ends with one of the following events:
A COMMIT or ROLLBACK statement is issued
A DDL or DCL statement executes (automatic commit)
The user exits iSQL*Plus
The system crashesTransaction boundaries
With COMMIT and ROLLBACK statements, you can:
generated rollback segment records in buffers in the SGA
generated redo log entries in the redo log buffer of the SGA.
The changes have been made to the database buffers of the SGA.
The internal transaction table for the associated rollback segment records updated with SCN
LGWR writes SGA redo log entries to the online redo log file
Oracle releases locks
Oracle marks the transaction complete.COMMIT transaction
Oracle undoes all transaction changes using the undo tablespace or rollback segments
Oracle releases all the transaction’s locks of data
The transaction ends
ROLLBACK to SAVEPOINT
Oracle rolls back only the statements run after the savepoint.
Oracle preserves the specified savepoint, but all savepoints that were established after the specified one are lost
Oracle releases all table and row locks acquired since that savepointROLLBACK transaction
The data returned by a single query comes from a single point in time — the time that the query began
When a transaction executes in serializable mode, all data accesses reflect the state of the database as of the time the transaction began
When commit or rollback has been executed, the pre-images can be overwritten even if they are needed to provide a read-consistent view to another query.
"Snapshot too old" simply means that pre-images which the query needs to maintain a read-consistent view have been overwritten.
Common recommendations to reduce the possibility of "snapshot too old" are:
(amount of committed undo information to retain in the database)
You can set the isolation level of a transaction by usingone of these statements at the beginning of a transaction:
The mode prevents the associates resource from being shared
The mode allows the associated resource to be shared, depending on the operations involved
Levels of locking