RMAN Catalog Merge [message #463068] |
Tue, 29 June 2010 10:22 |
harshad.gohil
Messages: 157 Registered: April 2007 Location: USA
|
Senior Member |
|
|
DB : 10.2.0.4
OS : Sun Solaris 5.8
Hello Folks,
In our environment, we have one rman catalog database and under that we few catalog schemas. I am planning to merge all those schema into one existing schema.
For eg. Diff RMAN Schema RMAN, RMAN1, RMAN2, RMAN3
Merge it from RMAN1, RMAN2, RMAN3 to RMAN.
My Action plan for this situation is
1> Take Export of all schemas
2> Re-Register respected databases (from RMAN1, RMAN2, RMAN3) to RMAN.
3> Modify backup scripts points to correct schema (i.e. RMAN).
Question for my clarification
1> Do I needs to de-register from previous catalog schemas ?
2> If I need to restore my db's after this process, from where RMAN get that information as I have new catalog and this catalog does not contain any previous backup information ??
Unfortunately we are not on 11g yet, In case of 11g we have command for IMPORT CATALOG.
What's a best options for this scenario ? Thanks for your time.
|
|
|
|
Re: RMAN Catalog Merge [message #463264 is a reply to message #463135] |
Wed, 30 June 2010 07:55 |
harshad.gohil
Messages: 157 Registered: April 2007 Location: USA
|
Senior Member |
|
|
Reason for merge is to migrate catalog from one database to another database. We are planning to combine OEM and RMAN repository, before doing that we want to merge RMAN catalog so by that way we can easily pull RMAN report from one schema instead of getting it from 15 different schemas.
What implication you see by merging it to one?
|
|
|
Re: RMAN Catalog Merge [message #463274 is a reply to message #463264] |
Wed, 30 June 2010 08:44 |
|
Mahesh Rajendran
Messages: 10708 Registered: March 2002 Location: oracleDocoVille
|
Senior Member Account Moderator |
|
|
>>What implication you see by merging it to one?
As said, there are specific reasons, depending on your business/shop.
Nothing generic.
It my case, I backup many database and duplicate/restore them much more times and use separate catalog for backup/restore/duplication.
One advantage is can just upgrade the specific catalog, instead of all.
Since no native methods are available to merge in 10g, I would not try it in a production environment.
The only other option is to unregister and register back. I would also leave the other catalog just intact for a while.
|
|
|