Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> [oracle-l] Re: rman catalog considerations

[oracle-l] Re: rman catalog considerations

From: DENNIS WILLIAMS <DWILLIAMS_at_LIFETOUCH.COM>
Date: Fri, 23 Jan 2004 16:11:30 -0600
Message-ID: <0186754BC82DD511B5C600B0D0AAC4D607AFFDD0@EXCHMN3>


Daniel

  1. Yes, I would consider separate instances for RMAN catalog. This will give you more flexibility.
  2. Consider not using a catalog. Oracle9i beefed up the non-catalog features. I have used the catalog mode for several years and in the way I've used RMAN I don't feel it has been worth the trouble. This is heresy to some on this list, so I'll probably get flamed, but I'm just saying to consider it in your situation.

Dennis Williams
DBA
Lifetouch, Inc.
dwilliams_at_lifetouch.com

-----Original Message-----
From: Daniel Hanks [mailto:hanksdc_at_about-inc.com] Sent: Friday, January 23, 2004 3:33 PM
To: oracle-l_at_freelists.org
Subject: [oracle-l] rman catalog considerations

I'm in the process of revamping my backup procedures, and had some ideas I wanted to filter through the wisdom/experience of the list.

In my current setup, I have two main database machines, let's call them M1, and M2.

So essentially M1 hosts the recovery catalog for the databases on M2, and likewise M2 hosts the recovery catalog for the database on M1.

My question is, would it be prudent/beneficial to put the recovery catalogs into their own schemas in the 'business' instances, instead of maintaining them in their own instances?

Some benefits I see in doing this:

Some drawbacks to doing this:

Thanks for your thoughts and suggestions,

Received on Fri Jan 23 2004 - 16:11:30 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US