Oracle-L: RE: rman duplicate dbid?

From: DENNIS WILLIAMS <DWILLIAMS_at_LIFETOUCH.COM>
Date: Thu, 30 May 2002 09:13:40 -0800
Message-ID: <F001.0046FCF8.20020530091340@fatcity.com>

Bill - Glad that method of changing the db_id worked for you. The advantages I see for separate RMAN catalogs are:

If you need to upgrade the target database, you can do that without affecting the other databases. For example, if the upgrade requires a change to the catalog schema, you can just change it for that database without worrying about it affecting the other databases.
If you bollix up the catalog, in the worst case you clear it out and start fresh. You probably limit the damage to a single schema/target database.
In the development scenario, databases come and go. I can't recall an RMAN command like "delete all traces of a database". But you can export and drop the schema.
You may decide to relocate the catalog for a database to another instance and/or host. Separate catalogs give you this flexibility.
My systems people like the philosophy of a backup tape(s) containing everything you need to recreate the system. I can run the backup to disk, export the RMAN catalog schema and FTP it over to the target system before tape backup starts, so everything winds up on a single tape. Now I just need to prove that I can mount that tape on another system and get the database going again.
As a novice, it may be easier to review the schema tables, and if you decide to clean out some records, it is simpler. I haven't seen any downsides to having multiple catalogs, but would appreciate if anybody knows of any. Dennis Williams DBA Lifetouch, Inc. dwilliams_at_lifetouch.com

-----Original Message-----

Sent: Thursday, May 30, 2002 11:51 AM
To: Multiple recipients of list ORACLE-L

found a note on metalink about how to change the dbid by recreating the controlfile (note 174625.1) . . . one of those notes with the lovely disclaimer about how the script is not supported by Oracle support, done at your own risk, don't try this on a production db, etc. . . .

anyway, it worked just fine and I was able to register the second db in the catalog.

why would it give me more flexibility to use a separate catalog for each prod database? (also, we're a dev shop - only db's in use here are for app dev and qa)

any and all thoughts are appreciated

-----Original Message-----

Sent: Thursday, May 30, 2002 12:11 PM
To: Multiple recipients of list ORACLE-L

Bill

Perhaps you created one by cloning it from the other one. This can change the SID, but won't change the DB_ID. RMAN can't deal with multiple instances with the same DB_ID. The simplest way around this is to create a separate RMAN catalog for one of them (just create a separate username). Actually, I'm becoming convinced that maybe the way to go is to create a separate catalog for each production database. This gives you more flexibility, and I haven't seem any disadvantages to this. Dennis Williams
DBA
Lifetouch, Inc.
dwilliams_at_lifetouch.com

-----Original Message-----

Sent: Thursday, May 30, 2002 9:59 AM
To: Multiple recipients of list ORACLE-L

I'm just starting to set up RMAN (8.1.7+) . . . I'm registering all of my databases one by one from the command line. I have two db's on the same solaris box and when I run the rman command they both show up with the same DB_ID, thus preventing me from registering both of them . . . I get an error when registering the second that it's already registered.

they are distinct db's . . .

I tried unregistering one and then retrying, and again I get the same DBID for both.

any ideas?

thanks, y'all

-bill
--

Please see the official ORACLE-L FAQ: http://www.orafaq.com
--

Author: Magaliff, Bill
INET: Bill.Magaliff_at_lendware.com

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists


--------------------------------------------------------------------

To REMOVE yourself from this mailing list, send an E-Mail message

to: ListGuru_at_fatcity.com (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).
--

Please see the official ORACLE-L FAQ: http://www.orafaq.com
--

Author: DENNIS WILLIAMS
INET: DWILLIAMS_at_LIFETOUCH.COM

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists


--------------------------------------------------------------------

To REMOVE yourself from this mailing list, send an E-Mail message

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists


--------------------------------------------------------------------

To REMOVE yourself from this mailing list, send an E-Mail message

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists


--------------------------------------------------------------------

To REMOVE yourself from this mailing list, send an E-Mail message