RE: Duplicate DBIDs

  • From: "Schauss, Peter" <peter.schauss@xxxxxxx>
  • To: "Oracle-L (E-mail)" <oracle-l@xxxxxxxxxxxxx>
  • Date: Wed, 26 Jan 2005 16:49:02 -0500

I am running

The DBID is not an issue for my rman backups since I am using
the individual database control files to store the backup metadata.
(Yes, I do backup my control files.)

Peter Schauss

-----Original Message-----
From: Nick Tilbury @ Northampton [mailto:ntilbury@xxxxxxxxxxxx]
Sent: Wednesday, January 26, 2005 11:32 AM
To: rlsmith@xxxxxxx; Schauss, Peter; Oracle-L (E-mail)
Subject: RE: Duplicate DBIDs

We also had a similar issue. Which version of Oracle are you on ?
Renaming the database will not change it's DBID, but it can be done by =
executing a procedure
(the name of which escapes me for now).
8i databases having the same DBID did cause us some problems. However =
since upgrading to
9i, using RMAN duplicate database feature (which does change the DBID) =
we have had no problems.

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of Smith, Ron L.
Sent: 26 January 2005 16:23
To: peter.schauss@xxxxxxx; Oracle-L (E-mail)
Subject: RE: Duplicate DBIDs

You are already going through the edit on the controlfile.  Why not just
rename the database at the same time?
If not someone will surely mess up your production database, thinking
they are connected to the test version.


-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Schauss, Peter
Sent: Wednesday, January 26, 2005 10:12 AM
To: Oracle-L (E-mail)
Subject: Duplicate DBIDs

We have had a practice at our site of creating development and staging
databases by copying a cold backup to another system. We then edit the
output from "backup controlfile to trace" to rename the =3D3D

database and relocate the data files and restart
the database with the resulting script.  This means that a number of our
databases, mostly on different machines, have the same DBID. So far this
has not caused us any problems.  Are we running any risks here?

Peter Schauss

Important Notice!!
If you are not the intended recipient of this e-mail message, any use, =
distribution or copying of the message is prohibited.
Please let me know immediately by return e-mail if you have received =3D
this message by mistake, then delete the e-mail message.
Thank you.

This message is intended solely for the use of the individual or =
organisation to whom it is addressed.  It may contain privileged or =
confidential information.  If you have received this message in error, =
please notify the originator immediately.  If you are not the intended =
recipient, you should not use, copy, alter, or disclose the contents of =
this message.  All information or opinions expressed in this message =
and/or any attachments are those of the author and are not necessarily =
those of VarTecTelecom Europe Ltd or its affiliates. VarTec Telecom =
Europe Ltd accepts no responsibility for loss or damage arising from its =
use, including damage from virus.=20


Other related posts: