• From: "Bobak, Mark" <Mark.Bobak@xxxxxxxxxxxx>
  • To: "lawrence.wolfson@xxxxxxxxxx" <lawrence.wolfson@xxxxxxxxxx>, oracle_l <oracle-l@xxxxxxxxxxxxx>
  • Date: Thu, 26 Jun 2008 17:29:09 -0400


See Eric Grancher's comments in my blog before trying to use 11g catalog w/ 
10.2.0 target database.


Mark J. Bobak
Senior Database Administrator, System & Product Technologies
789 E. Eisenhower, Parkway, P.O. Box 1346
Ann Arbor MI 48106-1346
+1.734.997.4059  or +1.800.521.0600 x 4059

ProQuest...Start here.

From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On 
Behalf Of Wolfson Larry - lwolfs
Sent: Thursday, June 26, 2008 5:16 PM
To: oracle_l

Hi guys,
              I was wondering what advice you had on limiting and organizing 
DBs into different RMAN schemas.
            We've got a client with lots of DBs, who wants to move more to RMAN.

Unfortunately not everyone is proficient in RMAN to start with (I got elevated 
to #2 in proficiency, but don't be excited about that)
And we've had several cases where a DB was cloned and the DBID wasn't changed.
So I got to fix the Incarnations.

    We've also had problems where a DB was upgraded to 10G but the schema 
wasn't etc., etc.

    We've got 3 different RMAN catalog databases.  All
    Some have schemas with as many as 30 DBs being maintained.
    The DBs range from 8.1.6 to

    We've had a number of performance issues and earlier someone had split all 
the SAP DBs into their own.
There's at least a dozen of those. The other schemas are generally divided into 
specific releases and prod/dev/test.

    I've been thinking about not using catalogs for the dev & test DBs and just 
sticking with the control files.

    We want to create another RMAN DB and I thought we might as well go to 11G, 
but everyone is very leery about that.
I did like the new import feature in 11G.

    Suggestions and warnings welcome.
  Do have a copy of Note: 247611.1 Known RMAN Performance Problems


    Larry Wolfson


The information contained in this communication is confidential, is

intended only for the use of the recipient named above, and may be

legally privileged.

If the reader of this message is not the intended recipient, you are

hereby notified that any dissemination, distribution or copying of this

communication is strictly prohibited.

If you have received this communication in error, please resend this

communication to the sender and delete the original message or any copy

of it from your computer system.

Thank you.


Other related posts: