Just want to confirm Mark's suggestion. We use "nid" in our scripts for restores from our production backups every week several times and works like a charm. Small note to avoid headache - be sure that user running "nid" from script/command line has rw access to datafiles and controlfiles. Don't remember if it was mentioned already but in order to restore from the same backup more than once at the same time lock_name_space can be used. The same applies to restoring to the same host where original instance is running (though, that's not my slyle).
2005/11/12, Mark Bole <makbo@(protected)>: > There is another alternative. The DBNEWID utility allows one to change > the dbname and/or dbid of an existing database (in your case the copy of > the existing database). The actual executable name is "nid" under Unix > or "nid.exe" under Windows.
-- Best regards, Alex Gorbachev -- http://www.freelists.org/webpage/oracle-l
