The same way any other recovery is done -- archived logs are used to bring
the restored datafile back to the current SCN. It is not a "requirement"
that hot backups be done a tablespace at a time. The reason you might want
to do it is to reduce the overhead associated with the hot backup. Placing
a tablespace in hot backup mode causes more redo to be generated for blocks
in that tablespace (full blocks are written to the redo logs). If you have
a highly active database you might have a problem putting all tablespaces in
backup mode and waiting for all files to be backed up. However, I have
worked with many databases where this was not a problem. It just depends on
how busy the database is and how long your backups take.
Received on Sun Aug 26 2001 - 16:54:59 CDT
