How to enable flash back on RAC database.

Enabling Flashback /Archive Log mode on a Single Instance Database is quite straight forward. In case of RAC, you need to follow additional steps.

The requirements for enabling Flashback Database are:

• Your database must be running in ARCHIVELOG mode, because archived logs are used in the Flashback Database operation.
• You must have a flash recovery area enabled, because flashback logs can only be stored in the flash recovery area.
• For Real Application Clusters databases, the flash recovery area must be stored in a clustered file system or in ASM.

First of all configure flash recovery area by setting db_recovery_file_dest_size and db_recovery_file_dest

ALTER SYSTEM SET DB_RECOVERY_FILE_DEST_SIZE = 20G SCOPE=BOTH;

ALTER SYSTEM SET DB_RECOVERY_FILE_DEST = '+DG1' SCOPE=BOTH;

We are using ASM Diskgroup here which is sharable and available to both the nodes.Next step is to enable archivelog mode and then to turn on flashback. To perform this, database needs to be in mount mode.

We can use srvctl to disable any associated Database service and then stop the Database

[/home/oracle>srvctl stop service -d TESTDB

[/home/oracle>srvctl stop database -d TESTDB

Now set Cluster_database=false for enabling the Archivelog mode. This is a additional step which is required in RAC Database. For Single Instance, we do not require it.

/home/oracle>sqlplus "/ as sysdba"

Connected to an idle instance.

SQL> startup nomount

ORACLE instance started.

Total System Global Area 1073741824 bytes

Fixed Size 1271564 bytes

Variable Size 314575092 bytes

Database Buffers 750780416 bytes

Redo Buffers 7114752 bytes

SQL> alter system set cluster_database=false scope=spfile;

System altered.

SQL> shutdown immediate

ORA-01507: database not mounted

ORACLE instance shut down.

SQL> exit

SQL> startup mount

ORACLE instance started.

Total System Global Area 1073741824 bytes

Fixed Size 1271564 bytes

Variable Size 314575092 bytes

Database Buffers 750780416 bytes

Redo Buffers 7114752 bytes

Database mounted.

SQL>alter database archivelog;

SQL> alter database flashback on;

Database altered.

Set the Cluster_database parameter again to true.

SQL> alter system set cluster_database=true scope=spfile;

System altered.

SQL>shutdown immediate

We will again use srvctl to start the database and associated service

[/home/oracle>srvctl start database -d TESTDB

[/home/oracle>srvctl start service -d TESTDB

We can confirm whether Archivelog mode and Flashback is enabled by querying V$DATABASE

SQL> SELECT LOG_MODE,FLASHBACK_ON FROM V$DATABASE;

LOG_MODE FLASHBACK_ON

------------ ------------------

ARCHIVELOG YES

How to enable archive log in RAC?

How to enable archive log in RAC?

How to put the database in archive mode in rac?

SQL> select name from v$database;

NAME
---------
EBSTEST

SQL> alter system set cluster_database=False scope=spfile;

System altered.

SQL>

srvctl status database -d ebstest

srvctl stop database -d ebstest

sqlplus "/as sysdba"

SQL> startup mount
ORACLE instance started.

Total System Global Area 9556852736 bytes
Fixed Size 2166288 bytes
Variable Size 6375346672 bytes
Database Buffers 3154116608 bytes
Redo Buffers 25223168 bytes
Database mounted.
SQL> alter database archivelog;

Database altered.

SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination +ARCH
Oldest online log sequence 380
Next log sequence to archive 382
Current log sequence 382
SQL> alter system set cluster_database=true scope=spfile;

System altered.

SQL> shutdown immediate
ORA-01109: database not open


Database dismounted.
ORACLE instance shut down.
SQL>

How to Apply Critical Patch Update (CPU) on RAC

http://khalidali-oracledba.blogspot.com/2012/04/how-to-apply-critical-patch-update-cpu.html

How to Apply Critical Patch Update (CPU) on RAC

Applying CPU Patche "CPUJULY2011" for 10.2.0.4 Database on LINUX

Note: 

Before continue the following step please read the README file from the patch.

Critical patch update (CPU) patches are cumulative, which means fixes from previous Oracle security alerts and critical patch updates are included.

It is not required to have previous security patches applied before applying the CPUJul2011 patches. However, you must be on the stated patch set level for a given product home before applying the CPUJul2011 patches for that release.

The Critical Patch Update (CPU) patches are rolling up gradation,

Do one of the following, depending on whether this is a RAC environment:

If this is a RAC environment, choose one of the patch installation methods provided by OPatch (rolling, all node, or minimum downtime), and shutdown instances and listeners as appropriate for the installation method selected.

This CPU patch is rolling RAC installable, Please refer to My Oracle Support Note244241.1.

If this is not a RAC environment, shut down all instances and listeners associated with the Oracle home that you are updating.

Step by step CPU patches Applying:

If you are wish to applying rolling CPU patch on RAC, then the following steps must be following.

Rolling patch (no downtime)

-Shutdown the Oracle instance on node 1
-Apply the patch to the RAC home on node 1
-Start the Oracle instance on node 1
-Shutdown the Oracle instance on node 2
-Apply the patch to the RAC home on node 2
-Start the Oracle instance on node 2
-Shutdown the Oracle instance on node 3
-Apply the patch to the RAC home on node 3
-Start the Oracle instance on node 3

1.Download the CPU patch p12419249_10204_Linux-x86 from Metalink.

2.Change the owner of the patch file to oracle user.

# chown –R oracle: install p12419249_10204_Linux-x86.zip

3.Set the PATH variable to locate the opatch utility.

$ export PATH=$PATH: $ORACLE_HOME/OPatch

4.unzip the patch and go the unzipped directory

$unzip p12419249_10204_Linux-x86.zip

5.Fine the Opatch version

$ opatch version

Invoking OPatch 10.2.0.4.2

OPatch Version: 10.2.0.4.2

$ opatch lsinventory

Note: if you want check the CPU patch is whether rolling support or not, follow the steps.

-go to the patch directory

Cd /oracle/12419249

[oracle@rac1 12419249]$ opatch query -all

Invoking OPatch 10.2.0.4.2

Oracle Interim Patch Installer version 10.2.0.4.2

Copyright (c) 2007, Oracle Corporation.  All rights reserved.

Oracle Home                  : /oracle/product/10.2.0/rdbms

Central Inventory           : /oracle/product/10.2.0/oraInventory

from                             : /etc/oraInst.loc

OPatch version               : 10.2.0.4.2

OUI version                    : 10.2.0.4.0

OUI location                   : /oracle/product/10.2.0/rdbms/oui

Log file location              : /oracle/product/10.2.0/rdbms/cfgtoollogs/opatch/opatch2011-05-01_08-55-20AM.log

-------------------------------------------------------------------------------- 

Patch created on 20 May 2011, 03:02:21 hrs PST8PDT

Need to shutdown Oracle instances: false      (<--hear false mean we no need to down the database)

 Patch is roll-backable: true

 Patch is a rolling patch: true

 Patch has sql related actions: false

 Patch is an online patch: false

 Patch is a portal patch: false

 List of platforms supported:

 46: Linux Intel

 List of bugs to be fixed:

 8534387: CPUJUL2009 DATABASE 10.2.0.4

 8290506: CPUAPR2009 DATABASE 10.2.0.4

 7375644: MLR BUG FOR 10.2.0.4 FOR CPUOCT2008

 9352191: CPUAPR2010 DATABASE 10.2.0.4

 9655017: CPUJUL2010 DATABASE 10.2.0.4

 7150470: MLR BUG FOR 10.2.0.4 FOR CPUJUL2008

 7592346: CPUJAN2009 DATABASE 10.2.0.4

 9952272: CPUOCT2010 DATABASE 10.2.0.4

 9119226: CPUJAN2010 DATABASE 10.2.0.4

 11725015: CPUAPR2011 DATABASE 10.2.0.4

 12419249: CPUJUL2011 DATABASE 10.2.0.4

 8836308: CPUOCT2009 DATABASE 10.2.0.4

 10249540: CPUJAN2011 DATABASE 10.2.0.4

 List of optional components:

 oracle.rdbms.rsf  :  10.2.0.4.0

 oracle.rdbms       :  10.2.0.4.0

6.Backup the oraInventory  and Opatch directory

$cp -R oraInventory old_oraInventory

$cp -R opatch old_opatch

7.If you are Applying on RAC, follow the below steps:

Shut down the instance one of node

$ srvctl stop instance -d racdb –i racdb1

Shut down the ASM instanc respected node

$ srvctl stop asm -n rac1

Shut down all Nodeapps services of the node

$ srvctl stop ndoeapps -n rac1

8.Go to the Patch Directory and invoke opatch apply.

$ cd 12419249

$opatch apply or $opatch napply -skip_subset -skip_duplicate

9.Verify Patches are applied

$opatch lsinventory -detail -oh $ORACLE_HOME

10.Now start the Node1 and repeat the same 1 to 10 steps on Node2

$ srvctl start nodeapps –n rac1

$srvctl start asm –n rac1

$srvctl start instance –d racdb –i racdb1

Note: if the database on rac1 located, now relocate to node2

$ crs_relocate ora.racdb.db

11.Now stop Instance,asm and nodeapps on node2

$ srvctl stop instance –d racdb –i racdb2

$ srvctl stop asm –n rac2

$ srvctl stop nodeapps –n rac2

12.Go to the Patch Direcotry and invoke the opatch apply on node2

$ cd 12419249

$ opatch apply or opatch napply -skip_subset -skip_duplicate 

     13.Verify Patches are applied 

          $opatch lsinventory -detail -oh $ORACLE_HOME

     14.Start  the Instance,Asm and Nodeapps on node2

$srvctl start instance –d racdb –i racdb2

$srvctl start asm –n rac2

$srvctl start nodeapps –n rac2

$crs_stat –t 

Post CPU installation Steps:

For each database instance running on the Oracle home being patched, connect to the database using SQL*Plus on each node.

Connect as SYSDBA and run the catbundle.sql script as follows:

On node1 and node2:

cd $ORACLE_HOME/rdbms/admin

sqlplus /nolog

SQL> CONNECT / AS SYSDBA

SQL> STARTUP

SQL> @catbundle.sql cpu apply

SQL> @utlrp.sql

SQL> QUIT

The catbundle.sql execution is reflected in the dba_registry_history view by a row associated with bundle series CPU.

For information about the catbundle.sql script, see My Oracle Support Note 605795.1Introduction to Oracle Database catbundle.sql.

Check the following log files in $ORACLE_HOME/cfgtoollogs/catbundle for any errors:

catbundle_CPU__APPLY_.log

catbundle_CPU__GENERATE_.log

Recompiling Views in the Database

You may skip this section if you have recompiled views for this database during the installation of a previous CPU.

The time required to recompile the views and related objects depends on the total number of objects and on your system configuration. 

In one internal Oracle test with approximately 2000 views and 4000 objects, the total execution time for view_recompile_jan2008cpu.sql and utlrp.sql was about 30 minutes.

If you want to check whether view recompilation has already been performed for the database, execute the following statement.

SELECT * FROM registry$history where ID = '6452863';

If the view recompilation has been performed, this statement returns one or more rows. If the view recompilation has not been performed, this statement returns no rows. If no rows returns then go the following steps.

The following steps recompile the views in the database. For a RAC environment, perform these steps on only one node.

1. Run the pre-check script (so named because it was initially released in CPUJan2008), which reports the maximum number of views and objects that may be recompiled:

cd $ORACLE_HOME/cpu/view_recompile

sqlplus /nolog

SQL> CONNECT / AS SYSDBA

SQL> @recompile_precheck_jan2008cpu.sql

SQL> QUIT

The purpose of this step is to help you determine whether view recompilation should be done at the same time as the CPU install, or scheduled later.

Note:

If the database is not in a RAC environment(if Single Instance), perform this step and skip the next step 2. (If the database is in a RAC environment, go to the next step2.)

Run the view recompilation script, note that this script is run with the database in upgrade mode, which restricts connections as SYSDBA.

cd $ORACLE_HOME/cpu/view_recompile

sqlplus /nolog

SQL> CONNECT / AS SYSDBA

SQL> SHUTDOWN IMMEDIATE

SQL> STARTUP UPGRADE

SQL> @view_recompile_jan2008cpu.sql

SQL> SHUTDOWN;

SQL> STARTUP;

SQL> QUIT

2.If the database is in a RAC environment, run the view recompilation script as follows, note that this script is run with the database in upgrade mode, which restricts connections as SYSDBA. Stop all instances except the one where the view recompilation is being executed.

cd $ORACLE_HOME/cpu/view_recompile

sqlplus /nolog

SQL> CONNECT / AS SYSDBA

SQL> STARTUP NOMOUNT

SQL> ALTER SYSTEM SET CLUSTER_DATABASE=FALSE SCOPE=spfile;

SQL> SHUTDOWN

SQL> STARTUP UPGRADE

SQL> @?/ cpu/view_recompile /view_recompile_jan2008cpu.sql

SQL> SHUTDOWN;

SQL> STARTUP NOMOUNT;

Set the CLUSTER_DATABASE initialization parameter to TRUE:

SQL> ALTER SYSTEM SET CLUSTER_DATABASE=TRUE SCOPE=spfile;

Restart the database:

SQL> QUIT

cd $CRS_HOME/bin

srvctl start database -d racdb

If any invalid objects were reported, run the utlrp.sql script as follows:

cd $ORACLE_HOME/rdbms/admin

sqlplus /nolog

SQL> CONNECT / AS SYSDBA

SQL> @utlrp.sql

Then, manually recompile any invalid objects. For example:

SQL> alter package schemaname.packagename compile;

4. Verify Patches are applied.

$opatch lsinventory -detail -oh $CRS_HOME #if you have CRS_HOME

$opatch lsinventory -detail -oh $ORACLE_HOME #if you have both ORACLE_HOME

  The CPU patch was successfully applied.

Query to verify Number of connections connection to each node by service

Here is the query to check # of connections on each node by the service_name.

col service_name format a25

select 

inst_id,

count(*) as connections,

service_name

from 

gv$session

group by

inst_id, service_name;

RAC SERVICE EXAMPLE

My notes on Oracle RAC Services --Moid

1. To check the status of all services in a RAC Database
10g
srvctl config service -d racdb
11g
srvctl config service -d racdb | grep -IE "Service name|Preferred instances"


2. To check the status of the service called crm
10g
srvctl status service -d racdb -s crm
11g



3a. To add a service
srvctl add service -d racdb -s CLROCM_DataRead_P -r racdb1,racdb2


 srvctl add service -d racdb-s oocert_n1pn2p -r ,oocert2 -P BASIC -e SELECT

x39 =
  (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = x39-3001.xyz.com)(PORT = 1521))
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = x39_n1pn2p)
    )
  )

set linesize 200
set pagesize 200
col username format a12
col machine format a20
Select
inst_id,
username,
machine,
failover_type,
failover_method,
failed_over
from
gv$session
where
username='AFSHAN'
order by 1,machine;



3b) Verify service is created.
srvctl status service -d racdb -s CLROCM_DataRead_P


3c) Enable the service
srvctl enable service -d racdb -s CLROCM_DataRead_P


3d) If service is already enabled, then start the service.
10g
srvctl start service -d racdb -s CLROCM_DataRead_P

11g



3e) Verify service is created, enabled and started.
10g
srvctl status service -d racdb -s CLROCM_DataRead_P


11g




4) How to relocated the service?
srvctl relocate service -d AQCLP -s AQSVC3P -i AQCLP1  -t AQCLP2 -f

srvctl relocate service -d AQCLP -s AQSVC6P -i AQCLP1 -t AQCLP2 -f
Note: Contributed by Ahmad Bhutta

RAC : SERVICES

In this post, I will explain the concept of services and their benefits in 11g R2 RAC.

What is a service?

A service is a logical grouping of sessions performing similar kind of work. They  enable you to group database workloads and route work to the optimal instances that are assigned to offer the service.It is recommended that all the users who connect using a service have the same service-level requirements. We can use services to manage workloads or a group of applications. For example , all on-line users can use one service whereas batch users can use another service and reporting can use yet another service.

Benefits of services:

– Services make the work more manageable, measurable, tunable and recoverable.

– Services provide an abstraction layer and permit clients and middle tiers to access required data from the database independent of where the instances reside.

– Dynamic: As the load increases/reduces, the number of instances supporting a service can be increased/decreased accordingly.

- High availability : In case an instance crashes, the services supported by it failover to another surviving instance.

- Tuning and Monitoring Aid

. Tracing can be enabled for all the sessions who connect using a service: This can be used to identify the culprit SQL statements issued by the users connected via a service.  . Performance statistics are collected and aggregated by service: This can be used to find out the performance of all the sessions belonging to a service.

. Two Performance thresholds can be specified for a service: SERVICE_ELAPSED_TIME and SERVICE_CPU_TIME: The AWR monitors the service time and CPU time and publishes alerts when the performance esceeds the thresholds. In response to these alerts, you can change the priority of a job, stop overloaded process , or relocate, expand, shrink , start or stop a service.

- Resource Management Aid : We can bind resource consumer groups to services. The users who connect using a service will  get the resources as per the allocation specified for the respective consumer group in the active resource plan. For example, if OLTP and BATCH services are defined to run on the same instance and our requirement is as follows:

. During day time OLTP users should get more resources whereas BATCH users should get less resources

  . During night, BATCH users should get more resources whereas OLTP users should get less resources

We can have two consumer groups : OLTP_GRP mapped to OLTP service and

                                                                          BATCH_GRP mapped to BATCH service

so that all users who connect using OLTP service are assigned OLTP_GRP and all users who connect using BATCH service are assigned BATCH_GRP .

We can have two resource plans :

  . DAY_PLAN in which OLTP_GRP is given more resources and BATCH_GRP is given less resources.

  . NIGHT_PLAN in which BATCH_GRP is given more resources and OLTP_GRP is given less resources.

- Job Control Aid : We can associate jobs with a job class and job class can be mapped to service.

– If service is mapped to a consumer group, the jobs will get the resources as per the allocation specified for the respective consumer group in the active resource plan. If  jobs of a job class are taking more time than desired, we can change the consumer group mapping of the respective service to one with more resources.

– If the instance running the jobs of a job class crashes, the services on the crashed instance fail over to another instance and all the jobs of the job class mapped to thst service also failover along with it.

i.e.

       Job1  —–+

       Job2  ——|——– Jobclass1 —— Service1

       Job3  ——+                                  |

                                                  Consumer group

                                                          |

                                                 Resource Plan

– Using Transparent Application Failover:  When a node crashes, all the services running on the instance hosted by that node fail over to another instance. From now onwards, the users who try to connect using failed over services will connect to the instances supporting that service. But what happens to the sessions who were already connected using that service at the time of crash? That is decided by the TAF (Transparent application Failover) policy which can be defined for the service. We can have 3 types of TAF policies : Basic, Preconnect and None.

BASIC failover. In this approach, the application connects to a backup node only after the primary connection fails. This approach has low overhead, but the end user experiences a delay while the new connection is created.

PRECONNECT failover. In this approach, the application simultaneously connects to both a primary and a backup node. This offers faster failover, because a pre-spawned connection is ready to use. But the extra connection adds everyday overhead by duplicating connections.

  We can also specify FAILOVER_TYPE for a service i.e. what kind of activity going on in the connected sessions will be resumed after the failover .  It can be Select or Session.

SELECT failover. With SELECT failover, Oracle Net keeps track of all SELECT statements issued during the transaction, tracking how many rows have been fetched back to the client for each cursor associated with a SELECT statement. If the connection to the instance is lost, Oracle Net establishes a connection to another Oracle RAC node and re-executes the SELECT statements, repositioning the cursors so the client can continue fetching rows as if nothing has happened. The SELECT failover approach is best for data warehouse systems that perform complex and time-consuming transactions.

 SESSION failover. When the connection to an instance is lost, SESSION failover results only in the establishment of a new connection to another Oracle RAC node; any work in progress is lost. SESSION failover is ideal for online transaction processing (OLTP) systems, where transactions are small.

The following types of transactions do not automatically fail over and must be restarted by TAF:

• Transactional statements. Transactions involving INSERT, UPDATE, or DELETE statements are not supported by TAF.
•  ALTER SESSION statements. ALTER SESSION and SQL*Plus SET statements do not fail over.
• Transactions using temporary segments in the TEMP tablespace and global temporary tables do not fail over.
• PL/SQL package states. PL/SQL package states are lost during failover.

– Connection Load balancing : If we have multiple instances supporting a service, We can spread user connections across all those instances. For each service, you can define the method that you want the listener to use for load balancing by setting the connection load balancing goal, CLB_GOAL. It can have two values : CLB_GOAL_LONG(default) and CLB_GOAL_SHORT.

Where’s the configuration of services stored?

Data Dictionary (Bulk of service configuration)

DBA_SERVICES

DBA_RSRC_GROUP_MAPPINGS

DBA_THRESHOLDS

DBA_SCHEDULER_JOB_CLASSES

TNSNAMES.ORA

Server-side

Entries for LOCAL_LISTENER and REMOTE_LISTENER

Client-side (in tnsnames.ora)

CONNECT_DATA

Special entries for PRECONNECT services

Resource profile in Cluster Registry (OCR)

Resource

Start/stop script

Dependencies

Restart policy

Stringpairs

Instance list

Preferred/available instances

Enabled/disabled

TAF policy

Initialization Parameters

LOCAL_LISTENER

REMOTE_LISTENERS

DB_DOMAIN

DISPATCHERS

STATISTICS_LEVEL

References:

DATAGUARD BROKER COMMAND

dgmgrl utility
dgmgrl - Data Guard Manager (Observer) Utility, in Oracle

$dgmgrl [-silent | -echo] [username/password[@connect_identifier] [dgmgrl_command]]
$dgmgrl  /
$dgmgrl sys/india123
$dgmgrl sys/pwd@oltp
$dgmgrl sys/test@dgprimary "show database 'prod'"
$dgmgrl -logfile observer.log / "stop observer"
$dgmgrl -silent sys/test@dgprimary "show configuration verbose"
$dgmgrl  / "show configuration verbose"

ADD - Adds a standby database to the broker configuration.
DGMGRL> ADD DATABASE db_name [AS CONNECT IDENTIFIER IS conn_identifier] [MAINTAINED AS {PHYSICAL|LOGICAL}];
DGMGRL> ADD DATABASE 'primary' AS CONNECT IDENTIFIER IS primary MAINTAINED AS PHYSICAL;
DGMGRL> ADD DATABASE 'standby' AS CONNECT IDENTIFIER IS standby MAINTAINED AS LOGICAL;
DGMGRL> ADD DATABASE 'standby' AS CONNECT IDENTIFIER IS standby.foo.com;

CONNECT - Connects to an Oracle database instance.
DGMGRL> CONNECT username/password[@connect_identifier]
DGMGRL> CONNECT /
DGMGRL> CONNECT sys;
DGMGRL> CONNECT sys@test;
DGMGRL> CONNECT sys/pwd;
DGMGRL> CONNECT sys/pwd@dwh;
DGMGRL> CONNECT /@dwh;
$dgmgrl connect sys

CONVERT - Converts a database from one type to another (from Oracle 11g).
DGMGRL> CONVERT DATABASE database_name TO {SNAPSHOT STANDBY|PHYSICAL STANDBY};
DGMGRL> CONVERT DATABASE 'standby' to SNAPSHOT STANDBY;

DGMGRL> CONVERT DATABASE 'standby' to PHYSICAL STANDBY;

Prints Popular Posts Dictionary English dictionary online Archiver Automatic storage management

CREATE - Creates a broker configuration. 

DGMGRL> CREATE CONFIGURATION config_name AS PRIMARY DATABASE IS db_name CONNECT IDENTIFIER IS conn_ident;

DGMGRL> CREATE CONFIGURATION 'dg' AS PRIMARY DATABASE IS 'primary' CONNECT IDENTIFIER IS primary;

DGMGRL> CREATE CONFIGURATION 'dg_test' AS PRIMARY DATABASE IS 'test' CONNECT IDENTIFIER IS test;

DISABLE - Disables a configuration, a database, or fast-start failover (FSFO).

DGMGRL> DISABLE CONFIGURATION;
DGMGRL> DISABLE CONFIGURATION;

DGMGRL> DISABLE DATABASE database_name;
DGMGRL> DISABLE DATABASE 'standby';

DGMGRL> DISABLE FAST_START FAILOVER [FORCE | CONDITION condition];
DGMGRL> DISABLE FAST_START FAILOVER;
DGMGRL> DISABLE FAST_START FAILOVER FORCE;
DGMGRL> DISABLE FAST_START FAILOVER CONDITION '1578';

EDIT - Edits a configuration, database, or instance.
DGMGRL> EDIT CONFIGURATION SET PROTECTION MODE AS {MaxProtection|MaxAvailability|MaxPerformance};
DGMGRL> EDIT CONFIGURATION SET PROTECTION MODE AS MAXPROTECTION;
DGMGRL> EDIT CONFIGURATION SET PROTECTION MODE AS MAXAVAILABILITY;
DGMGRL> EDIT CONFIGURATION SET PROTECTION MODE AS MAXPERFORMANCE;


DGMGRL> EDIT CONFIGURATION SET PROPERTY property_name = value;
DGMGRL> EDIT CONFIGURATION SET PROPERTY FastStartFailoverThreshold = 45;
DGMGRL> EDIT CONFIGURATION SET PROPERTY FastStartFailoverAutoReinstate = FALSE;
DGMGRL> EDIT CONFIGURATION SET PROPERTY FastStartFailoverAutoReinstate = TRUE;
DGMGRL> EDIT CONFIGURATION SET PROPERTY BYSTANDERSFOLLOWROLECHANGE= 'NONE';


DGMGRL> EDIT DATABASE database_name SET PROPERTY property_name = value;
DGMGRL> EDIT DATABASE standby SET PROPERTY 'LogArchiveFormat'='log_%t_%s_%r_%d.arc';

DGMGRL> EDIT DATABASE prodb SET PROPERTY LogXptMode=SYNC;
DGMGRL> EDIT DATABASE prodb SET PROPERTY LogXptMode=ASYNC;
DGMGRL> EDIT DATABASE prodb SET PROPERTY LogXptMode=ARCH;
DGMGRL> EDIT DATABASE standby SET PROPERTY LogShipping=OFF;
DGMGRL> EDIT DATABASE standby SET PROPERTY LogShipping=ON;
DGMGRL> EDIT DATABASE prodb SET PROPERTY LogArchiveTrace=8;
DGMGRL> EDIT DATABASE prodb SET PROPERTY NetTimeout=60;
DGMGRL> EDIT DATABASE standby SET PROPERTY 'ReopenSecs'=300;
DGMGRL> EDIT DATABASE prodb SET PROPERTY ArchiveLagTarget=1200;
DGMGRL> EDIT DATABASE prodb SET PROPERTY FastStartFailoverTarget='standby_name';
DGMGRL> EDIT DATABASE standby SET PROPERTY 

'StandbyArchiveLocation'='/oradata/archive/';
DGMGRL> EDIT DATABASE standby SET PROPERTY 'DbFileNameConvert' = '/u01/od01/datafile/, /oradisk/od01/datafile/';
DGMGRL> EDIT DATABASE primary SET PROPERTY DelayMins='720';
DGMGRL> EDIT DATABASE prodb SET PROPERTY RedoCompression ='ENABLE'
DGMGRL> EDIT DATABASE prodb SET PROPERTY RedoCompression ='DISABLE'
DGMGRL> EDIT DATABASE primary SET PROPERTY LogArchiveMinSucceedDest =1

DGMGRL> EDIT DATABASE database_name RENAME TO new database_name;
DGMGRL> EDIT DATABASE 'standbyb' RENAME TO 'standby'; 

DGMGRL> EDIT DATABASE database_name SET STATE = state [WITH APPLY INSTANCE = instance_name];
DGMGRL> EDIT DATABASE standby SET STATE='READ-ONLY';
DGMGRL> EDIT DATABASE standby SET STATE='OFFLINE';

DGMGRL> EDIT DATABASE standby SET STATE='APPLY-OFF';
DGMGRL> EDIT DATABASE standby SET STATE='APPLY-ON';

DGMGRL> EDIT DATABASE standby SET STATE='TRANSPORT-OFF';
DGMGRL> EDIT DATABASE standby SET STATE='TRANSPORT-ON';

DGMGRL> EDIT DATABASE prodb SET STATE='LOG-TRANSPORT-OFF';
DGMGRL> EDIT DATABASE standby SET STATE='ONLINE' WITH APPLY INSTANCE=standby2;

DGMGRL> EDIT INSTANCE instance_name [ON DATABASE database_name] SET AUTO PFILE [={init_file_path|OFF}];
DGMGRL> EDIT INSTANCE 'standby1' ON DATABASE 'standby' SET AUTO PFILE='initstandby1.ora';

DGMGRL> EDIT INSTANCE instance_name [ON DATABASE database_name] SET PROPERTY property_name = value;
DGMGRL> EDIT INSTANCE * ON DATABASE database_name SET PROPERTY property_name = value;
DGMGRL> EDIT INSTANCE 'proddb' ON DATABASE 'proddb' SET PROPERTY 'StandbyArchiveLocation'='/oradata/arch/';
Corrupted Data Guard Datafile Displays Information Prints Popular Posts Dictionary

ENABLE - Enables a configuration, a database, or fast-start failover (FSFO).
DGMGRL> ENABLE CONFIGURATION;
DGMGRL> ENABLE CONFIGURATION;

DGMGRL> ENABLE DATABASE database_name;
DGMGRL> ENABLE DATABASE 'standby';

DGMGRL> ENABLE FAST_START FAILOVER [CONDITION condition];
DGMGRL> ENABLE FAST_START FAILOVER;
DGMGRL> ENABLE FAST_START FAILOVER CONDITION '1578';
DGMGRL> ENABLE FAST_START FAILOVER CONDITION "Stuck Archiver";
DGMGRL> ENABLE FAST_START FAILOVER CONDITION 'Corrupted Controlfile';
DGMGRL> ENABLE FAST_START FAILOVER CONDITION 'Corrupted Dictionary';
DGMGRL> ENABLE FAST_START FAILOVER CONDITION 'Inaccessible Logfile';

EXIT - Exits the program.
DGMGRL> EXIT;

FAILOVER - Changes a standby database to be the primary database.
DGMGRL> FAILOVER TO standby_database_name [IMMEDIATE]
DGMGRL> FAILOVER TO "primary";
DGMGRL> FAILOVER TO "snapdb" IMMEDIATE;

HELP - Displays description and syntax for a command.
DGMGRL> HELP [command];
DGMGRL> HELP REINSTATE
DGMGRL> HELP EDIT

QUIT - Exits the program.
DGMGRL> QUIT;

REINSTATE - Changes a database marked for reinstatement into a viable standby.
DGMGRL> REINSTATE DATABASE database_name;
DGMGRL> REINSTATE DATABASE prim1;

REM - Comment to be ignored by DGMGRL.
DGMGRL> REM [comment];

REMOVE - Removes a configuration, Oracle database, or instance.
DGMGRL> REMOVE CONFIGURATION [PRESERVE DESTINATIONS];
DGMGRL> REMOVE CONFIGURATION;
DGMGRL> REMOVE CONFIGURATION PRESERVE DESTINATIONS;


DGMGRL> REMOVE DATABASE database_name [PRESERVE DESTINATIONS];
DGMGRL> REMOVE DATABASE standby;
DGMGRL> REMOVE DATABASE standby PRESERVE DESTINATIONS;

DGMGRL> REMOVE INSTANCE instance_name [ON DATABASE database_name];
DGMGRL> REMOVE INSTANCE inst1 ON DATABASE racdb;

SHOW - Displays information about a configuration, database, instance or FSFO.
DGMGRL> SHOW CONFIGURATION [VERBOSE];
DGMGRL> SHOW CONFIGURATION;
DGMGRL> SHOW CONFIGURATION VERBOSE;
English dictionary online Archiver Automatic storage management Corrupted Data Guard Datafile


DGMGRL> SHOW DATABASE [VERBOSE] db_name [property_name];
DGMGRL> SHOW DATABASE 'standby';
DGMGRL> SHOW DATABASE VERBOSE 'test';
DGMGRL> SHOW DATABASE 'dwhdb' 'StatusReport';
DGMGRL> SHOW DATABASE 'proddb' 'LogXptStatus';
DGMGRL> SHOW DATABASE 'proddb' 'InconsistentProperties';
DGMGRL> SHOW DATABASE 'proddb' 'InconsistentLogXptProps';
DGMGRL> SHOW DATABASE 'primary' 'ArchiveLagTarget';
DGMGRL> SHOW DATABASE 'primary' 'LogShipping';
DGMGRL> SHOW DATABASE 'primary' 'PreferredApplyInstance';
DGMGRL> SHOW DATABASE 'proddb' 'StatusReport';
DGMGRL> SHOW DATABASE 'primary' 'RecvQEntries';
DGMGRL> SHOW DATABASE 'proddb' 'SendQEntries';

DGMGRL> SHOW INSTANCE [VERBOSE] instance_name [property_name] [ON DATABASE db_name];
DGMGRL> SHOW INSTANCE inst1;
DGMGRL> SHOW INSTANCE VERBOSE inst3;
DGMGRL> SHOW INSTANCE primary 'TopWaitEvents';

DGMGRL> SHOW FAST_START FAILOVER;
DGMGRL> SHOW FAST_START FAILOVER;

SHUTDOWN - Shuts down a currently running Oracle instance.
DGMGRL> SHUTDOWN [NORMAL | IMMEDIATE | ABORT];
DGMGRL> SHUTDOWN;
DGMGRL> SHUTDOWN NORMAL;
DGMGRL> SHUT IMMEDIATE;
DGMGRL> SHUT ABORT;

SQL - Executes a SQL statement
DGMGRL> SQL "sql_statement";

START - Starts the fast-start failover(FSFO) observer.
DGMGRL> START OBSERVER [FILE=observer_configuration_file];
DGMGRL> START OBSERVER;

STARTUP - Starts an Oracle database instance.
DGMGRL> STARTUP [RESTRICT] [FORCE] [PFILE=filespec]
[NOMOUNT  |  MOUNT | OPEN [READ ONLY|READ WRITE]];
DGMGRL> STARTUP;
DGMGRL> STARTUP NOMOUNT;
DGMGRL> STARTUP MOUNT;
DGMGRL> STARTUP OPEN;
DGMGRL> STARTUP FORCE;
DGMGRL> STARTUP FORCE RESTRICT NOMOUNT;
DGMGRL> STARTUP PFILE=initdwh.ora NOMOUNT;

STOP - Stops the fast-start failover(FSFO) observer.
DGMGRL> STOP OBSERVER;

SWITCHOVER - Switches roles between a primary and standby database.
DGMGRL> SWITCHOVER TO standby_database_name;
DGMGRL> SWITCHOVER TO "standby";
Displays Information Prints Popular Posts Dictionary English dictionary online


VALIDATE - command to checks whether the database is ready for a role transition or not.

DGMGRL> VALIDATE DATABASE ...;    -- From Oracle Database 12c


$BDUMP/drc*.log
$ORACLE_HOME/rdbms/log/drc*.log

alter system set dg_broker_start=false;
alter system set dg_broker_start=false sid='*';
alter system set dg_broker_start=FALSE SCOPE=spfile SID='*';
alter system set dg_broker_start=true;
alter system set dg_broker_start=true sid='*';
alter system set dg_broker_start=TRUE SCOPE=spfile SID='*';

alter system set dg_broker_config_file1='/u01/dg_broker_config_files/dr1TESTP.dat' sid='*';
alter system set dg_broker_config_file2='/u01/dg_broker_config_files/dr2TESTP.dat' sid='*';