Database Reference
In-Depth Information
Run the following SQL statements on the standby instance:
SQL> ALTER DATABASE ADD STANDBY LOGFILE THREAD 1
GROUP 11 SIZE 100M,
GROUP 12 SIZE 100M,
GROUP 13 SIZE 100M,
GROUP 14 SIZE 100M;
SQL> ALTER DATABASE ADD STANDBY LOGFILE THREAD 2
GROUP 15 SIZE 100M,
GROUP 16 SIZE 100M,
GROUP 17 SIZE 100M,
GROUP 18 SIZE 100M;
•
Now it is time to turn on auto-managed recovery and start applying logs in real time. Run the
following command on the standby instance:
SQL> alter database recover managed standby database using current logfile
disconnect from session;
•
Finally, add the second standby instance and configure standby database details in the OCR.
Run through the following set of statements from the command prompt:
# srvctl add database -d RONDBS -o /u00/app/oracle/product/12.1.0/db_1 -r PHYSICAL_STANDBY
# srvctl add instance -d RONDBS_1 -n rac1
# srvctl add instance -d RONDBS_2 -n rac2
•
Configure a TNS connection pointing to the first standby instance and then run through the
following steps on the primary database, from the first instance:
SQL> ALTER SYSTEM SET LOG_ARCHIVE_CONFIG='DG_CONFIG=(RONDB,RONDBS)' SCOPE=BOTH;
SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEST_1='LOCATION=<ARCHVIE_LOCATION>
VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=RONDB'
SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEST_2=SERVICE=<RONDBS_TNS>
VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=RONDBS'
Manage RMAN with OEM Cloud Control 12c
As mentioned earlier, RMAN can be managed and invoked through a command-line prompt interface or through an
OEM (also referred to as OEM Cloud Control 12c). We will run through some of the OEM screenshots here to manage
and schedule a database backup and recovery operation through OEM.
•
Log in to OEM Cloud Control 12c using the predefined login credentials (Figure
8-6
).
