Tuesday, October 14, 2008

V$RMAN_CONFIGURATION

V$RMAN_CONFIGURATION lists information about RMAN persistent configuration settings.

Column

Datatype

Description

CONF#

NUMBER

A unique key identifying this configuration record within the target database that owns it.

NAME

VARCHAR2(65)

The type of configuration. All options of the CONFIGURE command are valid types except:

· CONFIGURE EXCLUDE (described in RC_TABLESPACE)

· CONFIGURE AUXNAME (described in RC_DATAFILE)

· CONFIGURE SNAPSHOT CONTROLFILE (stored only in control file)

VALUE

VARCHAR2(1025)

The CONFIGURE command setting. Example: RETENTION POLICY TO RECOVERY WINDOW OF 10 DAYS

Note:

1.

select * from V$RMAN_CONFIGURATION;

CONF#

NAME

VALUE

1

RETENTION POLICY

TO RECOVERY WINDOW OF 92 DAYS

2

DEFAULT DEVICE TYPE TO

'SBT_TAPE'

Oracle data dictionary views

Oracle dynamic performance views

V$RMAN_COMPRESSION_ALGORITHM

V$RMAN_COMPRESSION_ALGORITHM provides descriptions of supported compression algorithms. It is used by the RMAN client.

Column

Datatype

Description

ALGORITHM_ID

NUMBER

Algorithm ID

ALGORITHM_NAME

VARCHAR2(64)

Name of the algorithm (for example, BZIP2 or ZLIB)

ALGORITHM_DESCRIPTION

VARCHAR2(64)

Description of the algorithm

ALGORITHM_COMPATIBILITY

VARCHAR2(18)

The required database compatibility level in order for the algorithm to work (for example, 11.0.0 for ZLIB)

DATABASE_COMPATIBILITY

VARCHAR2(18)

Current database compatibility

IS_VALID

VARCHAR2(3)

Whether or not the algorithm is valid with regard to the compatibility setting. Value is YES if ALGORITHM_COMPATIBILITY<=DATABASE_COMPATIBILITY.

IS_DEFAULT

VARCHAR2(3)

Whether or not this is the default algorithm

Oracle data dictionary views

Oracle dynamic performance views

V$RMAN_BACKUP_TYPE

V$RMAN_BACKUP_TYPE displays information about RMAN backup types.

Column

Datatype

Description

WEIGHT

NUMBER

Used to set precedence order of different backup types in reports.

INPUT_TYPE

VARCHAR2(13)

Used to represent possible filters used in creating various reporting screens.

Note:

1.

select * from V$RMAN_BACKUP_TYPE;

WEIGHT

INPUT_TYPE

1

BACKUPSET

2

SPFILE

3

CONTROLFILE

4

ARCHIVELOG

5

DATAFILE INCR

6

DATAFILE FULL

7

DB INCR

8

RECVR AREA

9

DB FULL

Oracle data dictionary views

Oracle dynamic performance views

V$RMAN_BACKUP_SUBJOB_DETAILS

V$RMAN_BACKUP_SUBJOB_DETAILS merges similar operations within an RMAN session into a single row. For example, if there are four BACKUP DATAFILE commands, three RECOVERY COPY OF DATAFILE commands, and one BACKUP RECOVERY AREA command, this view will contain three rows - one each for BACKUP, ROLLFORWARD, and COPY_DISK_TO_TAPE operation.

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

OPERATION

VARCHAR2(33)

Can be BACKUP, ROLLFORWARD, VALIDATE, or COPY_DISK_TO_TAPE. A row for each suboperation type for the session will be in the output view.

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

OBJECT_TYPE_WEIGHT

NUMBER

Used internally by Enterprise Manager

OPTIMIZED_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_DONE

VARCHAR2(3)

YES or NO, depending upon whether or not a control file autobackup was done as part of this 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.

AUTOBACKUP_COUNT

NUMBER

Number of autobackups performed by this job

COMPRESSION_RATIO

NUMBER

Compression ratio

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.

Note:

1.

select session_key, operation, status, compression_ratio, input_bytes_display, output_bytes_display

from V$RMAN_BACKUP_SUBJOB_DETAILS;

SESSION_KEY

OPERATION

STATUS

COMPRESSION_RATIO

INPUT_BYTES_DISPLAY

OUTPUT_BYTES_DISPLAY

18205

BACKUP

COMPLETED

3.41799049598936

1.17T

350.35G

17946

BACKUP

COMPLETED

3.46084052187209

1023.16G

295.64G

18317

BACKUP

COMPLETED

3.55417940479047

1.30T

373.20G

18060

BACKUP

FAILED

3.20107064644334

115.62G

36.12G

18351

BACKUP

COMPLETED

3.5238063780519

958.81G

272.10G

17981

BACKUP

COMPLETED

3.46973467834098

1.08T

319.63G

18054

BACKUP

FAILED

1

0.00K

0.00K

18376

BACKUP

COMPLETED

3.51405127279056

819.52G

233.21G

18095

BACKUP

COMPLETED

3.4687228625705

1.02T

301.19G

17521

BACKUP

COMPLETED

3.48035890958661

1.03T

303.29G

Oracle data dictionary views

Oracle dynamic performance views

V$RMAN_BACKUP_JOB_DETAILS

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 h:m:s
Note:
  1. 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
  1. Accessing V$RMAN_BACKUP_JOB_DETAILS will 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