If you name the clone the same name as the db being cloned, then rman won't change the dbid. After the clone is recovered, you just change the name to something else. Also I found that if you try to go back to a prior set of backupsets you will create the DBID problem too. I always use the latest backupsets and rename the clone to something other than the target. I am not sure this was what you are looking for but...
HTH,Ruth ----- Original Message ----- To: "Multiple recipients of list ORACLE-L" <[EMAIL PROTECTED]> Sent: Wednesday, September 18, 2002 2:18 PM Ok i hear people complain about the DBID issue when duplicating a database. Does this only occur when using OS utilities to do the duplication because the DBID can't be changed until 9ir2?, if you use the RMAN duplicate command, it appears it works ok, truth or fiction? thanks, joe -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Ruth Gramolini INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
