Home >> FAQs/Tutorials >> Oracle Tutorials
Oracle Tutorials - What Is a READ ONLY Transaction
(Continued from previous topic...)
What Is a READ ONLY Transaction?
A READ ONLY transaction is a transaction in which the read consistency is set at the transaction level.
In a READ ONLY transaction, a logical snapshot of the database is created at the beginning of the transaction
and released at the end of the transaction. This guaranties that all reads in all statements within this transaction
get consistent data from the database.
For example, if you have a transaction with many statements that takes 10 hours to be executed, a snapshot of the database
will be created for this transaction for 10 hours. If a query statement is executed at the beginning of the transaction
and at the end of the transaction, it will return the same result guarantied.
In another word, data changes made during this 10 hours by other users will not impact
the execution of statements within this transaction.
(Continued on next topic...)
- What Is a Transaction?
- How To Start a New Transaction?
- How To End the Current Transaction?
- How To Create a Test Table for Transaction Testing?
- How To Commit the Current Transaction?
- How To Rollback the Current Transaction?
- What Happens to the Current Transaction If a DDL Statement Is Executed?
- What Happens to the Current Transaction If the Session Is Ended?
- What Happens to the Current Transaction If the Session Is Killed?
- How Does Oracle Handle Read Consistency?
- What Is a READ WRITE Transaction?
- What Is a READ ONLY Transaction?
- How To Set a Transaction To Be READ ONLY?
- What Are the Restrictions in a READ ONLY Transaction?
- What Are the General Rules on Data Consistency?
- What Are Transaction Isolation Levels Supported by Oracle?
- What Is a Data Lock?
- How Data Locks Are Respected?
- How To Experiment a Data Lock?
- How To View Existing Locks on the Database?
- What Is a Dead Lock?
- How Oracle Handles Dead Locks?