Hi,
Can any one explain the reasons for performing log switch in hot backup, before putting the tablespace in backup mode and copyinh the corresponding data files. by using:
ALTER TABLESPACE BEGIN BACKUP;
.....
ALTER TABLESPACE END BACKUP;
Will be there be any problem, if I don't perform log switch before backing the datafiles?
One reason could be that if during the back stage/mode, if a desk crash or failure occurs, you can bring the db back in time just before the alter tablspc test begin backup; command!(by using the archive logs ofcourse).
Tarry
Tarry Singh
I'm a JOLE(JavaOracleLinuxEnthusiast)
--- Everything was meant to be---
When u put ur tablespace in hotback up mode,oracle will perform a checkpoint by writing all the modified blocks in the database buffer cache into the datafiles,advancing the SCN in the logfiles and datafile ,after this initial checkpoint,no further checkpoints will be written to datafiles.So the changes will be written to logfiles generating more redo till u end the backup.So i guess it really does not cause any issue if you dont switch logile.If at all u switch logfile before you take hotback up u will be writing into a fresh redolofile.
I hope i am write on this point.please correct me if i am wrong.
Anand,
you're right about the begin and endback up mode of the tablespace and how oracle stops chkpointing.
He's aking about log switching, so that the info can also be written to the offline redologs.(just in case!)
Cheers!!!
Tarry
Tarry Singh
I'm a JOLE(JavaOracleLinuxEnthusiast)
--- Everything was meant to be---
Usually people switch logs after the end backup to make sure they have all the redo generated during the backup.
Switching redo logs prior as well will not hurt. If you intend on NOT keeping the archives generated before the backup, then you should definetly do the switch.
Once you have eliminated all of the impossible,
whatever remains however improbable,
must be true.
Bookmarks