When you are copying an active datafile, the datafile contents may be changed while you are copying the data to your backup location. This means that your backup will be "inconsistent." The last part of the backup may contain newer transactions and the first part may contain older transactions. To solve this problem, you must be running in Archive Log mode so that Oracle can recover any transactions made while you were performing your backup.
While copying a block of a datafile, it is possible that the block may be inconsistent. This is called a "fractured block." It is possible that a row in that block may be inconsistent as well. Part of that row is old in your backup and part of the row is new in that backup. Oracle decided the best way to handle a fractured block is to write an image of that block to the archived redo log. On recovery, Oracle does not have to figure out which row is inconsistent since it replaces the entire block.
Dizwell Informatics has some great information on this as well.
Dig Deeper on Oracle database backup and recovery
Related Q&A from Brian Peasland
Oracle expert Brian Peasland answers one reader's question about common pitfalls when connecting Oracle to outside programs. Continue Reading
One reader asks expert Brian Peasland a question about datafile sizes with the Oracle RMAN duplicate 10g command. Continue Reading
Managing parent table-child table relations in Oracle SQL environments is key to efficient programming. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.