8
Reference

This chapter describes new or changed features in the Oracle8i Reference for release 8.1.7. The following parameter and dynamic performance views are new or have been revised for this release:

ORACLE_TRACE_ENABLE

This parameter was static previous to release 8.1.7. It is now dynamic.

Parameter type
Boolean

Syntax
ORACLE_TRACE_ENABLE = {TRUE | FALSE}

Default value
FALSE

Parameter class
Dynamic
Scope= ALTER SESSION, ALTER SYSTEM

To enable Oracle Trace collections for the server, set ORACLE_TRACE_ENABLE to TRUE. This setting alone does not start an Oracle Trace collection, but it allows Oracle Trace to be used for the server.
With ORACLE_TRACE_ENABLE set to TRUE, you can perform Oracle Trace collection of server event data in any of the following ways:

By using Oracle Trace Manager, which is supplied with the Oracle Diagnostic Pack

By using the TRACE statement

By specifying a collection name in the ORACLE_TRACE_COLLECTION_NAME parameter

See Also:

Oracle8i Designing and Tuning for Performance for more information on the Oracle Trace facility and on setting this parameter

V$ARCHIVED_LOG

This view displays archived log information from the control file, including archive log names. An archive log record is inserted after the online redo log is successfully archived or cleared (name column is NULL if the log was cleared). If the log is archived twice, there will be two archived log records with the same THREAD#, SEQUENCE#, and FIRST_CHANGE#, but with a different name. An archive log record is also inserted when an archive log is restored from a backup set or a copy and whenever a copy of a log is made with the RMAN copy command.

Column Datatype Description

RECID

NUMBER

Archived log record ID

STAMP

NUMBER

Archived log record stamp

NAME

VARCHAR2(513)

Archived log file name. If set to NULL, the log file was cleared before it was archived.

DEST_ID

NUMBER

Identifies the original destination from which the archivelog was generated. A value of 0 indicates the destination identifier is not available.

THREAD#

NUMBER

Redo thread number

SEQUENCE#

NUMBER

Redo log sequence number

RESETLOGS_CHANGE#

NUMBER

Resetlogs change# of the database when this log was written

RESETLOGS_TIME

DATE

Resetlogs time of the database when this log was written

FIRST_CHANGE#

NUMBER

First change# in the archived log

FIRST_TIME

DATE

Timestamp of the first change

NEXT_CHANGE#

NUMBER

First change in the next log

NEXT_TIME

DATE

Timestamp of the next change

BLOCKS

NUMBER

Size of the archived log in blocks

BLOCK_SIZE

NUMBER

Redo log block size

CREATOR

VARCHAR2(4)

Identifies the creator of the archivelog (ARCH, FRDF, or RMAN)

REGISTRAR

VARCHAR2(4)

Identifies the registrar of the entry (RFS, ARCH, FRGD, RMAN, or SRMN, which is RMAN at standby)

STANDBY_DEST

VARCHAR2(3)

(YES/NO) Indicates if the entry is an archivelog destination

ARCHIVED

VARCHAR2(3)

Indicates that the online redo log was archived (YES) or that RMAN only inspected the log and created a record for future application of redo logs during recovery.
See Also: Oracle8i Recovery Manager User's Guide and Reference.

DELETED

VARCHAR2(3)

Specifies (YES | NO) whether an RMAN delete command has physically deleted the archived log file from disk, as well as logically removing it from the control file of the target database and from the recovery catalog.

COMPLETION_TIME

DATE

Time when the archiving completed

Column	Datatype	Description
`RECID`	`NUMBER`	Archived log record ID
`STAMP`	`NUMBER`	Archived log record stamp
`NAME`	`VARCHAR2(513)`	Archived log file name. If set to `NULL`, the log file was cleared before it was archived.
DEST_ID	NUMBER	Identifies the original destination from which the archivelog was generated. A value of 0 indicates the destination identifier is not available.
`THREAD#`	`NUMBER`	Redo thread number
`SEQUENCE#`	`NUMBER`	Redo log sequence number
`RESETLOGS_CHANGE#`	`NUMBER`	Resetlogs change# of the database when this log was written
`RESETLOGS_TIME`	`DATE`	Resetlogs time of the database when this log was written
`FIRST_CHANGE#`	`NUMBER`	First change# in the archived log
`FIRST_TIME`	`DATE`	Timestamp of the first change
`NEXT_CHANGE#`	`NUMBER`	First change in the next log
`NEXT_TIME`	`DATE`	Timestamp of the next change
`BLOCKS`	`NUMBER`	Size of the archived log in blocks
`BLOCK_SIZE`	`NUMBER`	Redo log block size
CREATOR	VARCHAR2(4)	Identifies the creator of the archivelog (`ARCH`, `FRDF`, or `RMAN`)
REGISTRAR	VARCHAR2(4)	Identifies the registrar of the entry (`RFS`, `ARCH`, `FRGD`, `RMAN`, or `SRMN`, which is `RMAN` at standby)
STANDBY_DEST	VARCHAR2(3)	(`YES`/`NO`) Indicates if the entry is an archivelog destination
`ARCHIVED`	`VARCHAR2(3)`	Indicates that the online redo log was archived (`YES`) or that RMAN only inspected the log and created a record for future application of redo logs during recovery. See Also: Oracle8i Recovery Manager User's Guide and Reference.
`DELETED`	`VARCHAR2(3)`	Specifies (`YES` \| `NO`) whether an RMAN delete command has physically deleted the archived log file from disk, as well as logically removing it from the control file of the target database and from the recovery catalog.
`COMPLETION_TIME`	`DATE`	Time when the archiving completed

V$BACKUP_DATAFILE

For release 8.1.7, V$BACKUP_DATAFILE has a new column: CONTROLFILE_TYPE.

This view displays backup datafile and backup control file information from the control file.

Column Datatype Description

RECID

NUMBER

Backup datafile record ID

STAMP

NUMBER

Backup datafile record stamp

SET_STAMP

NUMBER

Backup set stamp

SET_COUNT

NUMBER

Backup set count

FILE#

NUMBER

Datafile number; set to 0 for control file

CREATION_CHANGE#

NUMBER

Creation change of the datafile

CREATION_TIME

DATE

Creation timestamp of the datafile

RESETLOGS_CHANGE#

NUMBER

Resetlogs change# of the datafile when it was backed up

RESETLOGS_TIME

DATE

Resetlogs timestamp of the datafile when it was backed up

INCREMENTAL_LEVEL

NUMBER

(0-4) incremental backup level

INCREMENTAL_CHANGE#

NUMBER

All blocks changed after incremental change# is included in this backup; set to 0 for a full backup

CHECKPOINT_CHANGE#

NUMBER

All changes up to checkpoint change# are included in this backup

CHECKPOINT_TIME

DATE

Timestamp of the checkpoint

ABSOLUTE_FUZZY_CHANGE#

NUMBER

Highest change# in this backup

MARKED_CORRUPT

NUMBER

Number of blocks marked corrupt

MEDIA_CORRUPT

NUMBER

Number of blocks media corrupt

LOGICALLY_CORRUPT

NUMBER

Number of blocks logically corrupt

DATAFILE_BLOCKS

NUMBER

Size of the datafile in blocks at backup time. This value is also the number of blocks taken by the datafile restarted from this backup.

BLOCKS

NUMBER

Size of the backup datafile in blocks. Unused blocks are not copied to the backup.

BLOCK_SIZE

NUMBER

Block size

OLDEST_OFFLINE_RANGE

NUMBER

The RECID of the oldest offline range record in this backup control file. 0 for datafile backups.

COMPLETION_TIME

DATE

The time completed

CONTROLFILE_TYPE

VARCHAR2(1)

B indicates normal copies
S indicates standby copies

Column	Datatype	Description
`RECID`	`NUMBER`	Backup datafile record ID
`STAMP`	`NUMBER`	Backup datafile record stamp
`SET_STAMP`	`NUMBER`	Backup set stamp
`SET_COUNT`	`NUMBER`	Backup set count
`FILE#`	`NUMBER`	Datafile number; set to 0 for control file
`CREATION_CHANGE#`	`NUMBER`	Creation change of the datafile
`CREATION_TIME`	`DATE`	Creation timestamp of the datafile
`RESETLOGS_CHANGE#`	`NUMBER`	Resetlogs change# of the datafile when it was backed up
`RESETLOGS_TIME`	`DATE`	Resetlogs timestamp of the datafile when it was backed up
`INCREMENTAL_LEVEL`	`NUMBER`	(0-4) incremental backup level
`INCREMENTAL_CHANGE#`	`NUMBER`	All blocks changed after incremental change# is included in this backup; set to 0 for a full backup
`CHECKPOINT_CHANGE#`	`NUMBER`	All changes up to checkpoint change# are included in this backup
`CHECKPOINT_TIME`	`DATE`	Timestamp of the checkpoint
`ABSOLUTE_FUZZY_CHANGE#`	`NUMBER`	Highest change# in this backup
`MARKED_CORRUPT`	`NUMBER`	Number of blocks marked corrupt
`MEDIA_CORRUPT`	`NUMBER`	Number of blocks media corrupt
`LOGICALLY_CORRUPT`	`NUMBER`	Number of blocks logically corrupt
`DATAFILE_BLOCKS`	`NUMBER`	Size of the datafile in blocks at backup time. This value is also the number of blocks taken by the datafile restarted from this backup.
`BLOCKS`	`NUMBER`	Size of the backup datafile in blocks. Unused blocks are not copied to the backup.
`BLOCK_SIZE`	`NUMBER`	Block size
`OLDEST_OFFLINE_RANGE`	`NUMBER`	The `RECID` of the oldest offline range record in this backup control file. 0 for datafile backups.
`COMPLETION_TIME`	`DATE`	The time completed
CONTROLFILE_TYPE	VARCHAR2(1)	B indicates normal copies S indicates standby copies

V$BACKUP_SET

This view displays backup set information from the control file. A backup set record is inserted after the backup set is successfully completed.

Column Datatype Description

RECID

NUMBER

Backup set record ID

STAMP

NUMBER

Backup set record timestamp

SET_STAMP

NUMBER

Backup set stamp. The backup set stamp and count uniquely identify the backup set.
Primary key for the V$BACKUP_SET table, and the foreign key for the following tables: V$BACKUP_PIECE, V$BACKUP_DATAFILE, V$BACKUP_REDOLOG, V$BACKUP_CORRUPTION

SET_COUNT

NUMBER

Backup set count. The backup set count is incremented by one every time a new backup set is started (if the backup set is never completed the number is "lost"). If the control file is recreated then the count is reset to 1. Therefore the count must be used with the stamp to uniquely identify a backup set.
Primary key for the V$BACKUP_SET table, and the foreign key for the following tables: V$BACKUP_PIECE, V$BACKUP_DATAFILE, V$BACKUP_REDOLOG, V$BACKUP_CORRUPTION

BACKUP_TYPE

VARCHAR2(1)

Type of files that are in this backup. If the backup contains archived redo logs, the value is `L'. If this is a datafile full backup, the value is `D'. If this is an incremental backup, the value is `I'.

CONTROLFILE_INCLUDED

VARCHAR2(3)

Set to YES if there is a control file included in this backup set, otherwise set to NO

INCREMENTAL_LEVEL

NUMBER

Location where this backup set fits into the database's backup strategy. Set to zero for full datafile backups, non-zero for incremental datafile backups, and NULL for archivelog backups.

PIECES

NUMBER

Number of distinct backup pieces in the backup set

START_TIME

DATE

The starting time

COMPLETION_TIME

DATE

The time that this backup set completed

ELAPSED_SECONDS

NUMBER

The number of elapsed seconds

BLOCK_SIZE

NUMBER

Block size of the backup set

INPUT_FILE_SCAN_ONLY

VARCHAR2(3)

YES indicates no actual backup is performed, but the datafiles are read. NO indicates a normal backup is performed

Column	Datatype	Description
`RECID`	`NUMBER`	Backup set record ID
`STAMP`	`NUMBER`	Backup set record timestamp
`SET_STAMP`	`NUMBER`	Backup set stamp. The backup set stamp and count uniquely identify the backup set. Primary key for the `V$BACKUP_SET` table, and the foreign key for the following tables: `V$BACKUP_PIECE, V$BACKUP_DATAFILE, V$BACKUP_REDOLOG, V$BACKUP_CORRUPTION`
`SET_COUNT`	`NUMBER`	Backup set count. The backup set count is incremented by one every time a new backup set is started (if the backup set is never completed the number is "lost"). If the control file is recreated then the count is reset to 1. Therefore the count must be used with the stamp to uniquely identify a backup set. Primary key for the `V$BACKUP_SET` table, and the foreign key for the following tables: `V$BACKUP_PIECE, V$BACKUP_DATAFILE, V$BACKUP_REDOLOG, V$BACKUP_CORRUPTION`
`BACKUP_TYPE`	`VARCHAR2(1)`	Type of files that are in this backup. If the backup contains archived redo logs, the value is `L'. If this is a datafile full backup, the value is `D'. If this is an incremental backup, the value is `I'.
`CONTROLFILE_INCLUDED`	`VARCHAR2(3)`	Set to `YES` if there is a control file included in this backup set, otherwise set to `NO`
`INCREMENTAL_LEVEL`	`NUMBER`	Location where this backup set fits into the database's backup strategy. Set to zero for full datafile backups, non-zero for incremental datafile backups, and NULL for archivelog backups.
`PIECES`	`NUMBER`	Number of distinct backup pieces in the backup set
`START_TIME`	`DATE`	The starting time
`COMPLETION_TIME`	`DATE`	The time that this backup set completed
`ELAPSED_SECONDS`	`NUMBER`	The number of elapsed seconds
`BLOCK_SIZE`	`NUMBER`	Block size of the backup set
INPUT_FILE_SCAN_ONLY	VARCHAR2(3)	YES indicates no actual backup is performed, but the datafiles are read. NO indicates a normal backup is performed

V$DATAFILE_COPY

For release 8.1.7, V$DATAFILE_COPY has a new column: CONTROLFILE_TYPE.

This view displays datafile copy information from the control file.

Column Datatype Description

RECID

NUMBER

Datafile copy record ID

STAMP

NUMBER

Datafile copy record stamp

NAME

VARCHAR2(513)

Filename of the datafile copy. The maximum length of the name is OS dependent.

TAG

VARCHAR2(32)

Datafile copy tag

FILE#

NUMBER

Absolute datafile number

RFILE#

NUMBER

Tablespace relative datafile number

CREATION_CHANGE#

NUMBER

Datafile creation change#

CREATION_TIME

DATE

Datafile creation timestamp

RESETLOGS_CHANGE#

NUMBER

Resetlogs change# of the datafile when the copy was made

RESETLOGS_TIME

DATE

Resetlogs timestamp of the datafile when the copy was made

INCREMENTAL_LEVEL

NUMBER

The incremental level

CHECKPOINT_CHANGE#

NUMBER

Checkpoint change# of the datafile when the copy was made

CHECKPOINT_TIME

DATE

Checkpoint timestamp of the datafile when the copy was made

ABSOLUTE_FUZZY_CHANGE#

NUMBER

Highest change seen when the datafile was copied

RECOVERY_FUZZY_CHANGE#

NUMBER

Highest change written to the file by media recovery

RECOVERY_FUZZY_TIME

DATE

Timestamp of the highest change written to the file by media recovery

ONLINE_FUZZY

VARCHAR2(3)

(YES | NO) If set to YES, this is a copy taken using an operating system utility after a crash or offline immediate (or an invalid copy taken while datafile was online and the database open). Recovery will need to apply all redo up to the next crash recovery marker to make the file consistent.

BACKUP_FUZZY

VARCHAR2(3)

(YES | NO) If set to YES, this is a copy taken using the BEGIN BACKUP/END BACKUP technique. Recovery will need to apply all redo up to the end backup marker to make this copy consistent.

MARKED_CORRUPT

NUMBER

Number of blocks marked corrupt by this copy operation. That is, blocks that were not marked corrupted in the source datafile, but were detected and marked as corrupted during the copy operation.

MEDIA_CORRUPT

NUMBER

Total number of media corrupt blocks. For example, blocks with checksum errors are marked media corrupt.

LOGICALLY_CORRUPT

NUMBER

Total number of logically corrupt blocks. For example, applying redo for unrecoverable operations will mark affected blocks logically corrupt.

BLOCKS

NUMBER

Size of the datafile copy in blocks (also the size of the datafile when the copy was made)

BLOCK_SIZE

NUMBER

Block size of the datafile

OLDEST_OFFLINE_RANGE

NUMBER

The RECID of the oldest offline range record in this control file copy; 0 for datafile copies

DELETED

VARCHAR2(3)

(YES | NO) If set to YES the datafile copy has been deleted or overwritten

COMPLETION_TIME

DATE

Time when the copy was completed

CONTROLFILE_TYPE

VARCHAR2(1)

B indicates normal copies
S indicates standby copies

Column	Datatype	Description
`RECID`	`NUMBER`	Datafile copy record ID
`STAMP`	`NUMBER`	Datafile copy record stamp
`NAME`	`VARCHAR2(513)`	Filename of the datafile copy. The maximum length of the name is OS dependent.
`TAG`	`VARCHAR2(32)`	Datafile copy tag
`FILE#`	`NUMBER`	Absolute datafile number
`RFILE#`	`NUMBER`	Tablespace relative datafile number
`CREATION_CHANGE#`	`NUMBER`	Datafile creation change#
`CREATION_TIME`	`DATE`	Datafile creation timestamp
`RESETLOGS_CHANGE#`	`NUMBER`	Resetlogs change# of the datafile when the copy was made
`RESETLOGS_TIME`	`DATE`	Resetlogs timestamp of the datafile when the copy was made
`INCREMENTAL_LEVEL`	`NUMBER`	The incremental level
`CHECKPOINT_CHANGE#`	`NUMBER`	Checkpoint change# of the datafile when the copy was made
`CHECKPOINT_TIME`	`DATE`	Checkpoint timestamp of the datafile when the copy was made
`ABSOLUTE_FUZZY_CHANGE#`	`NUMBER`	Highest change seen when the datafile was copied
`RECOVERY_FUZZY_CHANGE#`	`NUMBER`	Highest change written to the file by media recovery
`RECOVERY_FUZZY_TIME`	`DATE`	Timestamp of the highest change written to the file by media recovery
`ONLINE_FUZZY`	`VARCHAR2(3)`	(`YES` \| `NO`) If set to `YES`, this is a copy taken using an operating system utility after a crash or offline immediate (or an invalid copy taken while datafile was online and the database open). Recovery will need to apply all redo up to the next crash recovery marker to make the file consistent.
`BACKUP_FUZZY`	`VARCHAR2(3)`	(`YES` \| `NO`) If set to `YES`, this is a copy taken using the `BEGIN BACKUP/END BACKUP` technique. Recovery will need to apply all redo up to the end backup marker to make this copy consistent.
`MARKED_CORRUPT`	`NUMBER`	Number of blocks marked corrupt by this copy operation. That is, blocks that were not marked corrupted in the source datafile, but were detected and marked as corrupted during the copy operation.
`MEDIA_CORRUPT`	`NUMBER`	Total number of media corrupt blocks. For example, blocks with checksum errors are marked media corrupt.
`LOGICALLY_CORRUPT`	`NUMBER`	Total number of logically corrupt blocks. For example, applying redo for unrecoverable operations will mark affected blocks logically corrupt.
`BLOCKS`	`NUMBER`	Size of the datafile copy in blocks (also the size of the datafile when the copy was made)
`BLOCK_SIZE`	`NUMBER`	Block size of the datafile
`OLDEST_OFFLINE_RANGE`	`NUMBER`	The `RECID` of the oldest offline range record in this control file copy; 0 for datafile copies
`DELETED`	`VARCHAR2(3)`	(`YES` \| `NO`) If set to `YES` the datafile copy has been deleted or overwritten
`COMPLETION_TIME`	`DATE`	Time when the copy was completed
CONTROLFILE_TYPE	VARCHAR2(1)	B indicates normal copies S indicates standby copies

V$PROXY_DATAFILE

For release 8.1.7, V$PROXY_DATAFILE has a new colum: CONTROLFILE_TYPE.

This view contains descriptions of datafile and control file backups that are taken with Proxy Copy. Each row represents a backup of one database file.

Column Datatype Description

RECID

NUMBER

Proxy copy record ID

STAMP

NUMBER

Proxy copy record stamp

DEVICE_TYPE

VARCHAR2(17)

Type of the device on which the copy resides

HANDLE

VARCHAR2(513)

Proxy copy handle identifies the copy for restore

COMMENTS

VARCHAR2(81)

Comment returned by the operating system or storage subsystem. This value is informational only; not needed for restore.

MEDIA

VARCHAR2(65)

Name of the media on which the copy resides. This value is informational only; not needed for restore.

MEDIA_POOL

NUMBER

The media pool in which the copy resides. This is the same value that was entered in the pool operand of the Recovery Manager backup command

TAG

VARCHAR2(32)

Proxy copy tag

STATUS

VARCHAR2(1)

Indicates the status of the copy:

A - The object is available

D - The object is deleted

X - The object has been "cross-checked" and found not to exist. A subsequent "delete expired" command will change the status to D. If, for some reason, the object really does still exist, then a subsequent "cross-check" command will change the status back to A.

FILE#

NUMBER

Absolute datafile number, or 0 if this is a control file backup

CREATION_CHANGE#

NUMBER

Datafile creation change number

CREATION_TIME

DATE

Datafile creation Timestamp

RESETLOGS_CHANGE#

NUMBER

Resetlogs change number of the datafile when the copy was made

RESETLOGS_TIME

DATE

Resetlogs timestamp of the datafile when the copy was made

CHECKPOINT_CHANGE#

NUMBER

Checkpoint change number of the datafile when the copy was made

CHECKPOINT_TIME

DATE

Checkpoint timestamp of the datafile when the copy was made

ABSOLUTE_FUZZY_CHANGE#

NUMBER

The highest change in any block of the file, if known

RECOVERY_FUZZY_CHANGE#

NUMBER

Highest change written to the file by media recovery

RECOVERY_FUZZY_TIME

DATE

Timestamp of the highest change written to the file by media recovery

INCREMENTAL_LEVEL

NUMBER

0 if this backup is part of an incremental backup strategy, otherwise NULL

ONLINE_FUZZY

VARCHAR2(3)

(YES|NO) If set to YES, this copy was made after a crash or offline immediate (or is a copy of a copy which was taken improperly while the database was open). Recovery will need to apply all redo up to the next crash recovery marker to make the file consistent.

BACKUP_FUZZY

VARCHAR2(3)

(YES|NO) If set to YES, this is a copy taken using the BEGIN BACKUP|END BACKUP technique. Note that the BEGIN BACKUP|END BACKUP technique is used internally when proxy copies of open files are created. Recovery will need to apply all redo up to the end backup marker to make this copy consistent.

BLOCKS

NUMBER

Size of the copy in blocks (also the size of the datafile when the copy was made)

BLOCK_SIZE

NUMBER

Block size of the datafile

OLDEST_OFFLINE_RANGE

NUMBER

If file# is 0 (ie, this is a control file backup), the RECID of the oldest offline range record in this control file copy. 0 for datafile copies.

START_TIME

DATE

The starting time

COMPLETION_TIME

DATE

The completion time

ELAPSED_SECONDS

NUMBER

The number of elapsed seconds

CONTROLFILE_TYPE

VARCHAR2(1)

B indicates normal copies
S indicates standby copies

Column	Datatype	Description
`RECID`	`NUMBER`	Proxy copy record ID
`STAMP`	`NUMBER`	Proxy copy record stamp
`DEVICE_TYPE`	`VARCHAR2(17)`	Type of the device on which the copy resides
`HANDLE`	`VARCHAR2(513)`	Proxy copy handle identifies the copy for restore
`COMMENTS`	`VARCHAR2(81)`	Comment returned by the operating system or storage subsystem. This value is informational only; not needed for restore.
`MEDIA`	`VARCHAR2(65)`	Name of the media on which the copy resides. This value is informational only; not needed for restore.
`MEDIA_POOL`	`NUMBER`	The media pool in which the copy resides. This is the same value that was entered in the pool operand of the Recovery Manager backup command
`TAG`	`VARCHAR2(32)`	Proxy copy tag
`STATUS`	`VARCHAR2(1)`	Indicates the status of the copy: `A` - The object is available `D` - The object is deleted `X` - The object has been "cross-checked" and found not to exist. A subsequent "delete expired" command will change the status to `D`. If, for some reason, the object really does still exist, then a subsequent "cross-check" command will change the status back to `A`.
`FILE#`	`NUMBER`	Absolute datafile number, or 0 if this is a control file backup
`CREATION_CHANGE#`	`NUMBER`	Datafile creation change number
`CREATION_TIME`	`DATE`	Datafile creation Timestamp
`RESETLOGS_CHANGE#`	`NUMBER`	Resetlogs change number of the datafile when the copy was made
`RESETLOGS_TIME`	`DATE`	Resetlogs timestamp of the datafile when the copy was made
`CHECKPOINT_CHANGE#`	`NUMBER`	Checkpoint change number of the datafile when the copy was made
`CHECKPOINT_TIME`	`DATE`	Checkpoint timestamp of the datafile when the copy was made
`ABSOLUTE_FUZZY_CHANGE#`	`NUMBER`	The highest change in any block of the file, if known
`RECOVERY_FUZZY_CHANGE#`	`NUMBER`	Highest change written to the file by media recovery
`RECOVERY_FUZZY_TIME`	`DATE`	Timestamp of the highest change written to the file by media recovery
`INCREMENTAL_LEVEL`	`NUMBER`	0 if this backup is part of an incremental backup strategy, otherwise `NULL`
`ONLINE_FUZZY`	`VARCHAR2(3)`	(`YES`\|`NO`) If set to `YES`, this copy was made after a crash or offline immediate (or is a copy of a copy which was taken improperly while the database was open). Recovery will need to apply all redo up to the next crash recovery marker to make the file consistent.
`BACKUP_FUZZY`	`VARCHAR2(3)`	(`YES`\|`NO`) If set to `YES`, this is a copy taken using the `BEGIN BACKUP\|END BACKUP` technique. Note that the `BEGIN BACKUP\|END BACKUP` technique is used internally when proxy copies of open files are created. Recovery will need to apply all redo up to the end backup marker to make this copy consistent.
`BLOCKS`	`NUMBER`	Size of the copy in blocks (also the size of the datafile when the copy was made)
`BLOCK_SIZE`	`NUMBER`	Block size of the datafile
`OLDEST_OFFLINE_RANGE`	`NUMBER`	If file# is 0 (ie, this is a control file backup), the `RECID` of the oldest offline range record in this control file copy. 0 for datafile copies.
`START_TIME`	`DATE`	The starting time
`COMPLETION_TIME`	`DATE`	The completion time
`ELAPSED_SECONDS`	`NUMBER`	The number of elapsed seconds
CONTROLFILE_TYPE	VARCHAR2(1)	`B` indicates normal copies `S` indicates standby copies

V$SQL_SHARED_CURSOR

This new dynamic performance view describes explains why a particular child cursor is not shared with existing child cursors. Each column identifies a specific reason why the cursor cannot be shared.

Column Datatype Description

ADDRESS

RAW(4)

Address of the child cursor

KGLHDPAR

VARCHAR2(1)

(Y or N) Address of the pattern cursor

UNBOUND_CURSOR

VARCHAR2(1)

(Y or N) The existing child cursor was not fully built (in other words, it was not optimized)

SQL_TYPE_MISMATCH

VARCHAR2(1)

(Y or N) The SQL type does not match the existing child cursor

OPTIMIZER_MISMATCH

VARCHAR2(1)

(Y or N) The optimizer environment does not match the existing child cursor

OUTLINE_MISMATCH

VARCHAR2(1)

(Y or N) The outlines do not match the existing child cursor

STATS_ROW_MISMATCH

VARCHAR2(1)

(Y or N) The existing statistics do not match the existing child cursor

LITERAL_MISMATCH

VARCHAR2(1)

(Y or N) Non-data literal values do not match the existing child cursor

SEC_DEPTH_MISMATCH

VARCHAR2(1)

(Y or N) Security level does not match the existing child cursor

EXPLAIN_PLAN_CURSOR

VARCHAR2(1)

(Y or N) The child cursor is an explain plan cursor and should not be shared

BUFFERED_DML_MISMATCH

VARCHAR2(1)

(Y or N) Buffered DML does not match the existing child cursor

PDML_ENV_MISMATCH

VARCHAR2(1)

(Y or N) PDML environment does not match the existing child cursor

INST_DRTLD_MISMATCH

VARCHAR2(1)

(Y or N) Insert direct load does not match the existing child cursor

SLAVE_QC_MISMATCH

VARCHAR2(1)

(Y or N) The existing child cursor is a slave cursor and the new one was issued by the coordinator (or, the existing child cursor was issued by the coordinator and the new one is a slave cursor)

TYPECHECK_MISMATCH

VARCHAR2(1)

(Y or N) The existing child cursor is not fully optimized

AUTH_CHECK_MISMATCH

VARCHAR2(1)

(Y or N) Authorization/translation check failed for the existing child cursor

BIND_MISMATCH

VARCHAR2(1)

(Y or N) The bind metadata does not match the existing child cursor

DESCRIBE_MISMATCH

VARCHAR2(1)

(Y or N) The typecheck heap is not present during the describe for the child cursor

LANGUAGE_MISMATCH

VARCHAR2(1)

(Y or N) The language handle does not match the existing child cursor

TRANSLATION_MISMATCH

VARCHAR2(1)

(Y or N) The base objects of the existing child cursor do not match

ROW_LEVEL_SEC_MISMATCH

VARCHAR2(1)

(Y or N) The row level security policies do not match

INSUFF_PRIVS

VARCHAR2(1)

(Y or N) Insufficient privileges on objects referenced by the existing child cursor

INSUFF_PRIVS_REM

VARCHAR2(1)

(Y or N) Insufficient privileges on remote objects referenced by the existing child cursor

REMOTE_TRANS_MISMATCH

VARCHAR2(1)

(Y or N) The remote base objects of the existing child cursor do not match

Parameter type	Boolean
Syntax	`ORACLE_TRACE_ENABLE = {TRUE \| FALSE}`
Default value	`FALSE`
Parameter class	Dynamic Scope= `ALTER SESSION`, `ALTER SYSTEM`
To enable Oracle Trace collections for the server, set `ORACLE_TRACE_ENABLE` to `TRUE`. This setting alone does not start an Oracle Trace collection, but it allows Oracle Trace to be used for the server. With `ORACLE_TRACE_ENABLE` set to `TRUE`, you can perform Oracle Trace collection of server event data in any of the following ways: By using Oracle Trace Manager, which is supplied with the Oracle Diagnostic Pack By using the `TRACE` statement By specifying a collection name in the `ORACLE_TRACE_COLLECTION_NAME` parameter
See Also: Oracle8i Designing and Tuning for Performance for more information on the Oracle Trace facility and on setting this parameter

Column	Datatype	Description
`ADDRESS`	`RAW(4)`	Address of the child cursor
KGLHDPAR	VARCHAR2(1)	(`Y` or `N`) Address of the pattern cursor
`UNBOUND_CURSOR`	VARCHAR2(1)	(`Y` or `N`) The existing child cursor was not fully built (in other words, it was not optimized)
`SQL_TYPE_MISMATCH`	VARCHAR2(1)	(`Y` or `N`) The SQL type does not match the existing child cursor
`OPTIMIZER_MISMATCH`	VARCHAR2(1)	(`Y` or `N`) The optimizer environment does not match the existing child cursor
`OUTLINE_MISMATCH`	VARCHAR2(1)	(`Y` or `N`) The outlines do not match the existing child cursor
`STATS_ROW_MISMATCH`	VARCHAR2(1)	(`Y` or `N`) The existing statistics do not match the existing child cursor
`LITERAL_MISMATCH`	VARCHAR2(1)	(`Y` or `N`) Non-data literal values do not match the existing child cursor
`SEC_DEPTH_MISMATCH`	VARCHAR2(1)	(`Y` or `N`) Security level does not match the existing child cursor
`EXPLAIN_PLAN_CURSOR`	VARCHAR2(1)	(`Y` or `N`) The child cursor is an explain plan cursor and should not be shared
`BUFFERED_DML_MISMATCH`	VARCHAR2(1)	(`Y` or `N`) Buffered DML does not match the existing child cursor
`PDML_ENV_MISMATCH`	VARCHAR2(1)	(`Y` or `N`) PDML environment does not match the existing child cursor
`INST_DRTLD_MISMATCH`	VARCHAR2(1)	(`Y` or `N`) Insert direct load does not match the existing child cursor
`SLAVE_QC_MISMATCH`	VARCHAR2(1)	(`Y` or `N`) The existing child cursor is a slave cursor and the new one was issued by the coordinator (or, the existing child cursor was issued by the coordinator and the new one is a slave cursor)
`TYPECHECK_MISMATCH`	VARCHAR2(1)	(`Y` or `N`) The existing child cursor is not fully optimized
AUTH_CHECK_MISMATCH	VARCHAR2(1)	(`Y` or `N`) Authorization/translation check failed for the existing child cursor
BIND_MISMATCH	VARCHAR2(1)	(`Y` or `N`) The bind metadata does not match the existing child cursor
DESCRIBE_MISMATCH	VARCHAR2(1)	(`Y` or `N`) The typecheck heap is not present during the describe for the child cursor
LANGUAGE_MISMATCH	VARCHAR2(1)	(`Y` or `N`) The language handle does not match the existing child cursor
TRANSLATION_MISMATCH	VARCHAR2(1)	(`Y` or `N`) The base objects of the existing child cursor do not match
ROW_LEVEL_SEC_MISMATCH	VARCHAR2(1)	(`Y` or `N`) The row level security policies do not match
INSUFF_PRIVS	VARCHAR2(1)	(`Y` or `N`) Insufficient privileges on objects referenced by the existing child cursor
INSUFF_PRIVS_REM	VARCHAR2(1)	(`Y` or `N`) Insufficient privileges on remote objects referenced by the existing child cursor
REMOTE_TRANS_MISMATCH	VARCHAR2(1)	(`Y` or `N`) The remote base objects of the existing child cursor do not match

8 Reference