1. Advanced Database Technologies Lecture 6: Transactions and Database Recovery

2. CG096 Advanced Database Technologies Lecture 6: Transaction Processing and Recovery 2 Content  What is a Transaction?  ACID properties  Transaction Processing  Database Recovery

3. CG096 Advanced Database Technologies Lecture 6: Transaction Processing and Recovery 3 1. What is a Transaction? Definition The sequence of a logically linked actions that access a shared database, usually on behalf of on-line users Examples Airlines operation: Reserve an airline seat. Buy an airline ticket. Assemble cabin crew. Fly. ATM Cash operation: Check credentials. Check money. Withdraw amount. Pay amount. Credit card sale: Log on the card. Verify credit card details. Check money. Handle. Issue withdrawal. Internet sale: Request an item from an on-line catalogue. Check availability. Provide credit card details. Check details. Issue order. Dispatch. Issue withdrawal.

4. CG096 Advanced Database Technologies Lecture 6: Transaction Processing and Recovery 4 Origin and Needs for Transactions in DB

5. CG096 Advanced Database Technologies Lecture 6: Transaction Processing and Recovery 5 Automated Teller Machines (ATM)

6. CG096 Advanced Database Technologies Lecture 6: Transaction Processing and Recovery 6 2. A.C.I.D. properties Transactions have 4 main properties u Atomicity - all or nothing u Consistency - preserve database integrity u Isolation - execute as if they were run alone u Durability - results aren’t lost by a failure

7. CG096 Advanced Database Technologies Lecture 6: Transaction Processing and Recovery 7 2.1 Atomicity All-or-nothing, no partial results. u E.g. in a money transfer, debit one account, credit the other. Either both debiting and crediting operation succeed, or neither of them do. u Successful completion is called Commit (Commit statement in SQL), unsuccessfull - Rollback (statement Rollback in SQL) u Transaction failure is called Abort Commit and abort are irrevocable actions. An Abort undoes operations that already executed u For database operations, restore the data’s previous value from before the transaction (Rollback-it); u But some real world operations are not undoable. Examples - transfer money, print ticket, fire missile

8. CG096 Advanced Database Technologies Lecture 6: Transaction Processing and Recovery 8 2.2 Consistency Every transaction should maintain DB consistency u Referential integrity - E.g. each order references an existing customer number and existing part numbers u The books balance (debits = credits, assets = liabilities) Consistency preservation is a property of a transaction, not of the database mechanisms for controlling it (unlike the A, I, and D of ACID) If each transaction maintains consistency, then serial executions of transactions do too.

9. CG096 Advanced Database Technologies Lecture 6: Transaction Processing and Recovery 9 2.3 Isolation Intuitively, the effect of a set of transactions should be the same as if they ran independently. Formally, an interleaved execution of transactions is serializable if its effect is equivalent to a serial one. Implies a user view where the system runs each user’s transaction stand-alone. Of course, transactions in fact run with lots of concurrency, to use device parallelism. Transactions can use common data (shared data) They can use the same data processing mechanisms (time sharing)

10. CG096 Advanced Database Technologies Lecture 6: Transaction Processing and Recovery 10 2.4 Durability When a transaction commits, its results will survive failures (e.g. of the application, OS, DB system … even of the disk). Makes it possible for a transaction to be a legal contract. Implementation is usually via a log u DB system writes all transaction updates to its log u to commit, it adds a record “commit(T i )” to the log u when the commit record is on disk, the transaction is committed. u system waits for disk ack before acking to user

11. CG096 Advanced Database Technologies Lecture 6: Transaction Processing and Recovery 11 3. Transaction Processing Identifying critical points for database changes through set of database states Preparation for the control over transaction progress using labels of the transaction states Management of the transactions using explicit manipulation of transaction states and enforcing transaction operations Can be automatic (controlled by the RDBMS) or programmatic (programmed using SQL or other supported programming languages, like PL/SQL)

12. CG096 Advanced Database Technologies Lecture 6: Transaction Processing and Recovery 12 3.1 Database State and Changes D 1, D 2 - Logically consistent states of the database data T - Transaction for changing the database t 1, t 2 - Absolute time before and after the transaction

13. CG096 Advanced Database Technologies Lecture 6: Transaction Processing and Recovery 13 Transaction Parameters diff D = D 2  D 1 can have different scale: u single data item in one memory area u many items across several files and databases u structural changes like new database schema, etc.  t = t 2 - t 1 is the time for executing T T occupies real physical resources u between D 1 and D 2 there may be intermediate states D 11, D 12 …; some of them can be inconsistent u the final state D 2 state could be unreachable When T fails u we should first come back to D 1 (recovery) u then try again to reach D 2 (redo)

14. CG096 Advanced Database Technologies Lecture 6: Transaction Processing and Recovery 14 Transaction Operations For recovery purposes the system needs to keep track of when a transaction starts, terminates and commits. begin: marks the beginning of a transaction execution; end: specifies that the read and write operations have ended and marks the end limit of transaction execution; commit: signals a successful end of the transaction. Any updates executed by the transaction can be safely committed to the database and will not be undone; rollback: signals that the transaction has ended unsuccessfully. Any changes that the transaction may have applied to the database must be undone; undo: similar to rollback but it applies to a single operation rather than to a whole transaction; redo: specifies that certain transaction operations must be redone to ensure that all the operations of a committed transaction have been applied successfully to the database;

15. CG096 Advanced Database Technologies Lecture 6: Transaction Processing and Recovery 15 Reading and Writing Specify read or write operations on the database items that are executed as part of a transaction read (X): reads a database item named X into a program variable also named X. 1. find the address of the disk block that contains item X 2. copy that disk block into a buffer in the main memory 3. copy item X from the buffer to the program variable write (X): writes the value of program variable X into the database 1. find the address of the disk block that contains item X 2. copy that disk block into a buffer in the main memory 3. copy item X from the program variable named X into its current location in the buffer 4. store the updated block in the buffer back to disk (this step updates the database on disk)

16. CG096 Advanced Database Technologies Lecture 6: Transaction Processing and Recovery 16 active partially committed aborted terminated BEGIN READ, WRITE END ROLLBACK COMMIT 3.2 Transaction State and Progress A transaction reaches its commit point when all operations accessing the database are completed and the result has been recorded in the log. It then writes a [commit, ] and terminates. When a system failure occurs, search the log file for entries [start, ] and if there are no logged entries [commit, ] then undo all operations that have logged entries [write,, X, old_value, new_value]

17. CG096 Advanced Database Technologies Lecture 6: Transaction Processing and Recovery 17 Logging transaction states Saving the initial database state D 1 before starting the transaction T: D 1 ->D 2 (transaction begins) Saving all intermediate states D 11, D 12 … (checkpoint logs) In the case of a failure at an intermediate state D 1i before reaching D 2, restore D 1 (rollback); the simplest strategy is to apply a series of atomic actions R which change the state to the initial state R: D 1i ->D 1 In the case of successful reach of the last intermediate state D 2, force-write or flush the log file to disk and change the database state to it (transaction ends); Note: if the transactions are controlled in SQL(using COMMIT), the rollback operation should be initiated explicitly (using ROLLBACK)

18. CG096 Advanced Database Technologies Lecture 6: Transaction Processing and Recovery 18 17 Entries in the log file [start, ]: the start of execution of the transaction identified by transaction-id [read,, X]: the transaction identified by transaction-id reads the value of database item X [write,, X, old- value, new-value]: the transaction identified by transaction-id changes the value of database item X from old- value to new-value [commit, ]: the transaction identified by transaction-id has completed all data manipulations and its effect can be recorded [rollback, ]: the transaction identified by transaction-id has been aborted and its effect lost Procedure Credit ( trans_id INTEGER, accno INTEGER, bcode CHAR(6), amount NUMBER) old NUMBER; new NUMBER; begin SELECT balance INTO old FROM account WHERE no = accno and branch = bcode; new := old + amount; UPDATE account SET amount = new WHERE no = accno and branch = bcode; COMMIT; EXCEPTION WHEN FAILURE THEN ROLLBACK; END credit;

19. CG096 Advanced Database Technologies Lecture 6: Transaction Processing and Recovery 19 Controlling Subtransactions All intermediate states of the transaction which are end states of the subtransactions included should become consistent database states In the case of successful reach of an intermediate state of such kind the actions are u temporary suspension of transaction execution u forced writing of all updated database blocks in main memory buffers to disk and flush the log file u resuming of transaction execution Note: If the transactions are controlled in SQL, the rollback operation can be stepped to an intermediate state which is labeled (using ROLLBACK TO )

20. CG096 Advanced Database Technologies Lecture 6: Transaction Processing and Recovery 20 Adding checkpoints to the log file A [checkpoint, ] record is created each time new checkpoint is encountered [commit, ] entries for the active subtransactions are automatically written when the system writes out to the database the effect of write operations of the successful transaction In the case of a rollback to a given checkpoint within a transaction an entry [commit, ] is logged against this subtransaction In the case of a rollback of the global transaction to a given checkpoint all subtransactions will not be committed either

21. CG096 Advanced Database Technologies Lecture 6: Transaction Processing and Recovery 21 4. Database Recovery Need for recovery from failure during transaction u for preventing the loss of data u to avoid global inconsistency of the database u to analyze the possible reasons for failure Factors to be accounted for database recovery: u what is the nature of the failure u when it happened in the transaction u what we need to recover

22. CG096 Advanced Database Technologies Lecture 6: Transaction Processing and Recovery 22 4.1 Categories of Transactions at Failure T 1 - Can be ignored (committed before the previous checkpoint) T 2 - Must Redo complete (the database will be rolled back to a state when the transaction was not committed) T 3 - Must Undo (not finished, and rollback to a state when not finished) T 4 - Must Redo if possible (finished, but not committed) T 5 - Must Undo (did not finish and the rollback will lead to a state before it was even started)

23. CG096 Advanced Database Technologies Lecture 6: Transaction Processing and Recovery 23 4.2 Types of Failure Catastrophic failure u Restore a previous copy of the database from archival backup u Apply transaction log to copy to reconstruct more current state by redoing committed transaction operations up to failure point u Incremental dump + log each transaction Non-catastrophic failure u Reverse the changes that caused the inconsistency by undoing the operations and possibly redoing legitimate changes which were lost u The entries kept in the system log are consulted during recovery. u No need to use the complete archival copy of the database. If an error or hardware/software crash occurs between the begin and end of transaction, the database will be inconsistent

24. CG096 Advanced Database Technologies Lecture 6: Transaction Processing and Recovery 24 4.3 Recovery Strategy Mirroring u keep two copies of the database and maintain them simultaneously Backup u periodically dump the complete state of the database to some form of tertiary storage System Logging u the log keeps track of all transaction operations affecting the values of database items. The log is kept on disk so that it is not affected by failures except for disk and catastrophic failures.

25. CG096 Advanced Database Technologies Lecture 6: Transaction Processing and Recovery 25 Deferred Update: u no actual update of the database until the transaction reaches its commit point 1. Updates recorded in log 2. Transaction commit point 3. Force log to the disk 4. Update the database Immediate Update: u the database may be updated by some operations of a transaction before it reaches its commit point. 1. Update X recorded in log 2. Update X in database 3. Update Y recorded in log 4. Transaction commit point 5. Force log to the disk 6. Update Y in database FAILURE! REDO database from log entries No UNDO necessary because database never altered FAILURE! UNDO X FAILURE! REDO Y FAILURE! UNDO in reverse order in log REDO in committed log order (uses the write log entry) Write-ahead Logging