RMAN EXPIRED VS OBSOLETE

EXPIRED:
If you run CROSSCHECK, and if RMAN cannot locate the files, then it updates their
records in the RMAN repository to EXPIRED status. You can then use the DELETE
EXPIRED command to remove records of expired backups and copies from the RMAN
repository.

OBSOLETE:
backups that are no longer needed to satisfy specified recoverability requirements. You can delete files obsolete according to the configured default retention policy, or another retention policy that you specify

Fast Recovery Area usage

SELECT * FROM V$RECOVERY_AREA_USAGE;
FILE_TYPE PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
------------ ------------------ ------------------------- ---------------
CONTROLFILE 0 0 0
ONLINELOG 2 0 22
ARCHIVELOG 4.05 2.01 31
BACKUPPIECE 3.94 3.86 8
IMAGECOPY 15.64 10.43 66
FLASHBACKLOG .08 0 1

Backup Size

Query the V$RMAN_BACKUP_JOB_DETAILS view for the size of the backups in an
RMAN session.
If you run BACKUP DATABASE, then
V$RMAN_BACKUP_JOB_DETAILS.OUTPUT_BYTES shows the total size of backup
sets written by the backup job for the database that you are backing up. To view
backup set sizes for all registered databases, query
RC_RMAN_BACKUP_JOB_DETAILS.
The following query shows the backup job speed ordered by session key, which is
the primary key for the RMAN session. The columns in_sec and out_sec
display the data input and output per second.
COL in_size FORMAT a10
COL out_size FORMAT a10
SELECT SESSION_KEY,
INPUT_TYPE,
COMPRESSION_RATIO,
INPUT_BYTES_DISPLAY in_size,
OUTPUT_BYTES_DISPLAY out_size
FROM V$RMAN_BACKUP_JOB_DETAILS
ORDER BY SESSION_KEY;
The following sample output shows the speed of the backup jobs:
SESSION_KEY INPUT_TYPE COMPRESSION_RATIO IN_SIZE OUT_SIZE
----------- ------------- ----------------- ---------- ----------
10 DATAFILE FULL 1 602 50M 602.58M
17 DB FULL 1.137 634.80M 558.13M

Backup Job Speed

Query the V$RMAN_BACKUP_JOB_DETAILS view for the rate of backup jobs in an
RMAN session.

The following query shows the backup job speed ordered by session key, which is
the primary key for the RMAN session. The columns in_sec and out_sec
display the data input and output per second.
COL in_sec FORMAT a10
COL out_sec FORMAT a10
COL TIME_TAKEN_DISPLAY FORMAT a10
SELECT SESSION_KEY,
OPTIMIZED,
COMPRESSION_RATIO,
INPUT_BYTES_PER_SEC_DISPLAY in_sec,
OUTPUT_BYTES_PER_SEC_DISPLAY out_sec,
TIME_TAKEN_DISPLAY
FROM V$RMAN_BACKUP_JOB_DETAILS
ORDER BY SESSION_KEY;
The following sample output shows the speed of the backup jobs:
SESSION_KEY OPT COMPRESSION_RATIO IN_SEC OUT_SEC TIME_TAKEN
----------- --- ----------------- ---------- ---------- ----------
9 NO 1 8.24M 8.24M 00:01:14
16 NO 1.3273 6.77M 5.10M 00:01:45
113 NO 1 2.99M 2.99M 00:00:44

Backup Job History

To query details about past and current RMAN jobs:
1. Connect SQL*Plus to the database whose backup history you intend to query.
2. Query the V$RMAN_BACKUP_JOB_DETAILS view for information about the
backup type, status, and start and end time.
The following query shows the backup job history ordered by session key, which
is the primary key for the RMAN session:
COL STATUS FORMAT a9
COL hrs FORMAT 999.99
SELECT SESSION_KEY, INPUT_TYPE, STATUS,
TO_CHAR(START_TIME,'mm/dd/yy hh24:mi') start_time,
TO_CHAR(END_TIME,'mm/dd/yy hh24:mi') end_time,
ELAPSED_SECONDS/3600 hrs
FROM V$RMAN_BACKUP_JOB_DETAILS
ORDER BY SESSION_KEY;
The following sample output shows the backup job history:
SESSION_KEY INPUT_TYPE STATUS START_TIME END_TIME HRS
----------- ------------- --------- -------------- -------------- -------
9 DATAFILE FULL COMPLETED 04/18/07 18:14 04/18/07 18:15 .02
16 DB FULL COMPLETED 04/18/07 18:20 04/18/07 18:22 .03
113 ARCHIVELOG COMPLETED 04/23/07 16:04 04/23/07 16:05 .01