Catalog each other???

[Prettyman]

When two or more databases are backed up using RMAN, is it appropriate to use each database as the other's recovery catalog? Why?

A. Yes. The catalog is a recognized procedure
B. No. There would be too many dependencies
C. Yes, but only if the database are run in NOARCHIVELOG mode
D. No. A database that contains a catalog cannot be target database

Provide right answer please! Tend to select A, I think nothing voilates.

[Prettyman]

Anyone help me?

[Prettyman]

Got answer now, it is A. An example in Oracle online book

[dsimpson]

You can do it this way, and I have done so. But you need to make sure that the account name owning the catalog is unique amoung your servers - otherwise Oracle gets confused.

For production environments I generally like to set up a separate server just for OEM/OMS containing the RMAN catalog. Here is a diagram of this type of setup:

http://www.dotcomsolutionsinc.net/pr...ol901_42_.html

I have an application named Installgen which automates creating backup/recovery scripts along with creating the documentation for performing 15 different database recovery scenarios.

You may download a demo version of Installgen so that you may conveniently look at or modify the scripts on your own computer:
http://www.dotcomsolutionsinc.net/do...are/index.html

David Simpson
http://www.dotcomsolutionsinc.net