Mark Bole wrote:
You'll probably want to use "nid" in any event -- if you plan to use RMAN to backup both the original and the clone, at least. RMAN expected DBIDs to be unique, and it won't be one bit happy if they are not. Even if you don't happen to use RMAN today, having multiple databases with the same DBID laying around could be considered a "ticking time-bomb"...J. Dex wrote:
I know about Metalink Note 15390.1 [...]
[...]
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.
If you review the steps in the documentation (Data Guard Concepts) for creating a logical standby database you'll find it includes a subset of steps to accomplish what you are trying to do.
-- //www.freelists.org/webpage/oracle-l