RMAN Commands , 32 of 59

LIST

Purpose

To display information about backup sets, proxy copies, and image copies recorded in the repository. The LIST command displays the files against which you can run CROSSCHECK and DELETE commands. Use this command to list:

Backups and copies that do not have the status AVAILABLE in the RMAN repository
Backups and copies of datafiles that are available and can possibly be used in a restore operation
Specified archived logs, backup sets, backup pieces, control file copies, datafile copies, and proxy copies
Backups and copies restricted by tag, completion time, recoverability, or device
Incarnations of a specified database or of all databases known to the catalog

RMAN records the output to either standard output or the message log, but not to both at the same time. You can control how the output is organized (BY BACKUP or BY FILE) as well as the level of detail in the output (VERBOSE or SUMMARY).

See Also:

Oracle9i Recovery Manager User's Guide to learn how to make lists and reports, and "cmdLine"

Restrictions and Usage Notes

Execute LIST only at the RMAN prompt.
RMAN must be connected to the target database. If RMAN is connected in NOCATALOG mode, then the database must be mounted. If RMAN is connected to a recovery catalog, then the target instance must be started but the target database does not need to be mounted.

Keywords and Parameters

Syntax Element	Description
`INCARNATION`	Displays information about the incarnations of a database. Whenever you open a database with the `RESETLOGS` option, then you create a new incarnation of the database. So, if `LIST` `INCARNATION` displays `n` incarnations of a specified database, then you have reset the online logs for this database `n`-1 times. The `LIST` output includes the primary keys of all database incarnation records for the specified database name. Use the key in a `RESET DATABASE` command to change the incarnation that RMAN considers to be current to a previous incarnation. See Also: Table 2-18 for an explanation of the column headings of the `LIST` `INCARNATION` output table
`OF` `DATABASE` `'database_name'`	Specifies the name of the database. If you do not specify the `OF` `DATABASE` option, then the command lists all databases registered in the recovery catalog.
`EXPIRED`	Displays backup sets, proxy copies, and image copies marked in the repository as `EXPIRED`, that is, "not found." To ensure that `LIST` `EXPIRED` shows up-to-date output, issue a `CROSSCHECK` command periodically. When you issue a `CROSSCHECK` command, RMAN searches on disk and tape for the backups and copies recorded in the repository. If it does not find them, then it updates their repository records to status `EXPIRED`.
`listObjectSpec`	Specifies the type of object or objects that you are listing. See Also: "recordSpec"
`BACKUP`	Displays information about backups: backup sets, backup pieces, and proxy copies. The output displays a unique key for each. The `LIST` `BACKUP` command defaults to `BY` `BACKUP`. Unless you specify the `RECOVERABLE` option, RMAN lists both usable and unusable backups, even those that cannot be restored, are expired or unavailable, or are incrementals that cannot be restored because their parent full backup or copy no longer exists. See Also: "LIST Output" for an explanation of the column headings of the `LIST` output tables. Use the `KEY` column of the output to obtain the primary key usable in the `CHANGE` and `DELETE` commands.
`COPY`	Displays information about datafile copies, archived redo logs, and image copies of archived redo logs. By default, `LIST` `COPY` displays copies of all database files and archived redo logs. Both usable and unusable image copies are included in the output, even those that cannot be restored or are expired or unavailable. See Also: Table 2-15 and Table 2-17 for an explanation of the column headings of the `LIST` `COPY` output tables
`OF` listObjList	Restricts the list of objects operated on to the object type specified in the `listObjList` clause. If you do not specify an object, then `LIST` defaults to `OF` `DATABASE` `CONTROLFILE` `ARCHIVELOG` `ALL`. Note: The `LIST` `BACKUP` `...` `LIKE` command is not valid. The only valid exception is `LIST` `BACKUP` `OF` `ARCHIVELOG` `LIKE`. See Also: "listObjList"
`archivelogRecordSpecifier`	Displays information about a range of archived redo logs.
`listBackupOption`	Specifies the type of object or objects that you are listing. See Also: "recordSpec"
`BY` `BACKUP`	Lists backup sets, then the contents of each backup set (pieces and files), and then proxy copies. This is the default option for `LIST` `BACKUP`. If you specify the `SUMMARY` option, then this command is equivalent to `LIST` `BACKUP` `SUMMARY`.
`VERBOSE`	Gives detailed description of contents of each backup set (default).
`SUMMARY`	Gives a one-line summary for each datafile (when using `BY` `FILE`) or backup (when using `BY` `BACKUP`).
`BY` `FILE`	Lists a datafile, then its backup sets (including recovery action info), and then proxy copies.
maintQualifier	Restricts the range of the listing. Refer to "maintQualifier".
`RECOVERABLE`	Specifies datafile backups or copies whose status in the repository is `AVAILABLE` and which can be used for restore and recovery in the target database's current incarnation. This list includes all backups and copies except the following: Incremental backups that have no valid parent to which the incremental can be applied. Full backups that were taken before the most recent `RESETLOGS`, and which have been in online read/write status sometime between the time the backup was taken and the `RESETLOGS`. In other words, a backup taken prior to the `RESETLOGS` can be used in the current incarnation only if the file was offline clean or read at the time of the backup, and was never made read/write again before the `RESETLOGS`.
`untilClause`	Specifies an end time, SCN, or log sequence number. See "untilClause".
recordSpec	Specifies the object or objects that you are listing. Refer to "recordSpec".

LIST Output

The information that appears in the output is shown in the following tables:

Table 2-3 List of Backup Sets (for datafile backup sets)

Column	Indicates
`BS` `Key`	A unique key identifying this backup set. If you are connected to a recovery catalog, then `BS` `Key` is the primary key of the backup set in the catalog. It corresponds to `BS_KEY` in the `RC_BACKUP_SET` view. If you are connected in the default `NOCATALOG` mode, then `BS` `Key` displays the `RECID` from `V$BACKUP_SET`.
`Type`	The type of backup: `Full` or `Incr` (incremental). Note: Column only included in datafile backup sets.
`LV`	The level of the backup: `NULL` for nonincrementals, level `0`-`4` for incrementals. Note: Column only included in datafile backup sets.
`Size`	The size of the backup in bytes. Note: Column only included in datafile backup sets.
`Device` `Type`	The type of device on which the backup was made, for example, `DISK` or `sbt`.
`Elapsed` `Time`	The duration of the backup.
`Completion` `Time`	The date and time that the backup set completed. Note that the format of this field depends on the `NLS_LANG` and `NLS_DATE_FORMAT` environment settings.

Table 2-4 List of Backup Pieces (for sets with only one piece)

Column	Indicates
`BP` `Key`	A unique identifier for this backup piece in the recovery catalog or target database control file. If you are connected to a recovery catalog, then `BP` `Key` is the primary key of the backup piece in the catalog. It corresponds to `BP_KEY` in the `RC_BACKUP_PIECE` view. If you are connected in `NOCATALOG` mode, then `BP` `Key` displays the `RECID` from `V$BACKUP_PIECE`. Note: The values for `KEY` in the recovery catalog and the control file are different.
`Status`	The backup piece status: `AVAILABLE`, `UNAVAILABLE`, or `EXPIRED` (refer to the `CHANGE`, `CROSSCHECK,` and `DELETE` commands for an explanation of each status).
`Tag`	The tag applied to the backup set; `NULL` if none. Note that tag names are not case sensitive and display in all uppercase.
`Piece` `Name`	The filename or handle of the backup piece.
`Controlfile` `Included`	A control file is included in the backup. Note: This row appears only if the current control file is included in the backup.
`SPFILE` `Included`	A server parameter file is included in the backup.
`Ckp` `SCN`	The SCN of the backup control file checkpoint. All database changes recorded in the redo records before the specified SCN are reflected in this control file. Note: This row appears only if the current control file is included in the backup.
`Ckp` `time`	The time of the backup control file checkpoint. All database changes recorded in the redo records before the specified time are reflected in this control file. Note: This row appears only if the current control file is included in the backup.

Table 2-5 List of Datafiles in backup set ...

Column	Indicates
`File`	The number of the file that was backed up.
`LV`	The level of the backup: `NULL` for nonincrementals, level 0-4 for incrementals.
`Type`	The type of backup: `Full` or `Incr` (incremental).
`Ckp` `SCN`	The checkpoint of the datafile at the time it was backed up. All database changes prior to the SCN have been written to the file; changes after the specified SCN have not been written to the file.
`Ckp` `Time`	The checkpoint of the datafile at the time it was backed up. All database changes prior to the time have been written to the file; changes after the specified time have not been written to the file.
`Name`	The location where this file would be restored now if it were restored from this backup set and no `SET` `NEWNAME` command was entered. See Also: "SET"

Table 2-6 List of Archived Logs in backup set ...

Column	Indicates
`Thrd`	The thread number of the redo log.
`Seq`	The log sequence number of the archived log.
`Low` `SCN`	The lowest SCN in the archived log.
`Low` `Time`	The time when Oracle switched into the redo log having this sequence number.
`Next` `SCN`	The low SCN of the next archived log sequence.
`Next` `Time`	The low time of the next archived log sequence.

Table 2-7 Backup Set Copy ... of backup set ... (only if multiple pieces)

Column	Indicates
`Device` `Type`	The type of device on which the backup was made, for example, `DISK` or `sbt`.
`Elapsed` `Time`	The duration of the backup.
`Completion` `Time`	The date and time that the backup set completed. Note that the format of this field depends on the `NLS_LANG` and `NLS_DATE_FORMAT` environment settings.
`Tag`	The tag applied to the backup set; `NULL` if none. Note that tag names are not case sensitive and display in all uppercase.

Table 2-8 List of Backup Pieces for backup set ... Copy ... (mult. pieces)

Column	Indicates
`BP` `Key`	A unique identifier for this backup piece in the recovery catalog or target database control file. If you are connected to a recovery catalog, then `BP` `Key` is the primary key of the backup piece in the catalog. It corresponds to `BP_KEY` in the `RC_BACKUP_PIECE` view. If you are connected in `NOCATALOG` mode, then `BP` `Key` displays the `RECID` from `V$BACKUP_PIECE`. Note: The values for `KEY` in the recovery catalog and the control file are different.
`Pc#`	The number of the backup piece in the backup set.
`Status`	The backup piece status: `AVAILABLE`, `UNAVAILABLE`, or `EXPIRED` (refer to the `CHANGE`, `CROSSCHECK,` and `DELETE` commands for an explanation of each status).
`Piece` `Name`	The filename or handle of the backup piece.

Table 2-9 List of Proxy Copies

Column	Indicates
`PC` `Key`	A unique key identifying this proxy copy. If you are connected to a catalog, then `PC` `Key` is the primary key of the proxy copy in the catalog. It corresponds to `XDF_KEY` in the `RC_PROXY_DATAFILE` view or `XCF_KEY` in the `RC_PROXY_CONTROLFILE` view. If you are connected in `NOCATALOG` mode, then `PC` `Key` displays the `RECID` from `V$PROXY_DATAFILE`.
`File`	The absolute datafile number of the file that was copied.
`Status`	The proxy copy status: `AVAILABLE`, `UNAVAILABLE`, or `EXPIRED` (see the `CHANGE`, `CROSSCHECK`, and `DELETE` commands for an explanation of each status).
`Completion` `Time`	The date and time that the backup set completed. Note that the format of this field depends on the `NLS_LANG` and `NLS_DATE_FORMAT` environment settings.
`Ckp` `SCN`	The SCN of the proxy copy control file checkpoint. All database changes recorded in the redo records before the specified SCN are reflected in this control file.
`Ckp` `time`	The time of the proxy copy control file checkpoint. All database changes recorded in the redo records before the specified time are reflected in this control file.
`Datafile name`	The location where this file would be restored now if it were restored from this backup set and no `SET` `NEWNAME` command was entered. See Also: "SET"
`Handle`	The media manager's handle for the proxy copy.
`Tag`	The tag applied to the proxy copy; `NULL` if none. Note that tag names are not case sensitive and display in all uppercase.

Table 2-10 List of Backup Sets (LIST BACKUP ... SUMMARY)

Column	Indicates
`Key`	A unique key identifying this backup set. If you are connected to a recovery catalog, then `BS` `Key` is the primary key of the backup set in the catalog. It corresponds to `BS_KEY` in the `RC_BACKUP_SET` view. If you are connected in `NOCATALOG` mode, then `BS` `Key` displays the `RECID` from `V$BACKUP_SET`.
`TY`	The type of backup: backup set (`B`) or proxy copy (`P`).
`LV`	The level of the backup: `NULL` for nonincrementals, level `0`-`4` for incrementals.
`S`	The status of the backup: `A` (available), `U` (unavailable), or `X` (all backup pieces in set expired). Refer to the `CHANGE`, `CROSSCHECK`, and `DELETE` commands for an explanation of each status.
`Device` `Type`	The type of device on which the backup was made, for example, `DISK` or `sbt`.
`Completion` `Time`	The date and time that the backup set completed. Note that the format of this field depends on the `NLS_LANG` and `NLS_DATE_FORMAT` environment settings.
`#Pieces`	The number of backup pieces in the backup set.
`#Copies`	The number of copies made of each backup piece in the set. The number is `1` if no duplexing was performed. Otherwise, the value ranges from `2` to `4`.
`Tag`	The tag applied to the backup set; `NULL` if none. An asterisk (*) indicates multiple copies with different tags. Note that tag names are not case sensitive and display in all uppercase.

Table 2-11 List of Backup Pieces (LIST BACKUPPIECE ...)

Column	Indicates
`BP` `Key`	A unique identifier for this backup piece in the recovery catalog or target database control file. If you are connected to a catalog, then `BP` `Key` is the primary key of the backup piece in the catalog. It corresponds to `BP_KEY` in the `RC_BACKUP_PIECE` view. If you are connected in `NOCATALOG` mode, then `BP` `Key` displays the `RECID` from `V$BACKUP_PIECE`. Note: The values for `KEY` in the recovery catalog and the control file are different.
`BS` `Key`	A unique key identifying this backup set. If you are connected to a recovery catalog, then `BS` `Key` is the primary key of the backup set in the catalog. It corresponds to `BS_KEY` in the `RC_BACKUP_SET` view. If you are connected in `NOCATALOG` mode, then `BS` `Key` displays the `RECID` from `V$BACKUP_SET`.
`Pc#`	The number of the backup piece in the backup set.
`Cp#`	The copy number of this backup piece in the backup set. The number is `1` if no duplexing was performed. Otherwise, the value ranges from `2` to `4`.
`Status`	The backup piece status: `AVAILABLE`, `UNAVAILABLE`, or `EXPIRED` (see the `CHANGE`, `CROSSCHECK`, and `DELETE` commands for an explanation of each status).
`Device` `Type`	The type of device on which the backup was made, for example, `DISK` or `sbt`.
`Piece` `Name`	The filename or handle of the backup piece.

Table 2-12 List of Datafile Backups (LIST BACKUP ... BY FILE)

Column	Indicates
`File`	The absolute datafile number.
`Key`	A unique key identifying this backup set. If you are connected to a recovery catalog, then `Key` is the primary key of the backup set in the catalog. It corresponds to `BS_KEY` in the `RC_BACKUP_SET` view. If you are connected in `NOCATALOG` mode, then `Key` displays the `RECID` from `V$BACKUP_SET`.
`TY`	The type of backup: backup set (`B`) or proxy copy (`P`).
`LV`	The backup level: `F` for nonincrementals, level `0`-`4` for incrementals.
`S`	The status of the backup: `A` (available), `U` (unavailable), or `X` (all backup pieces in set expired). Refer to the `CHANGE`, `CROSSCHECK`, and `DELETE` commands for an explanation of each status.
`Ckp` `SCN`	The checkpoint of the datafile at the time it was backed up. All database changes prior to the SCN have been written to the file; changes after the specified SCN have not been written to the file.
`Ckp` `Time`	The checkpoint of the datafile at the time it was backed up. All database changes prior to the time have been written to the file; changes after the specified time have not been written to the file.
`#Pieces`	The number of backup pieces in the backup set.
`#Copies`	The number of copies made of each backup piece in the set. The number is `1` if no duplexing was performed. Otherwise, the value ranges from `2` to `4`.
`Tag`	The tag applied to the backup set; `NULL` if none. Note that tag names are not case sensitive and display in all uppercase.

Table 2-13 List of Archived Log Backups (LIST BACKUP ... BY FILE)

Column	Indicates
`Thrd`	The thread number of the redo log.
`Seq`	The log sequence number of the archived log.
`Low` `SCN`	The lowest SCN in the archived log.
`Low` `Time`	The time when Oracle switched into the redo log having this sequence number.
`BS` `Key`	A unique key identifying this backup set. If you are connected to a recovery catalog, then `BS` `Key` is the primary key of the backup set in the catalog. It corresponds to `BS_KEY` in the `RC_BACKUP_SET` view. If you are connected in `NOCATALOG` mode, then `BS` `Key` displays the `RECID` from `V$BACKUP_SET`.
`S`	The status of the backup: `A` (available), `U` (unavailable), or `X` (all backup pieces in set expired). Refer to the `CHANGE`, `CROSSCHECK`, and `DELETE` commands for an explanation of each status.
`#Pieces`	The number of backup pieces in the backup set.
`#Copies`	The number of copies made of each backup piece in the set. The number is `1` if no duplexing was performed. Otherwise, the value ranges from `2` to `4`.
`Tag`	The tag applied to the backup set; `NULL` if none. Note that tag names are not case sensitive and display in all uppercase.

Table 2-14 List of Controlfile Backups (LIST BACKUP ... BY FILE)

Column	Indicates
`CF` `Ckp` `SCN`	Checkpoint SCN of the control file.
`Ckp` `Time`	The log sequence number of the archived log.
`BS` `Key`	A unique key identifying this backup set. If you are connected to a recovery catalog, then `BS` `Key` is the primary key of the backup set in the catalog. It corresponds to `BS_KEY` in the `RC_BACKUP_SET` view. If you are connected in `NOCATALOG` mode, then `BS` `Key` displays the `RECID` from `V$BACKUP_SET`.
`S`	The status of the backup: `A` (available), `U` (unavailable), or `X` (all backup pieces in set expired). Refer to the `CHANGE`, `CROSSCHECK`, and `DELETE` commands for an explanation of each status.
`#Pieces`	The number of backup pieces in the backup set.
`#Copies`	The number of copies made of each backup piece in the set. The number is `1` if no duplexing was performed. Otherwise, the value ranges from `2` to `4`.
`Tag`	The tag applied to the backup set; `NULL` if none. Note that tag names are not case sensitive and display in all uppercase.

Table 2-15 List of Datafile Copies

Column	Indicates
`Key`	The unique identifier for the datafile copy. Use this value in a `CHANGE` command to alter the status of the datafile copy. If you are connected to a recovery catalog, then `Key` is the primary key of the datafile copy in the catalog. It corresponds to `CDF_KEY` in the `RC_DATAFILE_COPY` view. If you are connected in `NOCATALOG` mode, then `Key` displays the `RECID` from `V$DATAFILE_COPY`. Note: The values for `KEY` in the recovery catalog and the control file are different.
`File`	The file number of the datafile from which this copy was made.
`S`	The status of the copy: `A` (available), `U` (unavailable), or `X` (expired). Refer to the `CHANGE`, `CROSSCHECK`, and `DELETE` commands for an explanation of each status.
`Completion` `Time`	The date and time that the copy completed. Note that the value of this field is sensitive to the `NLS_LANG` and `NLS_DATE_FORMAT` environment variables.
`Ckp` `SCN`	The checkpoint of this datafile when it was copied. All database changes prior to this SCN have been written to this datafile.
`Ckp` `TIME`	The checkpoint of this datafile when it was copied. All database changes prior to this time have been written to this datafile.
`Name`	The filename of the datafile copy.

Table 2-16 List of Controlfile Copies

Column	Indicates
`Key`	The unique identifier for the control file copy. Use this value in a `CHANGE` command to alter the status of the copy. If you are connected to a recovery catalog, then `Key` is the primary key of the control file copy in the catalog. It corresponds to `CCF_KEY` in the `RC_CONTROLFILE_COPY` view. If you are connected in `NOCATALOG` mode, then `Key` displays the `RECID` from `V$DATAFILE_COPY`. Note: The values for `Key` in the recovery catalog and the control file are different.
`S`	The status of the copy: `A` (available), `U` (unavailable), or `X` (expired). Refer to the `CHANGE`, `CROSSCHECK`, and `DELETE` commands for an explanation of each status.
`Completion` `Time`	The date and time that the copy completed. Note that the value of this field is sensitive to the `NLS_LANG` and `NLS_DATE_FORMAT` environment variables.
`Ckp` `SCN`	The checkpoint of this control file when it was copied.
`Ckp` `TIME`	The checkpoint of this control file when it was copied.
`Name`	The filename of the control file copy.

Table 2-17 List of Archived Log Copies

Column	Indicates
`Key`	The unique identifier for this archived redo log copy. Use this value in a `CHANGE` command to alter the status of the copy. If you are connected to a recovery catalog, then `Key` is the primary key of the backup set in the catalog. It corresponds to `AL_KEY` in the `RC_ARCHIVED_LOG` view. If you are connected in `NOCATALOG` mode, then `Key` displays the `RECID` from `V$ARCHIVED_LOG`. Note: The values for `Key` in the recovery catalog and the control file are different.
`Thrd`	The redo log thread number.
`Seq`	The log sequence number.
`S`	The status of the copy: `A` (available), `U` (unavailable), or `X` (expired). Refer to the `CHANGE`, `CROSSCHECK`, and `DELETE` commands for an explanation of each status.
`Low` `Time`	The time when Oracle switched into the redo log having this sequence number.
`Name`	The filename of the archived redo log copy.

Table 2-18 List of Database Incarnations

Column	Indicates
`DB` `Key`	When combined with the `Inc` `Key`, the unique key by which RMAN identifies the database incarnation in the recovery catalog. Use this key to unregister a database, that is, delete all the rows associated with that database from the recovery catalog.
`Inc` `Key`	When combined with `DB` `Key`, the unique key by which RMAN identifies the database incarnation in the recovery catalog. Use this key in `RESET DATABASE` `...` `TO` `INCARNATION` when recovering the database to a time before the most recent `RESETLOGS`.
`DB` `Name`	The database name as listed in the `DB_NAME` parameter.
`DB` `ID`	The database identification number, which Oracle generates automatically at database creation.
`CUR`	Whether the incarnation is the current incarnation of the database.
`Reset` `SCN`	The SCN at which the incarnation was created.
`Reset` `Time`	the time at which the incarnation was created.

Examples

Listing Backups: Example

This example lists all backups in default verbose mode:

LIST BACKUP;

List of Backup Sets
===================

BS Key  Device Type Elapse Time Completion Time
------- ----------- ----------- ---------------
236     DISK        00:00:08    21-SEP-00      
        BP Key: 237   Status: AVAILABLE   Tag: TAG20011121T053733
        Piece Name: /oracle/oradata/09c5unih_1_1

  List of Archived Logs in backup set 236
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    141     49173      21-SEP-01 49784      21-SEP-01
  1    142     49784      21-SEP-01 50331      21-SEP-01

BS Key  Type LV Size       Device Type Elapse Time Completion Time
------- ---- -- ---------- ----------- ----------- ---------------
244     Full    61M        DISK        00:00:18    21-SEP-01      
        BP Key: 245   Status: AVAILABLE   Tag: TAG20011121T053816
        Piece Name: /oracle/oradata/0ac5unj5_1_1
  Controlfile Included: Ckp SCN: 51554        Ckp time: 21-SEP-01
  SPFILE Included: Modification time: 21-SEP-01
  List of Datafiles in backup set 244
  File LV Type Ckp SCN    Ckp Time  Name
  ---- -- ---- ---------- --------- ----
  1       Full 51555      21-SEP-01 /oracle/oradata/trgt/system01.dbf
  2       Full 51555      21-SEP-01 /oracle/oradata/trgt/undotbs_01.dbf

List of Proxy Copies
====================

PC Key  File Status      Completion time     Ckp SCN    Ckp time
------- ---- ----------- ------------------- ---------- -------------------
552     1    AVAILABLE   10/07/2001 03:05:21 78022      10/07/2001 03:05:10  
             Datafile name: /oracle/oradata/trgt/system01.dbf 
             Handle: 0jb8l876_1_0        

561     1    AVAILABLE   10/07/2001 03:38:22 78025      10/07/2001 03:38:09  
             Datafile name: /oracle/oradata/trgt/system01.dbf 
             Handle: 0lb8la51_1_0        
             Tag: WKLYBKUP

Listing a Summary of Backups: Example

The following example lists a summarized version of all RMAN backups:

LIST BACKUP SUMMARY;

List of Backups
===============
Key     TY LV S Device Type Completion Time      #Pieces #Copies Tag
------- -- -- - ----------- -------------------- ------- ------- ---
35      B  A  A SBT_TAPE    FEB 08 2002 05:37:37 1       1       TAG20020208T053733
42      B  F  A SBT_TAPE    FEB 08 2002 05:38:21 1       1       TAG20020208T053744

Listing Backups by File: Example

This example groups all backups by file:

LIST BACKUP BY FILE;

List of Datafile Backups
========================

File Key     TY LV S Ckp SCN    Ckp Time          #Pieces #Copies Tag
---- ------- -  -- - ---------- ----------------- ------- ------- ---
1    502     B  0  A 37973      09/28/01 19:28:36 1       3       *
     552     P  F  X 78022      10/07/01 03:05:10 1       1       DF_1
     561     P  0  U 78025      10/07/01 03:38:09 2       1       DF_1
2    502     B  0  A 37973      09/28/01 19:28:36 1       2       *
     562     P  0  U 78027      10/07/01 03:38:22 1       1       DF_2

List of Archived Log Backups
============================

Thrd Seq     Low SCN    Low Time  BS Key  S #Pieces #Copies Tag
---- ------- ---------- --------- ------- - ------- ------- ---
1    141     49463      14-SEP-01 213     A 1       1       TAG20011114T125431

List of Controlfile Backups
===========================

CF Ckp SCN Ckp Time  BS Key  S #Pieces #Copies Tag
---------- --------- ------- - ------- ------- ---
51593      14-SEP-01 222     A 1       1      

List of SPFILE Backups
======================

Modification Time    BS Key  S #Pieces #Copies Tag
-------------------- ------- - ------- ------- ---
OCT 08 2001 05:38:55 251     A 1       1

Listing Archived Redo Logs: Example

The following example lists archived logs and copies of logs:

LIST COPY OF DATABASE ARCHIVELOG ALL;

List of Archived Log Copies
Key     Thrd Seq     S Low Time  Name
------- ---- ------- - --------- ----
153     1    30      A 14-SEP-01 /oracle/oradata/trgt/arch/archive1_30.dbf
154     1    31      A 14-SEP-01 /oracle/oradata/trgt/arch/archive1_31.dbf

Listing Backups of Specific Datafiles: Example

The following example lists backups of datafile 3 in summary mode:

LIST BACKUP OF DATAFILE 3 SUMMARY;

List of Backups
===============

Key     TY LV S Device Type Completion Time #Pieces #Copies Tag
------- -- -- - ----------- --------------- ------- ------- ---
180     B  0  A DISK        14-SEP-01       1       2       TAG20011114T125431

Listing Database Incarnations: Example

This example lists all database incarnations recorded in the recovery catalog:

LIST INCARNATION;

List of Database Incarnations
DB Key  Inc Key DB Name  DB ID            CUR Reset SCN  Reset Time
------- ------- -------- ---------------- --- ---------- ----------
1       2       RDBMS    674879952        YES 1          14-SEP-01