Thank you for visiting Spatial DBA - Oracle and ArcSDE.
Please visit Oracle DBA Tips (http://www.oracledbatips.com) for more Oracle DBA Tips.
==================================================================
V$RMAN_BACKUP_JOB_DETAILS displays details about backup jobs.
Column
|
Datatype
|
Description
|
SESSION_KEY | NUMBER |
Session identifier
|
SESSION_RECID | NUMBER |
Together, with
SESSION_KEY and SESSION_STAMP, used to uniquely identify job output from V$RMAN_OUTPUT |
SESSION_STAMP | NUMBER |
Together, with
SESSION_KEY and SESSION_RECID, used to uniquely identify job output from V$RMAN_OUTPUT |
COMMAND_ID | VARCHAR2(33) |
Either a user-specified SET COMMAND ID or a unique command ID generated by RMAN
|
START_TIME | DATE |
Start time of the first BACKUP command in the job
|
END_TIME | DATE |
End time of the last BACKUP command in the job
|
INPUT_BYTES | NUMBER |
Sum of all input file sizes backed up by this job
|
OUTPUT_BYTES | NUMBER |
Output size of all pieces generated by this job
|
STATUS_WEIGHT | NUMBER |
Used internally by Enterprise Manager
|
OPTIMIZED_WEIGHT | NUMBER |
Used internally by Enterprise Manager
|
OBJECT_TYPE_WEIGHT | NUMBER |
Used internally by Enterprise Manager
|
OUTPUT_DEVICE_TYPE | VARCHAR2(17) |
Can be DISK, SBT, or *. An * indicates more than one device (in most cases, it will be DISK or SBT).
|
AUTOBACKUP_COUNT | NUMBER |
Number of autobackups performed by this job
|
AUTOBACKUP_DONE | VARCHAR2(3) |
YES or NO, depending upon whether or not a control file autobackup was done as part of this backup job
|
STATUS | VARCHAR2(23) |
One of the following values:
· RUNNING WITH WARNINGS
· RUNNING WITH ERRORS
· COMPLETED
· COMPLETED WITH WARNINGS
· COMPLETED WITH ERRORS
· FAILED
|
INPUT_TYPE | VARCHAR2(13) |
Contains one of the following values. If the user command does not satisfy one of them, then preference is given in order, from top to bottom of the list.
· DB FULL
· RECVR AREA
· DB INCR
· DATAFILE FULL
· DATAFILE INCR
· ARCHIVELOG
· CONTROLFILE
· SPFILE
|
OPTIMIZED | VARCHAR2(3) |
YES or NO, depending on whether optimization was applied. Applicable to backup jobs only.
|
ELAPSED_SECONDS | NUMBER |
Number of elapsed seconds
|
COMPRESSION_RATIO | NUMBER |
Compression ratio
|
INPUT_BYTES_PER_SEC | NUMBER |
Input read-rate-per-second
|
OUTPUT_BYTES_PER_SEC | NUMBER |
Output write-rate-per-second
|
INPUT_BYTES_DISPLAY | VARCHAR2(4000) |
Values in user-displayable form. They will be converted to a format of nM, nG, nT, nP, and so on.
|
OUTPUT_BYTES_DISPLAY | VARCHAR2(4000) |
Values in user-displayable form. They will be converted to a format of nM, nG, nT, nP, and so on
|
INPUT_BYTES_PER_SEC_DISPLAY | VARCHAR2(4000) |
Input read-rate-per-second. These values are in user-displayable form. They will be converted to a format of nM, nG, nT, nP, and so on.
|
OUTPUT_BYTES_PER_SEC_DISPLAY | VARCHAR2(4000) |
Output write-rate-per-second. These values are in user-displayable form. They will be converted to a format of nM, nG, nT, nP, and so on.
|
TIME_TAKEN_DISPLAY | VARCHAR2(4000) |
Time taken, shown in user-displayable format
|
Note:
- Useful query:
SELECT end_time, status, session_key, session_recid, session_stamp,
command_id, start_time, time_taken_display, input_type,
output_device_type, input_bytes_display, output_bytes_display,
output_bytes_per_sec_display
FROM V$RMAN_BACKUP_JOB_DETAILS;
|
select session_key, start_time, end_time, output_device_type, status, time_taken_display
from V$RMAN_BACKUP_JOB_DETAILS;
|
SESSION_KEY
|
START_TIME
|
END_TIME
|
OUTPUT_
DEVICE_TYPE
|
STATUS
|
TIME_TAKEN_
DISPLAY
|
17384
|
2008-07-15 6:00:19 PM
|
2008-07-16 5:14:57 AM
|
DISK
|
COMPLETED
|
11:14:38
|
17409
|
2008-07-17 6:00:20 PM
|
2008-07-18 4:23:06 AM
|
DISK
|
COMPLETED
|
10:22:46
|
18006
|
2008-09-04 6:01:09 PM
|
2008-09-05 3:59:53 AM
|
DISK
|
COMPLETED
|
09:58:44
|
18054
|
2008-09-09 9:04:44 AM
|
FAILED
| |||
18060
|
2008-09-09 1:14:13 PM
|
2008-09-09 2:24:57 PM
|
DISK
|
FAILED
|
01:10:44
|
18436
|
2008-10-09 6:00:20 PM
|
2008-10-10 2:08:14 AM
|
DISK
|
COMPLETED
|
08:07:54
|
18461
|
2008-10-11 6:01:06 PM
|
2008-10-12 2:04:21 AM
|
DISK
|
COMPLETED
|
08:03:15
|
- Accessing
V$RMAN_BACKUP_JOB_DETAILSwill cause a performance issue in Oracle 10.2.0.2 – 10.2.0.4. There are several notes related the view in Metalink.
The workaround is:
SQL> Connect / as sysdba
exec dbms_stats.DELETE_TABLE_STATS('SYS','X$KCCRSR'); exec dbms_stats.LOCK_TABLE_STATS('SYS','X$KCCRSR'); |
Oracle data dictionary views
Last updated: August 11, 2009
|
