本帖最后由 lovehewenyu 于 2013-6-21 16:37 编辑
ARCHIVELOG DELETION POLICY
Determines when archived redo log files are eligible for deletion.
The archived log deletion policy applies to all log archiving destinations, including the fast recovery area. The policy does not apply to archived redo log files in backup sets.
Only archived redo log files in the fast recovery area are automatically deleted by the database. You can execute the BACKUP ... DELETE INPUT, DELETE ARCHIVELOG, or DELETE OBSOLETE commands to delete logs manually from log archiving destinations, including the recovery area. If FORCE is not specified on the deletion commands, then these deletion commands obey the archived log deletion policy. If FORCE is specified, then the deletion commands ignore the archived log deletion policy.
In the recovery area, the database retains logs eligible for deletion as long as possible. The database deletes the oldest logs first when disk space is required. When the recovery area is under disk pressure, the database may delete archived redo log files needed by Oracle Streams.
Note: The deletion policy does not apply to foreign archived redo log files, which are logs received by a logical standby database for a LogMiner session. These logs are transferred from a primary database, but unlike ordinary archived redo log files they have a different DBID. Foreign archived redo log files cannot be backed up or restored on a logical standby database.
TO APPLIED ON
[ALL] STANDBY
Specifies that archived redo log files are eligible for deletion if both of the following conditions are met:
The archived redo log files have been applied to the required standby databases.
The logs are not needed by the BACKED UP ... TIMES TO DEVICE TYPE deletion policy. If the BACKED UP policy is not set, then this condition is always met.
Which remote destinations are considered depends on the following criteria:
If you do not specify ALL, then archived redo log files are eligible for deletion after being applied to all mandatory remote destinations.
If you specify ALL, then archived redo log files are eligible after being applied or consumed on all remote destinations, whether mandatory or not.
For example, standby database sby1 may be the only remote destination receiving logs, but other remote destinations may apply logs by referring to the same location on sby1. With ALL, sby1 marks the log on the primary database as consumed as soon as it is not required at sby1, but does not permit deletion of this log until it is applied or consumed by all other dependent remote destinations referring to the same location.
Note: It is invalid to specify the TO APPLIED clause in combination with either NONE or the TO SHIPPED clause.
See Also: Oracle Data Guard Concepts and Administration for details
BACKED UP integer
TIMES TO DEVICE
TYPE deviceSpecifier Specifies that archived redo log files are eligible for deletion if both of the following conditions are met:
The specified number of archived log backups exist on the specified device type.
The logs are not needed by the TO SHIPPED TO ... STANDBY or TO APPLIED ON ... STANDBY deletion policy. If neither standby deletion policy is set, then this condition is always met.
If you configure the deletion policy with this clause, then a BACKUP ARCHIVELOG command copies the logs unless integer backups exist on the specified device type. If integer backups of the logs exist, then the BACKUP ARCHIVELOG command skips the logs. In this way, the archived log deletion policy functions as a default NOT BACKED UP integer TIMES clause on the BACKUP ARCHIVELOG command. You can override this deletion policy by specifying FORCE option on the BACKUP command.
See Also: deviceSpecifier
TO NONE
Disables the archived log deletion policy. This is the default setting.
Archived redo log files can be located inside or outside of the fast recovery area. Logs in any location can be deleted by manual commands. Only logs in the fast recovery area can be deleted automatically by the database.
When the deletion policy is set to NONE, RMAN considers archived redo log files as eligible for deletion if they meet both of the following conditions:
The archived redo log files, whether in the fast recovery area or outside of it, have been transferred to the required remote destinations specified by LOG_ARCHIVE_DEST_n.
The archived redo log files in the fast recovery area have been backed up at least once to disk or SBT or the logs are obsolete according to the backup retention policy.
The backup retention policy considers logs obsolete only if the logs are not needed by a guaranteed restore point and the logs are not needed by Flashback Database. Archived redo log files are needed by Flashback Database if the logs were created later than SYSDATE-'DB_FLASHBACK_RETENTION_TARGET'.
For example, suppose that archived redo log files have been transferred to required remote destinations. The logs are obsolete according to the recovery window retention policy, but have not been backed up. In this case, the logs are eligible for deletion. Alternatively, suppose that the logs are obsolete and have been backed up to SBT, but have not been transferred to required remote destinations. In this case, the logs are not eligible for deletion.
If the deletion policy is set to NONE, and if you execute a deletion command for archived redo log files outside the fast recovery area, then RMAN obeys only the conditions specified on the deletion command.
TO SHIPPED TO
[ALL] STANDBY Specifies that archived redo log files are eligible for deletion if both of the following conditions are met:
The archived redo log files have been transferred to the required remote destinations.
The logs are not needed by the BACKED UP ... TIMES TO DEVICE TYPE deletion policy. If the BACKED UP deletion policy is not set, then this condition is always met.
Which remote destinations are considered depends on the following criteria:
If you do not specify ALL, then the archived redo log files are eligible for deletion after transfer to mandatory remote destinations only.
If you specify ALL, then the logs are eligible for deletion after transfer to all remote destinations, whether mandatory or not.
Note: It is invalid to specify the TO SHIPPED clause in combination with NONE or the TO APPLIED clause.
See Also: Oracle Data Guard Concepts and Administration for details