A transaction is logical piece of work consisting of one or more SQL statements. A transaction is started whenever data is read or written and they are ended by a COMMIT or ROLLBACK. DDL statements always perform a commit first this is called an implicit commit this is because the user did not issue the commit.
Oracle uses transaction locking and multiversion concurrency control using undo records to ensure serializability in transactions, this stops any user conflicts while ensuring database consistency.
Database transactions should exhibit attributes described by the ACID properties:
Transaction Concurrent Control
Oracle uses locking to ensure data consistency but the locking is done via the least restrictive fashion, with the goal of maintaining the maximum amount of concurrency.
Concurrency problems can be any of the following
|Occurs when a transaction reads data that has been updated by an ongoing transaction but has not been committed permanently to the database, it is possible that the transaction may be rolled back.
|Are caused by the appearance of new data in between two database operations in a transaction.
|Is caused by transactions trying to read data while it is being updated by other transaction.
|When a transaction finds data that it has read previously has been modified by some other transaction, you have a non-repeatable-read or fuzzy read. Basically when you read data at one time and its different when you read it again.
To overcome the above problems you could serialize all the transactions making sure that data is consistent, however this does not scale well. Oracle serializes the transaction via isolation levels and the management of undo data.
The main isolation levels are the following
|Then transaction will lock all the tables it is accessing to prevent other transactions updating data until it either rollbacks or commits
|A transaction that reads the data twice from a table at different points in time will find the same values each time. Both dirty reads and non-repeatable are avoided with this level of isolation.
|Allows a transaction to read another transaction's immediate value before it commits
|Guarantees that the row data won't change while you're accessing a particular row in a table.
Oracle uses locks and multiversion concurrency control system, it uses row-level locking (it never uses lock escalation), it will automatically place the lock for you and store the lock information in the data block, locks are held until the transaction is either committed or rolled back. Multiversion concurrency is a timestamp approach to read the original data, oracle will write the original data to a undo record in the undo tablespace, queries then have a consistent view of the data which provide read consistency- they only see data from a single point in time, for more information see Oracle locking.
There are a number of different locks in Oracle and tables that can obtain information regarding locks.
|Oracle uses row-level locks, this is to protect the row while its being changed, the lock will never block a reader of the same row. A table lock is also placed but this ensures that no DDL is used on the table.
|When changing table attributes Oracle places a exclusive lock on the table to prevent any modifications to the rows. This lock is also used during DML transactions to make sure the table is not changed when changing or inserting data.
|Latches protect the memory structure with the SGA, they control the processes that access the memory area's.
|Are used by oracle to protect access to structures such as data files, tablespaces and rollback segments.
|Are specialized locking mechanisms used in distributed systems.
|Occurs when a lock is placed on an object by a user to prevent other users accessing the same object.
|Occurs when two sessions block each other while each waits for a resource that the other session is holding. Oracle always steps in to resolve the issue by killing one of the sessions, check the alert.log for deadlocks.
|lists all locks or latches held in the database, and all outstanding requests for a lock or latch
|shows all the sessions that are waiting for a lock
|displays a session if it is not waiting for a locked object but is holding a lock on an object for which another session is waiting
|This view lists the locks currently held by the Oracle Database and outstanding requests for a lock or latch
This view lists session information for each current session
See Oracle Locking for more information.
Integrity Constraints and Transaction
See constraints for more information about deferable and immediate constraints.
You can create a transaction within a transaction that will rollback independently of its parent transaction. They can be used in the following
create or replace procedure autonomous_example
The pragma directive tells oracle that this is a new autonomous transaction and that it is independent from its parent.
A trigger cannot contain a commit or rollback statement, however by using autonomous transactions you can overcome this limitation, it is considered bad practice but it is possible.
|Trigger with a commit
create table tab1 (col1 number);
create trigger test_trig
SQL> insert into tab1 values (1);
|Overcome commit problem
create or replace trigger test_trig
Undo data provides read consistency, there are two ways to control the undo manual or automatic. see undo data for more details
Simple Oracle transaction
Note: if the users transaction was an update then the before update row would have been written to the undo buffer cache, this would be used if the user rolls back the change of if another user run's a select on that data before the new update was committed.