Implementation notes. These are the steps to follow Enable forced logging. Create a password file. Configure a standby redo log. Enable archiving. Set up the primary database initialization parameters. Configure the listener and tnsnames to support the database on both nodes.The tests have been performed on Oracle Linux 5.5 with the Red Hat Kernel. You then begin by configuring the Data Guard broker, unless of course you know. I found note “11gR2 RAC DB switchover using DG broker ID.With Oracle Database 11g Release 2, Oracle ASM adds support for storing the Oracle Clusterware OCR and voting disk files. OCR and voting disk files are two component of Oracle clusterware. To install and configuration Oracle RAC there are several tools that RAC provides.Backup DB Broker Configuration Files. ++ Please disable the Data Guard Broker before you do patch or upgrade. Oracle Data Guard running on Oracle Database 10g or Oracle Database 11g. Oracle DBA RAC Expert by Rajasekhar. Forex trading industry. Connect to the DGMGRL from any of primary nodes and run the below statements to create and enable the DataGuard configuration. Verify that the DG Broker is configured correctly and it has all the databases and instances registered as expected.How to setup Active Dataguard and Dataguard Broker. -- 11.1 Create the Data Guard configuration using the Primary site. Oracle Data Guard Broker 11g Release 2.Create an Oracle Data Guard Broker configuration for the primary database. You use the dgmgrl command to create the Oracle Data Guard Broker configuration. You need to know the name of the Oracle Data Guard Broker configuration that you want to create, the name of the primary database, and the net service name through which to connect.
How to set up data guard broker for RAC Martins Blog.
This can be done by setting property Log Xpt Mode to SYNC. But we should do it for primary database at same time so that post switchover we have same mode.In earlier versions of Oracle, the Data Guard Broker has been regarded with suspicion.However, in Oracle 11g R2 the Data Guard Broker is much more stable and has become the preferred tool for managing Data Guard configurations. Borders world trade center. Before we start, first you should check my article Configuring Oracle Dataguard, for a single node primary database and single node standby database; because configuring Dataguard for RAC is not much different than setting up Dataguard for single node database. During this article, I would be referring to the aforementioned document rather thanThis step by step guide will take you through the steps to install and configure Oracle Grid Infrastructure 12c and Database 12c including RAC to RAC Data Guard and Data Broker configuration in a Primary and Physical Standby environment for high availability.The salesdr database is a physical copy of the sales database. Create an Oracle Data Guard Broker configuration for the primary database. You use the dgmgrl command to create the Oracle Data Guard Broker configuration. You need to know the name of the Oracle Data Guard Broker configuration that you want to create, the name of the primary database, and the net service name through which to connect.
It is possible to override the default service names, but in this case I chose the lazy option and stuck with the Oracle defaults.Note that in a RAC environment the SID_NAME will be different on each node, so don't copy the file between nodes.We also specified entries for both the primary and standby databases in $ORACLE_HOME/network/admin/ Commercial trade. For example: PROD = (DESCRIPTION = (ADDRESS = (PROTOCOL=TCP)(HOST=server14.juliandyke.com)(PORT=1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = PROD) ) ) STBY = (DESCRIPTION = (ADDRESS = (PROTOCOL=TCP)(HOST=server15.juliandyke.com)(PORT=1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = STBY) ) ) In this example, the PROD database will run on server14 and the STBY database will run on server15.Next enable the Data Guard Broker for each database (primary and standby) in the configuration by setting the DG_BROKER_START parameter to TRUE.The Data Guard Broker maintains two copies of its configurations.
Oracle in World Step by Step Oracle 11gR2 RAC Installation..
The locations of these files are specified by the DG_BROKER_CONFIG_FILE1 and DG_BROKER_CONFIG_FILE2 parameters.For a single instance database, the default values are: The default values are probably adequate for a single instance database; in a RAC environment the defaults should be modified to specify a location in a shared file system or ASM diskgroup(s).On any node in the configuration, start the Data Guard Broker command utility (DGMGRL) and connect as the SYS user. Swing trading wiki. SWITCHOVER TO 'STBY' Performing switchover NOW, please wait... Operation requires shutdown of instance "PROD" on database "PROD" Shutting down instance "PROD"... Switchover succeeded, new primary is "STBY" If the environment has been correctly configured then switchover generally works first time.ORACLE instance shut down.\n Operation requires startup of instance "PROD" on database "PROD" Starting instance "PROD"... However, it can take a few minutes to complete the switchover operation.If the operation does not complete immediately then don't panic. Switchover succeeded, new primary is "PROD" SHOW CONFIGURATION Configuration - DG1 Protection Mode: Max Availability Databases: PROD - Primary database STBY - Physical standby database Fast-Start Failover: DISABLED Configuration Status: SUCCESS SHOW CONFIGURATION VERBOSE Configuration - DG1 Protection Mode: Max Availability\n Databases: PROD - Primary database STBY - Physical standby database Properties: Fast Start Failover Threshold = '30' Operation Timeout = '30' Fast Start Failover Lag Limit = '30' Communication Timeout = '180' Fast Start Failover Auto Reinstate = 'TRUE' Fast Start Failover Pmy Shutdown = 'TRUE' Bystanders Follow Role Change = 'ALL' Fast-Start Failover: DISABLED Configuration Status: SUCCESS SHOW DATABASE VERBOSE 'PROD' Database - PROD Role: PRIMARY Intended State: TRANSPORT-ON Instance(s): PROD Properties: DGConnect Identifier = 'PROD' Observer Connect Identifier = '' Log Xpt Mode = 'SYNC' Delay Mins = '0' Binding = 'OPTIONAL' Max Failure = '0' Max Connections = '1' Reopen Secs = '300' Net Timeout = '30' Redo Compression = 'DISABLE' Log Shipping = 'ON' Preferred Apply Instance = '' Apply Instance Timeout = '0' Apply Parallel = 'AUTO' Standby File Management = 'AUTO' Archive Lag Target = '0' Log Archive Max Processes = '5' Log Archive Min Succeed Dest = '1' Db File Name Convert = ' DATA2, DATA1' Log File Name Convert = ' FRA2, FRA1' Fast Start Failover Target = '' Inconsistent Properties = '(monitor)' Inconsistent Log Xpt Props = '(monitor)' Send QEntries = '(monitor)' Recv QEntries = '(monitor)' Sid Name = 'PROD' Static Connect Identifier = '(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=10.227.27.1) (PORT=1521))(CONNECT_DATA=(SERVICE_NAME=PROD_DGMGRL) (INSTANCE_NAME=PROD)(SERVER=DEDICATED)))' Standby Archive Location = ' FRA1' Alternate Location = '' Log Archive Trace = '0' Log Archive Format = '%t_%s_%r.dbf' Top Wait Events = '(monitor)' Database Status: SUCCESS I can never remember the names of the Data Guard dynamic performance views so I really like the Transport Lag and Apply Lag fields in the above output.
Wait for a few minutes and then check the status again. SWITCHOVER TO 'PROD' Performing switchover NOW, please wait... Operation requires shutdown of instance "STBY" on database "STBY" Shutting down instance "STBY"... Operation requires startup of instance "STBY" on database "STBY" Starting instance "STBY"... Data Guard is the name for Oracle's standby database solution, used for disaster recovery and high availability.This article gives an example of the setup and administration of Data Guard using the Data Guard Broker. Create standby redo logs on the primary database (in case of switchovers).The standby redo logs should be at least as big as the largest online redo log and there should be one extra group per thread compared the online redo logs.In my case, the following standby redo logs must be created on both servers. ALTER DATABASE ADD STANDBY LOGFILE THREAD 1 GROUP 10 SIZE 50M; ALTER DATABASE ADD STANDBY LOGFILE THREAD 1 GROUP 11 SIZE 50M; ALTER DATABASE ADD STANDBY LOGFILE THREAD 1 GROUP 12 SIZE 50M; ALTER DATABASE ADD STANDBY LOGFILE THREAD 1 GROUP 13 SIZE 50M; -- If Oracle Managed Files (OMF) is not used.
Database Administration 11gR2 RAC-RAC Data Guard.
This Oracle Database 11g RAC Administration Release 2 training explores RAC database administration in the Oracle Grid Infrastructure environment. Expert instructors will help you develop the skills to administer cluster databases using Enterprise Manager and command-line utilities like SRVCTL, CRSCTL and SQL*Plus.ORACLE-BASE - Data Guard Physical Standby Setup Using the Data Guard Broker in Oracle Database 11g Release 2.Oracle 11gR2 GI and RDBMS installation or update. The Data Guard Broker configuration in RAC instances should be on shared storage. LISTENER = (DESCRIPTION_LIST = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = ol7-121-dg2)(PORT = 1521)) (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521)) ) ) SID_LIST_LISTENER = (SID_LIST = (SID_DESC = (GLOBAL_DBNAME = cdb1_stby_DGMGRL) (ORACLE_HOME = /u01/app/oracle/product/22.214.171.124/db_1) (SID_NAME = cdb1) ) ) ADR_BASE_LISTENER = /u01/app/oracle DUPLICATE TARGET DATABASE FOR STANDBY FROM ACTIVE DATABASE DORECOVER SPFILE SET db_unique_name='cdb1_stby' COMMENT 'Is standby' SET db_file_name_convert='/original/directory/path1/','/new/directory/path1/','/original/directory/path2/','/new/directory/path2/' SET log_file_name_convert='/original/directory/path1/','/new/directory/path1/','/original/directory/path2/','/new/directory/path2/' SET job_queue_processes='0' NOFILENAMECHECK; Once the command is complete, we can start using the broker. DGMGRL SWITCHOVER TO cdb1; Performing switchover NOW, please wait... Operation requires start up of instance "cdb1" on database "cdb1_stby" Starting instance "cdb1"... REINSTATE DATABASE cdb1; Reinstating database "cdb1", please wait... Although a switchover/switchback is safe for both the primary and standby database, a failover renders the original primary database useless for converting to a standby database.At this point we have a primary database and a standby database, so now we need to start using the Data Guard Broker to manage them. DGMGRL SHOW CONFIGURATION; Configuration - my_dg_config Protection Mode: Max Performance Members: cdb1 - Primary database cdb1_stby - Physical standby database Fast-Start Failover: DISABLED Configuration Status: SUCCESS (status updated 26 seconds ago) DGMGRL SHOW DATABASE cdb1_stby; Database - cdb1_stby Role: PHYSICAL STANDBY Intended State: APPLY-ON Transport Lag: 0 seconds (computed 1 second ago) Apply Lag: 0 seconds (computed 1 second ago) Average Apply Rate: 11.00 KByte/s Real Time Query: OFF Instance(s): cdb1 Database Status: SUCCESS DGMGRL A database can be in one of two mutually exclusive modes (primary or standby). Operation requires a connection to instance "cdb1" on database "cdb1" Connecting to instance "cdb1"... Operation requires shut down of instance "cdb1" on database "cdb1" Shutting down instance "cdb1"... Operation requires start up of instance "cdb1" on database "cdb1" Starting instance "cdb1"... If flashback database is not enabled, the original primary must be scrapped and recreated as a standby database.Connect to both databases (primary and standby) and issue the following command. These roles can be altered at runtime without loss of data or resetting of redo logs. Switchover succeeded, new primary is "cdb1_stby" DGMGRL $ dgmgrl sys/Password1@cdb1_stby DGMGRL for Linux: Version 126.96.36.199.0 - 64bit Production Copyright (c) 2000, 2013, Oracle. An alternative is to enable flashback database on the primary (and the standby if desired) so in the event of a failover, the primary can be flashed back to the time before the failover and quickly converted to a standby database, as shown above.