Changes in This Release for Backup and Recovery User's Guide

This preface contains:

• Changes in Oracle Database Release 19c

• Changes in Oracle Database Release 18c, Version 18.1

Changes in Oracle Database Release 19c

The following are changes in the Oracle Database Backup and Recovery User’s Guide for Oracle Database Release 19c.

• Recovery catalog support for PDBs

  You can connect to a recovery catalog when the target database is a pluggable database (PDB).

  See "Connecting as Target to a PDB".

• Automatic deletion of flashback logs

  Flashback logs that are beyond the retention period are automatically deleted. Automatically deleting flashback logs simplifies the management of the fast recovery area and improves the performance of flashback database.

  See "Managing Space for Flashback Logs in the Fast Recovery Area".

• Deprecated Features

  Starting in Oracle Database 19c, the Data Recovery Advisor (DRA) feature is deprecated.

  The deprecation of DRA includes deprecation of the following Oracle Recovery Manager (RMAN) commands: LIST FAILURE, ADVISE FAILURE, REPAIR FAILURE, and CHANGE FAILURE. Database administrators will no longer have access to these commands. There is no replacement feature for DRA.

Changes in Oracle Database Release 18c, Version 18.1

The following are changes in Oracle Database Backup and Recovery User’s Guide for Oracle Database release 18c, version 18.1.

New Features

• Duplicate PDBs into an existing CDB

  The DUPLICATE command can be used to duplicate a PDB to an existing CDB.

  See Also:

  • About Duplicating PDBs

  • Duplicating a PDB to an Existing CDB

• Duplicate databases to Oracle Cloud

  An on-premises Oracle database can be duplicated to Oracle Cloud Infrastructure Classic. Similarly, you can duplicate an Oracle database in Oracle Cloud Infrastructure Classic as an on-premises database.

  See Also:

  • Duplicating Databases to Oracle Cloud

  • Duplicating an Oracle Cloud Database as an On-premise Database

• Roll forward a physical standby

  Improvements to the functionality for rolling forward a standby database result in a simplified procedure for performing this task.

  See Also:

  Steps to Refresh a Physical Standby Database with Changes Made to the Primary Database

• RMAN backups usable after migration

  RMAN backups of a non-CDB or PDB that were created before the non-CDB or PDB was migrated and plugged in to a different CDB can be used for recovery operations in the new CDB.

  See Also:

  • Creating a Preplugin Backup of the Whole Database

  • Creating Preplugin Backups of PDBs Using RMAN

  • Performing Complete Recovery of PDBs Using Preplugin Backups

• Shadow lost write protection

  Data loss is minimized by fast detection and immediate response to data block lost rewrites.

  See Also:

  Enabling Shadow Lost Write Protection