Try that the copy of the system tablespace will be the last file copied.
Also if you can make snapshoot and archivelog all before copying the
system tablespace. Since while cloning you create a new controlfile, you
need that all transaction come to end in the "last" archive file.
Another option is to do change-based recovery, while the last SCN will
be the last SCN in the last archive file (select first_change#-1,
sequence# from v$log_history, and take the SCN in the last file this is
the last SCN from the previous file).
HTH
Ofer
-----Original Message-----
From: Newbie-Slingshot
[mailto:oracledba-ezmlmshield-x78655547.[Email address protected]
Sent: Friday, October 06, 2006 6:18 AM
To: LazyDBA Discussion
Subject: ONLINE CONSISTENT HOT BACKUP - HOW
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 ...
---------------------------------------------------------------------
TO REPLY TO EVERYBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY To post a
dba job: http://jobs.lazydba.com To Subscribe : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
**********************************************************************
The information contained in this e-mail message may be
privileged and confidential. The information is intended only
for the use of the individual or entity named above. If the
reader of this message is not the intended recipient, you are
hereby notified that any dissemination, distribution or copying
of this communication is strictly prohibited. If you have
received this communication in error, please notify us
immediately by telephone, or by e-mail and delete the message
from your computer. Thank you!
Unless otherwise stated, any views or opinions expressed in
this e-mail are solely those of the author and do not represent those of
Barak I.T.C (1995) The International Telecommunications Services Corp. Ltd.
**********************************************************************
Oracle LazyDBA home page