To query details about past and current RMAN jobs: -- 查询RMAN备份的作业的具体细节
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
Responding to an Instance Crash During File Creation -- 实例CRASH时正在创建文件到RECOVERY AREA
As a rule, the fast recovery area is self-maintaining. When an instance crashes during
the creation of a file in the fast recovery area, however, the database may leave the file
in the fast recovery area. When this situation occurs, the alert log contains the
following error, where location is the location of the fast recovery area:
ORA-19816: WARNING: Files may exist in location that are not known to database.
In such a situation, use the RMAN command CATALOG RECOVERY AREA to recatalog
any such files. If the file header of the file in question is corrupted, then delete the file
manually with an operating system utility.
-- 重新CATALOG进去