Posts

Showing posts from May, 2017

Perform the Switchover in our Test DB ENV

Perform the Switchover in our Test DB ENV Primary database - IP (10.0.0.1) ===================================== Before Switchover from primary to standby ===================================== SQL> select name,open_mode,database_role from v$database; NAME      OPEN_MODE            DATABASE_ROLE --------- -------------------- ---------------- PR        READ WRITE           PRIMARY SQL> select instance_name from v$instance; INSTANCE_NAME ---------------- pr SQL> select process from v$managed_standby; PROCESS --------- ARCH LNS [oracle@pr ~]$ dgmgrl DGMGRL for Linux: Version 11.2.0.4.0 - 64bit Production Copyright (c) 2000, 2009, Oracle. All rights reserved. Welcome to DGMGRL, type "help" for information. DGMGRL> connect sys/xxx Connected DGMGRL> show configuration Configuration - PRDG   Protection Mode: MaxPerformance   Databases:     pr  - Primary database     std - Physical standb

Data Guard Broker Configuration (DGMGRL Utility)

Data Guard Broker Configuration (DGMGRL Utility) Data Guard broker configuration using the command line dgmgrl interface,  Below are the step by step procedure tested & verified in our Test ENV Primary Database : PR Standby Database: STD Set the below parameter as on both Primary as well as Standby database start the Data Guard Broker process SQL> ALTER SYSTEM SET DG_BROKER_START=TRUE SCOPE=BOTH; System altered. Edit the listener.ora on both nodes to add a static entry for DGMGRL This is to prevent the ORA-12154 error which can be observed on startup of the standby database after performing a switchover. Ensure that the GLOBAL_DBNAME is set to db_unique_name_DGMGRL.db_domain $ cat $ORACLE_HOME/network/admin/listener.ora LISTENER =   (DESCRIPTION_LIST =     (DESCRIPTION =       (GLOBAL_DBNAME = pr_dgmgrl)       (ADDRESS = (PROTOCOL = TCP)(HOST = pr)(PORT = 1521))     )   ) ADR_BASE_LISTENER = /u01/app/oracle Create the co