I do a lot of cloning and I use the set database (newname) resetlogs
noarchivelog option when recreating the controlfile for the cloned
(target) database. It is my understanding that the set command sets the
new pointers to this controlfile because you have a new name for the
database, you will have a new incarnation (resetlogs). The noarchivelog is
simple to state that this database will override the logs whenever there
is a log switch. No archiving will be required.

The reuse clause will be used if you had lost all control files for the
same database and therefore you did not have to change the name, etc. You
do not necessarily have to use resetlogs, except your logs are not in sync
and you want to reinitialize and start from 0. If your database is
initially in archivelog mode then you leave it that way. My two cents.
Sabina.




"Dustin Hayden " <oracledba-ezmlmshield-x52229852.[Email address protected]

11/01/2005 12:21 PM

To
"LazyDBA Discussion" <[Email address protected]
cc

Subject
set and reuse set






Can someone please explain the difference between the using the following?



Create control file set database "NAME" resetlogs noarchive log

And

Create control file reuse set database "NAME" resetlogs noarchive log





TIA

Dustin





--------
website: http://www.LazyDBA.com
Please don't reply to RTFM questions
Oracle documentation is here: http://tahiti.oracle.com
To unsubscribe: see http://www.lazydba.com/unsubscribe.html
To subscribe: see http://www.lazydba.com
By using this list you agree to these terms:
http://www.lazydba.com/legal.html



Oracle LazyDBA home page