Oracle 11g Backup Restore Enhancements

Oracle 11g has added a lot of functionality to backup and recovery, with varying degrees of performance, functionality, security, and operability.

This article describes the validation when Rman deletes an archive log.

In the previous version of 11g, Oracle's Rman was not tightly integrated with other log applications, so when Rman deletes the archive log, it does not determine if the log is still useful for other systems.

When Rman deletes the log, other systems, such as data GUARD, streams, and so on, may be found to be unable to function because the log was deleted.

Starting with the 11g, Rman will first determine whether the log is still required by other systems, and the Rman will report to the police and not delete the log when other needs still need it.

First look at the situation under 10g:

　　SQL> conn sys/test@testrac_standby as sysdba已连接。
　　SQL> select sequence# from v$managed_standby where status = 'WAIT_FOR_LOG'；
　　SEQUENCE#
　　----------
　　577
　　SQL> shutdown immediate

ORA-01109: Database not open

The database has been unloaded.

The ORACLE routine has been closed.

　　SQL> exit从 Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
　　With the Partitioning， OLAP and Data Mining options 断开
　　$ rman target /

Recovery manager: Release 10.2.0.3.0-production on Thursday September 13 04:14:09 2007

Copyright (c) 1982, +, Oracle. All rights reserved.

Connect to target database: Testrac (dbid=4291216984)

rman> Delete archivelog sequence 577;