Database Engineer
Whenever a structural change is made on the primary, attempts to resync from the primary using db_unique_name during the standby RMAN backups, it fails with following error.
Db-unique-name for all databases participating in the Data Guard configuration has been configured. Continue reading → ORA-20079: full resync from primary database is not done with ORA-17627, RMAN-20051
In this blog post, I will talk about how you can perform workload routing across the standby databases based on Database role with GDS. GDS provides this functionality without requiring Oracle Clusterware to be installed. But if clusterware is installed then GDS automatically register the global service to GI home. When role transition happens in Data Guard Broker configuration, GDS relocates the global services automatically as per the role attribute. There is no need to write custom logic or database startup triggers to achieve this behavior. Continue reading → Global Data Services (GDS) with Active Data Guard – High Availability
In the event of a planned/unplanned outage, how efficiently can user sessions be directed to a secondary site/ Database with minimal disruption is called seamless application failover. This can be achieved when database failover is facilitated by oracle data guard. Continue reading → Seamless Application Failover with Oracle Data Guard
The purpose of this blog is to guide you through configuring Oracle Data Guard Fast-Start Failover (FSFO) using Data guard broker with physical standby database.
Oracle Data Guard is one of the software solutions provided by Oracle Corporation to maximize high availability of Oracle databases. Oracle Data Guard maintains one or many secondary databases as alternatives to the primary production database. Continue reading → Oracle Data Guard 12cR1 with Data Guard Broker