Hi all,

I have a 200GB+ database that I clone from time to time. Sometimes the
clone works and sometimes it doesn't and I have to apply archived logs
after logs and after logs until I have to give up. In most cases, this
happens because a batch job runs before the copy finishes. Does anyone
have a tried and tested way of making sure that a hot backup online copy
will always be consistent or at most maybe apply 5-10 archived logs and
then it becomes consistent? Any tips and tricks or scripts that anyone
from this FORUM uses will be very much appreciated.

FYI, this is how I do my hot backup:

1. Run ALTER DATABASE BACKUP CONTROLFILE TO TRACE
2. Create a list of tablespaces and append BEGIN BACKUP to the spool
file and run this file to place the tablespaces in backup mode.
3. Copy the datafiles using UNIX cp command. In some case, use scp to
copy to a remote directory
4. Copy the INIT file and the ORA password file
5. Create a list of tablespaces and append END BACKUP to the spool
file and run this file to take the tablespaces off backup mode.
6. Generate a list of archived logs that was generated during the
BEGIN and END backup and copy these archived logs as well.
7. Copy the REDOLOG files as sometimes the some log/s that needs to
be applied is/are in the REDOLOG.
8. On the TARGET server, modify the INIT.ORA file accordingly and
re-create the control files and startup the database. You may need
to apply archivelogs so that all datafiles will be consistent


Are my steps correct as above. I am including the TEMP tablespaces
during the copy as well as in some cases, this seems necessary and also
because it appears on the list of tablespace when I step 2.

Any advice or feedback will be very much appreciated. Thanks ...



Oracle LazyDBA home page