Oracle Data Guard on Oracle Cloud Infrastructure (OCI)



Setting up Oracle Data Guard on Oracle Cloud Infrastructure (OCI) involves several steps to ensure data protection and disaster recovery for Oracle databases. Below is a high-level overview of the process:

1. Prerequisites and Preparation

  • Oracle Database Versions: Ensure that both the primary and standby databases are running supported Oracle Database versions.
  • OCI Setup: You need an OCI tenancy with necessary permissions, VCNs (Virtual Cloud Networks), and subnets configured.
  • Networking: Ensure the network configuration allows communication between the primary and standby instances.
  • Access: SSH access to the database servers and Oracle Cloud Console access are required.

2. Prepare the Primary Database

  • Configure Archiving: Enable archive log mode and set up the archive destination.
  • Configure Initialization Parameters: Set necessary initialization parameters like DB_NAME, DB_UNIQUE_NAME, LOG_ARCHIVE_CONFIG, LOG_ARCHIVE_DEST_n, FAL_SERVER, etc.
  • Create a Backup: Take a backup of the primary database using RMAN (Recovery Manager) or another method.

3. Provision the Standby Database

  • Create a Compute Instance: Launch a new compute instance in OCI to host the standby database.
  • Install Oracle Database Software: Install the same version of Oracle Database as the primary.
  • Network Setup: Ensure network configurations (e.g., security lists, route tables) allow communication between the primary and standby instances.

4. Set Up Data Guard Configuration

  • Copy the Backup: Transfer the primary database backup to the standby server.
  • Restore and Configure Standby: Restore the backup on the standby server and set up the database.
  • Configuration Files: Copy the listener.ora and tnsnames.ora files to the standby server and configure them appropriately.

5. Enable Data Guard Broker (Optional but Recommended)

  • Configure Broker: Set up the Data Guard Broker on both primary and standby databases. This simplifies management and monitoring.
  • Start Broker: Enable the Data Guard Broker and start the Data Guard configuration.

6. Testing and Monitoring

  • Validate Setup: Verify that the Data Guard setup is working correctly by checking the status and performing role switch tests.
  • Monitoring: Regularly monitor the Data Guard environment using tools like Oracle Enterprise Manager or the Data Guard command-line interface (DGMGRL).

7. Management and Maintenance

  • Switchovers and Failovers: Practice performing switchover and failover operations to ensure readiness in case of a disaster.
  • Patching and Upgrades: Keep the databases patched and upgraded following Oracle’s best practices.

Example Commands and Configuration Files

Primary Database Initialization Parameters:


ALTER SYSTEM SET LOG_ARCHIVE_DEST_2='SERVICE=standby_db SYNC AFFIRM' SCOPE=BOTH;
ALTER SYSTEM SET LOG_ARCHIVE_CONFIG='DG_CONFIG=(primary_db,standby_db)' SCOPE=BOTH;

Standby Database Initialization Parameters:


FAL_SERVER=primary_db
FAL_CLIENT=standby_db

Data Guard Broker Configuration:


DGMGRL> CREATE CONFIGURATION 'DG_Config' AS PRIMARY DATABASE IS 'primary_db' CONNECT IDENTIFIER IS 'primary_db';
DGMGRL> ADD DATABASE 'standby_db' AS CONNECT IDENTIFIER IS 'standby_db' MAINTAINED AS PHYSICAL;
DGMGRL> ENABLE CONFIGURATION;

Comments

Post a Comment

Popular posts from this blog

Creating Physical Standby using RMAN Duplicate Without Shutting down The Primary

Oracle Server - Enterprise Edition - Version: 10.1.0.2 to 10.2.0.4 - Release: 10.1 to 10.2 Information in this document applies to any platform. Oracle Server Enterprise Edition - Version: 10.2.0.1 to 10.2.0.4 Goal  - Ref Metalink ID - 789370.1 The following note describes step-by-step procedure to create physical standby by using RMAN duplicate without shutting down the primary (Production) database. Database Name :- prim Primary db_unique_name :- prim standby db_unique_name :- stdby Primary Hostname :- raca.idc.oracle.com standby Hostname :- core1.idc.oracle.com Solution 1.Enable force logging. 2.Create SRL(standby redo logs). 3.Make proper changes in the parameter file of primary. 4.Backup the database that includes backup of datafiles, archivelogs and controlfile for standby and copy the backups to standby server. 5.Create the parameter file for standby, 6.Establish the connectivity from primary to standby. 7. Move backup to standby. 8 and 9. Start the standby instance. 10.U
Read more

How to Configure Logging for EM 12c Management Agent

The goal of this article is to provide instruction on how to enable logging for the Enterprise Manager 12c Management Agent.. ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- The logging properties for the agent are stored in $EMSTATE/sysman/config/emd.properties file, same as in 11.1. But the properties that control logging follow the log4j configuration syntax instead of the syntax supported by the 11.1 agent. To active changes to the logging parameters, you can use either of the emctl commands: emctl reload agent emctl setproperty agent Overview Agent logging entries look similar to the standard log4j logging, with the only significant difference being the prefix 'Logger.' that you will see on each line. For example: # logging properties Logger.log4j.appender.Rolling=org.apache.log4j.RollingFileAppender Logger.lo
Read more

index rebuild candidates oracle

Steps... CREATE TABLE index_log (  owner          VARCHAR2(30),  index_name     VARCHAR2(30),  last_inspected DATE,  leaf_blocks    NUMBER,     target_size    NUMBER,  idx_layout     CLOB); ALTER TABLE index_log ADD CONSTRAINT pk_index_log PRIMARY KEY (owner,index_name); CREATE TABLE index_hist (  owner          VARCHAR2(30),  index_name     VARCHAR2(30),  inspected_date DATE,  leaf_blocks    NUMBER,     target_size    NUMBER,  idx_layout     VARCHAR2(4000)); ALTER TABLE index_hist ADD CONSTRAINT pk_index_hist PRIMARY KEY  (owner,index_name,inspected_date); CREATE OR REPLACE PACKAGE index_util AUTHID CURRENT_USER IS vMinBlks     CONSTANT POSITIVE := 1000; vScaleFactor CONSTANT NUMBER := 0.6; vTargetUse   CONSTANT POSITIVE := 90;  -- equates to pctfree 10  vHistRet     CONSTANT POSITIVE := 10;  -- (#) records to keep in index_hist  procedure inspect_schema (aSchemaName IN VARCHAR2);  procedure inspect_index (aIndexOwner IN VARCHAR2, aIndexName IN VARCHAR2, a
Read more