Dataguard => 12cR2 New Feature "Multiple Instance Redo Apply"

Starting in Oracle 12.2, we can run Redo Apply all or on some standby instances.
With this concept of multiple instance redo apply (MIRA), Redo Apply performance can scale as wide as the target RAC configuration allows.

This feature is crucial for Exadata and RAC customers with demanding high workloads on the primary database. For Active Data Guard customers, they can have real-time access to the data being churned on the primary database.

The ALTER DATABASE RECOVER MANAGED STANDBY DATABASE command, now accepts new INSTANCES [ ALL | integer] clause to start Redo Apply on multiple instances. The ALL option, starts redo apply on all the RAC standby instances that are in open or mount mode. All the instances must be in the same mounted or open mode; one instance cannot be in open mode (Active Data Guard or read-only mode) while others are in mounted mode. The integer option, specifies the number of RAC standby instances that will perform redo apply. We cannot specify which RAC instance(s) will perform the redo apply.

Starting redo apply on multiple instances has the following restrictions:
• In-Memory column store is not supported.
• Block Change tracking (BCT) is not supported.

With multi-node MRP, redo apply performance is now directly correlated to network bandwidth and latency between the primary and standby database environments

RMAN Simulation For Tape

You can test RMAN tape utility without any media manager

CONFIGURE CHANNEL DEVICE TYPE sbt PARMS 'SBT_LIBRARY=oracle.disksbt, ENV=(BACKUP_DIR=/u01/app/oracle/backup/)' format '%U.bck';

CONFIGURE DEFAULT DEVICE TYPE TO 'sbt';

CONFIGURE DEVICE TYPE SBT_TAPE PARALLELISM 2 BACKUP TYPE TO BACKUPSET;

RMAN => 12cR2 New Feature "recover database until available redo"

After you restore your database, it is sometimes possible to lost your archivelogs to recover but even so you want to recover as far as possible and open your database with resetlogs.

Before 12cR2, if you face such a case like that, you need to switch SQL*Plus and run the below command:

recover database using backup controlfile until cancel;

Then, you should say “CANCEL” and open with resetlogs option.

or

you need to identifiy missing archivelog and give the "restore" command with until sequence/until time option.

After 12cR2, you dont need that extra step, you can directly say to oracle with RMAN to recover database  as far as possible and cancel it automatically.

The below screenshot is from classic output if I delete the sequence 5 manually.

And this is new behaviour with 12cR2, it could recover the database until sequence 5 without issue.

Installation

post for install

Dataguard

post for dataguard

PL/SQL

post for plsql

DB Admin

Exadata

post for exadata