You are not quite correct. While the tablespace is in hot backup mode, the
change number of the blocks are frozen. Changes are still applied to the
blocks and redo is still generated (Oracle does not "save up" all the
changes during the backup and then replay them at the end -- otherwise your
database query results would be quite stale). At the end of the backup, the
change numbers are updated, but the actual row changes have already taken
place as they would any other time. The reason the hot backup works is
because if you restored the files backed up during the hot backup, the
change number would be at the point of the beginning of the backup and then
normal recovery with redo logs can take place.
Received on Wed Aug 08 2001 - 01:38:37 CDT
