This preface contains:
The following are changes in Backup and Recovery User's Guide for Oracle Database 12c Release 1 (18.104.22.168).
The following are the new features in this release:
Oracle Virtual Private Database (VPD) for RMAN virtual private catalog
The RMAN recovery catalog is created and managed using VPD. This provides better performance and scalability when a large number of virtual private catalogs are created.
The following are changes in Backup and Recovery User's Guide for Oracle Database 12c Release 1 (22.214.171.124).
The following are new features in this release:
Support for multitenant container databases and pluggable databases
RMAN provides backup and recovery of multitenant container databases (CDBs), which are introduced in Oracle Database 12c Release 1 (12.1). This support includes backup and point-in-time recovery of specified pluggable databases (PDBs).
SYSBACKUP administrative privilege encompasses the permissions required for backup and recovery, including the ability to connect to a closed database. System administrators can grant
SYSBACKUP instead of
SYSDBA to users who perform backup and recovery, thus reducing the proliferation of the
SYSDBA privilege. In contrast to
SYSBACKUP does not include data access privileges such as
SELECT ANY TABLE.
Storage Snapshot Optimization
Storage Snapshot Optimization enables you to use third-party technologies to take a storage snapshot of your database without putting the database in
BACKUP mode. You can then use the snapshot to recover all or part of the database.
SQL Interface Improvements
You can now issue most SQL commands in RMAN without preceding the command with the SQL keyword. For a few commands that exist in both RMAN and SQL and have very different uses, you can specify the
SQL keyword to eliminate ambiguity. You no longer need to enclose the SQL command in quotes, which greatly simplifies the syntax when the SQL command itself requires quotation marks. The SQL
ALTER command replaces the RMAN command.
The new RMAN
DESCRIBE command provides the functionality of the SQL*Plus
Multisection Backup Improvements
RMAN provides multisection backup support for incremental backups and image copies. Wherever possible, unused block compression and Block Change Tracking are used in conjunction with multisection incremental backups. This improves backup and restore performance.
Restoring and Recovering Files Over a Network
You can now restore or recover a database, data files, tablespaces, or control files by using backup sets from a physical standby database. RMAN transfers the backup sets, over the network, to the destination host. This is useful in a Data Guard environment when you want to synchronize the standby and primary databases.
Active Database Duplication Improvements
RMAN can now perform active database duplication using backup sets. When sufficient auxiliary channels are allocated, the auxiliary instance connects to the target instance and retrieves the backup sets over the network, thus reducing the processing load on the target instance. Unused block compression can be used during the duplication process, thus reducing the size of backups transported over the network. You can specify the binary compression level to be used. You can also encrypt backups and use multisection backups while performing active database duplication.
Cross-Platform Backup and Restore Improvements
You can transport data across platforms by using full and incremental backup sets. Incremental backups can reduce overall application downtime during cross-platform data migration.
Recovering Tables and Table Partitions from RMAN Backups
RMAN can recover tables and table partitions to a specified point in time from previously-created RMAN backups.
Unified auditing and RMAN
Unified auditing consolidates all the Oracle Database audit records into one single audit trail. To use unified auditing, you must first upgrade your database to Oracle Database 12c Release 1 (12.1) and then migrate your database to use unified auditing.
You can specify that the duplicate database must not be opened using
RESETLOGS after it is created. You may prefer not to open the duplicate database if you want to change the initialization parameters of the duplicate database or if opening the duplicate database may start services in the duplicate database that will conflict with the source database.
This section contains additional changes in this release.
The following chapter has been relocated:
Chapter "Performing ASM Data Migration": This information is now included in the Oracle Automatic Storage Management Administrator's Guide.