Professional Documents
Culture Documents
inShare
HOT BACKUP
1. Taking the backup while the database is up and running is called hot backup.
2. During hot backup database will be in fuzzy state and still users can perform transactions which makes
backup inconsistent.
5. During hot backup, we will observe much redo generated because oracle will copy entire data block as
redo entry into LBC. This is to avoid fractured block.
6. A block fracture occurs when a block is being read by the backup, and being written to at the same
time by DBWR. Because the OS (usually) reads blocks at a different rate than Oracle, your OS copy
will pull pieces of an Oracle block at a time. What if the OS copy pulls half a block, and while that is
happening, the block is changed by DBWR? When the OS copy pulls the second half of the block it will
result in mismatched halves, which Oracle would not know how to reconcile.
7. This is also why the SCN of the datafile header does not change when a tablespace enters hot backup
mode. The current SCNs are recorded in redo, but not in the datafile. This is to ensure that Oracle will
always recover over the datafile contents with redo entries. When recovery occurs, the fractured
datafile block will be replaced with a complete block from redo, making it whole again.
Note: Database should be in archivelog mode to perform hot backup.