New Features for 11g Release 2

• Oracle Secure Backup (OSB) Cloud Module

  Users can take advantage of the internet based data storage services offered by Amazon Simple Storage Service (S3) for their RMAN backup and recovery tasks. The OSB Cloud Module interface extends the Amazon S3 functionality and provides an easy-to-manage, cost efficient and scalable alternative to maintaining in-house data storage and a fully configured backup infrastructure.

  See Also:

  Appendix C in Oracle Database Backup and Recovery Reference

• DUPLICATE Database Command Enhancements

  Users can DUPLICATE a database without connecting to a target database. The only requirements to this operation are a connection to a catalog and an auxiliary database. This new functionality is useful when the target database is not always available.

  Users can also DUPLICATE a database without connecting to a target database and a recovery catalog. In this particular scenario, the only requirement is that you must provide a disk backup location where RMAN can find all the backups, datafile copies, archived logs, and control file copies for database duplication. This database duplication enhancement is helpful when it is not possible to connect to the target database and the recovery catalog.

  When duplicating from a target database, checks are in place to see if any excluded tablespaces contain SYS-owned objects, materialized views, and identifies tablespaces that are not self-contained before starting any duplication operations.

  See Also:

  Chapter 23, "Duplicating a Database", and Oracle Database Backup and Recovery Reference to learn about the associated DUPLICATE command options NOREDO and UNDO TABLESPACE.

• RMAN Tablespace Point-in-Time Recovery (TSPITR) Enhancements

  TSPITR can be used to recover a dropped tablespace and to recover to a point-in-time before the tablespace is brought online. The latter TSPITR operation can be repeated as many times as necessary.

  Note:

  Prior to this release, TSPITR did not operate on dropped tablespaces.

• Automatic Block Repair

  The enhancements to corrupt block detection make block repair more efficient and increases availability. This is an enhancement to the repair process and complements the 11g Release 1 automatic block corruption detection.

  A detected corrupt block (e.g. via user's SQL query) is now automatically repaired by using a good block from a physical standby database. With automatic block repair, a user querying data in the corrupt block no longer sees the corrupt block error message displayed (ORA-01578). Instead of the corrupt block error message, there is a pause while the corrupt block is repaired, then the results of the SQL query are returned. The automatic block repair is transparent to the user unless the repair fails. This enhancement allows blocks to be recovered faster because no redo needs to be applied to the block that is taken from the physical standby database.

  The enhancement requires an Active Data Guard license since real-time query mode must be enabled on the physical standby database.

  The operation occurs automatically but can also be explicitly invoked with the RMAN RECOVER BLOCK command.

  See Also:

  Chapter 18, "Performing Block Media Recovery" and the Oracle Database Backup and Recovery Reference RECOVER command.

• SET NEWNAME options

  SET NEWNAME is more powerful and easier to use. You can use this command on a specific tablespace or on all datafiles and tempfiles. You can also change the names for multiple files in the database.

  A new string format identifier "%b" makes it easier to move files around. Using SET NEWNAME with the format identifier "%b", enables you to designate a filename without its directory path. This option is particular useful when you want to keep the names of your datafiles the same but move them to a different directory location.

• CONVERT DATABASE option

  A new option, SKIP UNNECESSARY DATAFILES, is now supported for the CONVERT DATABASE command. When invoked, the only datafiles that are converted are those requiring RMAN processing during transfer between the specified platforms. The rest of the datafiles can be used by the destination database via shared storage or pathname. Overall database transport time can be reduced when skipping the conversion of datafiles that do not contain undo segments. This option can be used when converting at the source or converting ON DESTINATION PLATFORM.

• Expanded Backup Compression Levels

  RMAN now offers a wider range of compression levels with the Advanced Compression Option (ACO). While the existing BASIC compression option may be suitable for most environments, you may want to explore the ACO backup compression levels (LOW, MEDIUM, and HIGH) to achieve better performance or higher compression ratios.

• INCARNATION Specifier Enhancement

Incarnations may now be used to further qualify archived redo log ranges for the BACKUP, RESTORE and LIST commands. You can now specify ALL, CURRENT or designate a particular incarnation number when listing ranges of archived logs.

• TO DESTINATION syntax has been added to the BACKUP command. This addition allows you to designate a specific directory location for backups to disk and is primarily for use with BACKUP RECOVERY AREA. If backup optimization is enabled, then RMAN only skips backups of identical files that reside in the directory location specified by the TO DESTINATION option.

Changes in RMAN Functionality or Prerequisites

• Block Change Tracking can be used at a physical standby database only if the Oracle Active Data Guard option is licensed.