Recovery Manager Command Syntax, 5 of 50

archivelogRecordSpecifier

Syntax

archlogRange::=

Purpose

A sub-clause used to specify a range of archived redo logs files for use in backup, restore, and maintenance operations.

Requirements

Use this clause only with the following commands:

Specifying a range of archived redo logs does not guarantee that RMAN includes all redo data in the range: for example, the last available archived log file may end before the end of the range, or an archived log file in the range may be missing. RMAN includes the archived redo logs it finds and does not issue a warning for missing files.

Keywords and Parameters

Query the V$ARCHIVED_LOG view to determine the timestamps, SCNs, and log sequence numbers for an archived log. For information on using the NLS_LANG and NLS_DATE_FORMAT environment variables to specify the format for the time, see the Oracle8i Reference.

Specifying Records by Time

This example deletes all archived redo logs older than two weeks:

change archivelog until time 'SYSDATE-14' delete;

Specifying Records by SCN

This example restores backup archived redo log files from tape that fall within a range of SCNs:

run {  
     allocate channel dev1 type 'sbt_tape';  
     restore archivelog 
          from SCN 500 until SCN 700; 
     release channel dev1;  
}

Specifying Records by Log Sequence Number

This example backs up all archived logs from sequence # 288 to sequence # 301 on thread 1 and deletes the archived logs after the backup is complete. If the backup fails, the logs are not deleted.

run {
     allocate channel dev1 type 'sbt_tape';
     backup archivelog 
          from logseq 288 until logseq 301 thread 1
          # delete original archived redo logs after backup completes
          delete input;
}

Specifying All Log Sequence Numbers in a Thread

This example crosschecks all archived redo logs in thread 1:

change archivelog from logseq 0 thread 1 crosscheck;

all	specifies exactly one copy of each distinct log sequence number. For example, if you execute backup archivelog all and you archive your logs to multiple destinations, RMAN backs up one copy of each log sequence number--not each archived copy of each log sequence number.
like 'string_pattern'	specifies a pathname for archived redo log files. Use this parameter when operating in OPS mode to specify which file system RMAN should access. For example, if nodes A, B, and C each archives locally, use the like parameter to inform the channel allocated on each node to back up only those logs that contain the specified pathname. See Also: "Backing Up in an OPS Environment" to learn how to make archived log backups in an OPS configuration, and Oracle8i Parallel Server Documentation Set: Oracle8i Parallel Server Concepts; Oracle8i Parallel Server Setup and Configuration Guide; Oracle8i Parallel Server Administration, Deployment, and Performance for more information about the Oracle Parallel Server configuration.
until time 'date_string'	specifies the end date for a sequence of archived redo log files. The time specified in the string must be formatted according to the NLS date format specification currently in effect. If you do not specify the from time parameter, the beginning time for the sequence will be the earliest available archived redo log. Query the V$ARCHIVED_LOG data dictionary view to determine the timestamps for the first and last entries in a log. See Also: Oracle8i Reference for information on using the NLS_LANG and NLS_DATE_FORMAT environment variables to specify the format for the time.
from time 'date_string'	specifies the beginning date for a sequence of archived redo log files. If you do not specify the until time parameter, RMAN will include all available log files beginning with the date specified in the from time parameter. Use the V$ARCHIVED_LOG data dictionary view to determine the timestamps for the first and last entries in a log file. See Also: Oracle8i Reference for information on using the NLS_LANG and NLS_DATE_FORMAT environment variables to specify the format for the time.
until SCN integer	specifies the ending SCN for a sequence of archived redo log files. If you do not specify the from SCN parameter, RMAN will use the lowest available SCN to begin the sequence.
from SCN integer	specifies the beginning SCN for a sequence of archived redo log files. If you do not specify the until SCN parameter, RMAN will include all available log files beginning with SCN specified in the from SCN parameter.
until logseq integer	specifies the terminating log sequence number for a sequence of archived redo log files. If you do not specify the from logseq parameter, RMAN uses the lowest available log sequence number to begin the sequence.
from logseq integer	specifies the beginning log sequence number for a sequence of archived redo log files. If you do not specify the until logseq parameter, RMAN will include all available log files beginning with log sequence number specified in the from logseq parameter. Note: You can specify all log sequence numbers in a thread by using the following syntax, where thread_number is an integer referring to the thread: archivelog from logseq 0 thread thread_number
thread integer	specifies the thread containing the archived redo log files you wish to include. You need only specify this parameter when running your database in an OPS configuration. Use the V$ARCHIVED_LOG data dictionary view to determine the thread number for an archived redo log record.