External failure-database recovery and security, Database Management System

External failure: A failure can also result because of an external cause, such as earthquakes, fire, floods, etc. The database must be duly backed up to avoid troubles occurring due to such failures.

In practice software failures are more ordinary than hardware failures.  Fortunately, recovery from software failures is much faster.

The essential unit of recovery is a transaction. But, how are the transactions can handle during recovery? Let some transactions are deadlocked, then at least one of these transactions has to be start again to break the deadlock and therefore the partial updates made by such restarted program in the database require to be undone so that the database did not go to an inconsistent state. So the transaction must roll back which makes sure that the transaction does not bring the database to an inconsistent state. This is one type of recovery. Let us take a case when a transaction has committed but the alteration made by the transaction has not been communicated to permanently store physical database. A software failure now happens and the contents of the RAM / CPU are lost. This remains the database in an inconsistent state. Such failure needs that on restarting the system the database be brought to a consistent state by using redo operation. The redo operation needs the changes made by the transaction again to bring the system to a consistent state. The database system then could be made available to the users. The main point here is that the database updates are performed in the buffer in the memory. Figure shows some cases of redo and undo. You can make more such cases.

                               511_External failure.png

 

Physical

Database

RAM

Activity

Case 1

A=6000

B=8000

A=4000

B=8000

Transaction T1 has just changed the value in RAM. Now it aborts, value in RAM is lost. No problem. But we are not sure that the physical database has been written back, so must undo.

Case 2

A=4000

B=8000

A=4000

B=8000

The value in physical database has got updated due to buffer management, now the transaction aborts. The transaction must be undone.

Case 3

A=6000

B=8000

A=4000

B=10000

Commit

The value B in physical database has not got updated due to buffer management. In case of failure now when the transaction has committed. The changes of transaction must be redone to ensure transfer of correct values to physical database.

                                                    Figure: Database Updates and Recovery

Posted Date: 3/12/2013 3:36:57 AM | Location : United States







Related Discussions:- External failure-database recovery and security, Assignment Help, Ask Question on External failure-database recovery and security, Get Answer, Expert's Help, External failure-database recovery and security Discussions

Write discussion on External failure-database recovery and security
Your posts are moderated
Related Questions

List some security violations (or) name any forms of malicious access. A) Unauthorized reading of data B) Unauthorized modification of data C) Unauthorized destruction of


Differentiate between logical database design and physical database design. Show how this separation leads to data independence? Basis Logical Databas

Where does view definition stored? A view definition is permanently stored as part of the database.

Define average latency time. The average latency time of the disk is one-half the time for a full rotation of the disk.

Depending upon the rules we have found, we can classify the locks into two types. Shared Lock: A transaction might be acquiring shared lock on a data item in order to read it

Prepare Heart Failure Registry database How are you today? Please I would like you to design a Heart Failure registry where doctors will log in to enter information about their


What will be create when a primary key if combined with a foreign key? A primary key if combined with a foreign key it creates Parent-Child relationship between the tables that