Data Guard 12.2 New Features Deep-Dive

By Charles Kim, Ace Director and President of Viscosity North America

January, 2017

Oracle Database 12c Release 2, packs a multitude of Data Guard 12.2 New Features with high availability, data protection, and disaster recovery. Through the new functionality shared in this paper, DBAs can provide better protection for mission critical production databases from human errors, data corruptions, failures, and disasters. With the new features in Oracle 12.2, DBAs can deliver a robust reporting environment while addressing corporate disaster recovery goals.

Create a Standby Database with DBCA

Starting with this release, we can leverage the Database Configuration Assistant (DBCA) command-line interface, to instantiate the Data Guard standby database from the primary database. Leveraging the DBCA command-line interface, will eliminate many of the manual steps needed to create a standby database. With the DBCA command-line interface, we can also embed post instantiation scripts to be executed with the –customScripts option, as a post standby database instantiation process. For multiple scripts, we can supply a list of script names followed by a comma. The scripts will be executed in the order of the supplied list.
As of this release, several restrictions apply. First, only non-multitenant, primary databases can be instantiated as standby databases. Also, RAC physical standby databases cannot be created. To convert the single instance database to RAC, DBAs can leverage OEM Cloud Control.
DBCA offers a new -createDuplicateDB parameter, to duplicate a database from the primary database. The –createAsStandby parameter, is available to duplicate a standby database from the primary database. Additional options for dbca with the – createDuplicateDB parameter are:

dbca -createDuplicateDB
-gdbName global_database_name
-primaryDBConnectionString easy_connect_string_to_primary -sid database_system_identifier
[-createAsStandby
[-dbUniqueName db_unique_name_for_standby]] [-customScripts scripts_list]
For the –primaryDBConnectionString, we can provide the easy connect string in the form of
'host[:port][/service_name][:server][/instance_name]'.
This eliminates the need to create a TNSNAMES.ORA entry.

To receive the full 9 page version of this document, please complete the download form provided.

SIGN UP TO DOWNLOAD

Full Name (required)

Your Email (required)

Company (required)

Phone number (required)

Job Title (required)