No question at this time
DBA Top 10
1 M. Cadot 15900
2 B. Vroman 15500
3 A. Kavsek 10000
4 T. Boles 6800
5 J. Schnackenberg 5800
6 M. Hidayathullah ... 3900
7 P. Wisse 1800
8 T. P 700
9 B. Derous 500
9 R. Wauben 500
9 H. Steijntjes 500
About
DBA-Village
The DBA-Village forum
Forum as RSS
as RSS feed
Site Statistics
Ever registered users48209
Total active users1645
Act. users last 24h6
Act. users last hour0
Registered user hits last week186
Registered user hits last month812
Go up

Schedule RMAN backup using Recovery Catalog(Primary & Physical STDBY)
Next thread: RAC cluster down
Prev thread: Oracle11g (11.2.0.4) RAC on Standard Edition 11.2.0.4

Message Score Author Date
Hello Everyone... We are using RMAN recovery ca...... raghavendra rao yella Jun 05, 2018, 21:46
Any thoughts on this Guys?... raghavendra rao yella Jun 06, 2018, 15:26

Follow up by mail Click here


Subject: Schedule RMAN backup using Recovery Catalog(Primary & Physical STDBY)
Author: raghavendra rao yella, United States
Date: Jun 05, 2018, 21:46, 16 days ago
Os info: Solaris 5.11
Oracle info: 11.2.0.3
Message: Hello Everyone...

We are using RMAN recovery catalog to backup our production instances... recovery catalog schema is on one of the remote databases in one of our data centers... but recently we have been coming across Backup's failures as a result of 'LOST CONNECTIVITY to Recovery Catalog database'. Tried sqlnet.expire_time, increasing firewall threasholds but nothing worked...

As such I created a recovery catalog on one of the local production database(this database has two instances PRIMARY/PHYSICAL STANDBY replicated using Data Guard)

We use OEM 12c to schedule all our backup's.
Now when I'm registering the production database that needs backup.. i'm coming across two hosts for recovery catalog(one primary and 2nd one is physical standby) which looks correct.. as recovery catalog database has primary/physical standby.
Currently i pointed recovery schema to the one on Primary database.

We perform data center swings every alternative months...
MY Question is -
so next time when we swing.. do we need to manually update the recovery catalog settings of our production instance to point the current primary database which hosts recovery catalog or does it change automatically?

Any suggestions?

Note#
All our productions instances are Dataguard replicated...
I don't want to use NON-PRODUCTION database to host RMAN catalog schema.. as such was using one of the production instance to host RMAN RECOVERY CATALOG SCHEMA.

Thanks for your valuable suggestions in advance...
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: Schedule RMAN backup using Recovery Catalog(Primary & Physical STDBY)
Author: raghavendra rao yella, United States
Date: Jun 06, 2018, 15:26, 15 days ago
Message: Any thoughts on this Guys?
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here