14
Views

This chapter describes the views that are used in a Data Guard environment. This is a subset of the views that are available for use in a database. This chapter contains the following sections:

About Views

An Oracle database contains a set of underlying views that are maintained by the server and accessible to the database administrator. These fixed views are also called dynamic performance views because they are continuously updated while a database is open and in use, and their contents relate primarily to performance.

Although these views appear to be regular database tables, they are not. These views provide data on internal disk structures and memory structures. You can select from these views, but you can never update or alter them.

Fixed view names are usually prefixed with either V$, or GV$, for example, V$ARCHIVE_DEST or GV$ARCHIVE_DEST. The views that are prefixed with DBA_ display all relevant information in the entire database. Standard dynamic performance views (V$ fixed views) store information on the local instance. In contrast, global dynamic performance views (GV$ fixed views) store information on all open instances. Each V$ fixed view has a corresponding GV$ fixed view. DBA_ views are intended only for administrators. They can be accessed only by users with the SELECT_ANY_TABLE privilege. (This privilege is assigned to the DBA role when the system is initially installed.)

In most cases, the information available in fixed views persists across instance shutdowns. However, certain fixed view information is reset when the instance is shut down; these views are specifically identified in this chapter.

For additional information about views, see Oracle9i Database Reference.

DBA_LOGSTDBY_EVENTS (Logical Standby Databases Only)

The DBA_LOGSTDBY_EVENTS view contains information about the activity of the logical standby database system. It can be used to determine the cause of failures that occur when log apply services apply redo logs. This view contains the following columns:

Column	Datatype	Description
`EVENT_TIME`	`DATE`	Time the event was logged
`CURRENT_SCN`	`NUMBER`	Change vector SCN for the event. If a failure occurred, examine this column to determine which archived log file contains the source of the failure (for example, an unsupported record).
`COMMIT_SCN`	`NUMBER`	SCN value for which the change was committed
`XIDUSN`	`NUMBER`	Transaction ID undo segment number
`XIDSLT`	`NUMBER`	Transaction ID slot number
`XIDSQN`	`NUMBER`	Transaction ID sequence number
`EVENT`	`CLOB`	The statement that was being processed when the failure occurred
`STATUS_CODE`	`NUMBER`	Status (or Oracle error code) belonging to the `STATUS` message
`STATUS`	`VARCHAR2(2000)`	Description of the current activity of the process or the reason why the apply operation stopped

DBA_LOGSTDBY_LOG (Logical Standby Databases Only)

The DBA_LOGSTDBY_LOG view shows the logs registered for a logical standby database. The view contains the following columns:

Column	Datatype	Description
`THREAD#`	`NUMBER`	Thread ID of the archived redo log. The `THREAD` number is `1` for a single instance. For Real Application Clusters, this column will contain different numbers.
`SEQUENCE#`	`NUMBER`	Sequence number of the archived redo log file
`FIRST_CHANGE#`	`NUMBER`	SCN of the current archived redo log
`NEXT_CHANGE#`	`NUMBER`	SCN of the next archived redo log
`FIRST_TIME`	`DATE`	Date of the current archived redo log
`NEXT_TIME`	`DATE`	Date of the next archived redo log
`FILE_NAME`	`VARCHAR2(3)`	Name of the archived redo log
`TIMESTAMP`	`DATE`	Time when the archived redo log was registered
`DICT_BEGIN`	`VARCHAR2(3)`	Value `Y` or `N`, where `Y` indicates that the beginning of the dictionary build is in this particular archived redo log
`DICT_END`	`VARCHAR2(3)`	Value `Y` or `N`, where `Y` indicates that the end of the dictionary build is in this particular archived redo log

Note:

The SCN values in this view correlate to the SCN values in the DBA_LOGSTDBY_PROGRESS (Logical Standby Databases Only) view.

DBA_LOGSTDBY_NOT_UNIQUE (Logical Standby Databases Only)

The DBA_LOGSTDBY_NOT_UNIQUE view identifies tables that have no primary and no non-null unique indexes. Most of the tables displayed in this view are supported because their columns contain enough information to be maintained in a logical standby database. Some tables, however, cannot be supported because their columns do not contain the necessary information. Unsupported tables usually contain a column defined using an unsupported datatype. This view contains the following columns:

Column Datatype Description

Column	Datatype	Description
`OWNER`	`VARCHAR2(30)`	Schema name
`TABLE_NAME`	`VARCHAR2(30)`	Name of the table
`BAD_COLUMN`	`VARCHAR2(1)`	This column contains a value of `Y` or `N`: `Y` indicates the table column is defined using an unbounded datatype, such as `LONG` or `BLOB`. If two rows in the table match except in their `LOB` column, then the table cannot be maintained properly. Log apply services will attempt to maintain these tables, but you must ensure the application does not allow uniqueness only in the unbounded columns. `N` indicates that enough column information is present to maintain the table in the logical standby database, but the log transport services and log apply services would run more efficiently if you added a primary key. You should consider adding a disabled `RELY` constraint to these tables.

OWNER

VARCHAR2(30)

Schema name

TABLE_NAME

VARCHAR2(30)

Name of the table

BAD_COLUMN

VARCHAR2(1)

This column contains a value of Y or N:

Y indicates the table column is defined using an unbounded datatype, such as LONG or BLOB. If two rows in the table match except in their LOB column, then the table cannot be maintained properly. Log apply services will attempt to maintain these tables, but you must ensure the application does not allow uniqueness only in the unbounded columns.
N indicates that enough column information is present to maintain the table in the logical standby database, but the log transport services and log apply services would run more efficiently if you added a primary key. You should consider adding a disabled RELY constraint to these tables.

DBA_LOGSTDBY_PARAMETERS (Logical Standby Databases Only)

The DBA_LOGSTDBY_PARAMETERS view contains the list of parameters used by the log apply services for logical standby databases. This view contains the following columns:

Column Datatype Description

Column	Datatype	Description
`NAME`	`VARCHAR2(30)`	Name of the parameter. Possible values are: `MAX_SGA` - System global area (SGA) allocated for the log apply services cache in megabytes `MAX_SLAVES` - Number of parallel query servers specifically reserved for log apply services `MAX_EVENTS_RECORDED` - Number of events stored in the `DBA_LOGSTDBY_EVENTS` view `TRANSACTION_CONSISTENCY` - Shows the level of transaction consistency maintained: `FULL`, `READ_ONLY`, or `NONE` `RECORD_SKIP_ERRORS` - Indicates records that are skipped `RECORD_SKIP_DDL` - Indicates skipped DDL statements `RECORD_APPLIED_DDL` - Indicates applied DDL statements `FIRST_SCN` - SCN at which log transport services will begin applying redo information `PRIMARY` - Database ID of the database to which logs are being applied `LMNR_SID` - LogMiner Session ID. This internal value indicates which LogMiner session is in use. `UNTIL_SCN` - SCN value at which log apply services will shut down until all transactions have been applied `END_PRIMARY_SCN` - During a switchover, this value indicates the last SCN applied by the new primary database from the old primary database `NEW_PRIMARY_SCN` - During a switchover, this value indicates the starting SCN for the new primary database `COMPLETED_SESSION` - Indicates that the log apply services session has concluded. The value will indicate `SWITCHOVER` or `FAILOVER`, as appropriate.
`VALUE`	`VARCHAR2(2000)`	Value of the parameter

NAME

VARCHAR2(30)

Name of the parameter. Possible values are:

MAX_SGA - System global area (SGA) allocated for the log apply services cache in megabytes
MAX_SLAVES - Number of parallel query servers specifically reserved for log apply services
MAX_EVENTS_RECORDED - Number of events stored in the DBA_LOGSTDBY_EVENTS view
TRANSACTION_CONSISTENCY - Shows the level of transaction consistency maintained: FULL, READ_ONLY, or NONE
RECORD_SKIP_ERRORS - Indicates records that are skipped
RECORD_SKIP_DDL - Indicates skipped DDL statements
RECORD_APPLIED_DDL - Indicates applied DDL statements
FIRST_SCN - SCN at which log transport services will begin applying redo information
PRIMARY - Database ID of the database to which logs are being applied
LMNR_SID - LogMiner Session ID. This internal value indicates which LogMiner session is in use.
UNTIL_SCN - SCN value at which log apply services will shut down until all transactions have been applied
END_PRIMARY_SCN - During a switchover, this value indicates the last SCN applied by the new primary database from the old primary database
NEW_PRIMARY_SCN - During a switchover, this value indicates the starting SCN for the new primary database
COMPLETED_SESSION - Indicates that the log apply services session has concluded. The value will indicate SWITCHOVER or FAILOVER, as appropriate.

VALUE

VARCHAR2(2000)

Value of the parameter

DBA_LOGSTDBY_PROGRESS (Logical Standby Databases Only)

The DBA_LOGSTDBY_PROGRESS view describes the progress of log apply services on the logical standby database. This view contains the following columns:

Column	Datatype	Description
`APPLIED_SCN`	`NUMBER`	Shows the newest SCN at which all changes have been applied. The values in the `APPLIED_SCN` and `NEWEST_SCN` columns will match if all available redo log data has been processed.
`APPLIED_TIME`	`DATE`	Estimate of the time and date of the `APPLIED_SCN`
`READ_SCN`	`NUMBER`	All log data greater than this SCN has been read and saved
`READ_TIME`	`DATE`	Estimate of the time and date of the `READ_SCN`
`NEWEST_SCN`	`NUMBER`	Most recent SCN available on the standby system. If no more logs are being transmitted to the standby database, changes could be applied to this SCN. The values in the `APPLIED_SCN` and `NEWEST_SCN` columns will match if all available redo log data has been processed.
`NEWEST_TIME`	`DATE`	Estimate of the time and date of the `NEWEST_SCN`

Note:

The SCN values in this view correlate to the SCN values in the DBA_LOGSTDBY_LOG (Logical Standby Databases Only) view.

DBA_LOGSTDBY_SKIP (Logical Standby Databases Only)

The DBA_LOGSTDBY_SKIP view lists the tables that will be skipped by log apply services. The DBA_LOGSTDBY_SKIP view contains the following columns:

Column	Datatype	Description
`ERROR`	`BOOLEAN`	Indicates if the statement should be skipped or just return errors for the statement
`STATEMENT_OPT`	`VARCHAR(30)`	Specifies the type of statement that should be skipped. It must be one of the `SYSTEM_AUDIT` statement options.
`SCHEMA`	`VARCHAR(30)`	Name of the schema under which this skip option should be used
`NAME`	`VARCHAR(30)`	Name of the option under which this skip option should be used
`PROC`	`VARCHAR(98)`	Name of a stored procedure that will be executed when processing the skip option

DBA_LOGSTDBY_SKIP_TRANSACTION (Logical Standby Databases Only)

The DBA_LOGSTDBY_SKIP_TRANSACTION view lists the skip settings chosen. This view contains the following columns:

Column	Datatype	Description
`XIDUSN`	`NUMBER`	Transaction ID undo segment number
`XIDSLT`	`NUMBER`	Transaction ID slot number
`XIDSQN`	`NUMBER`	Transaction ID sequence number

DBA_LOGSTDBY_UNSUPPORTED (Logical Standby Databases Only)

The DBA_LOGSTDBY_UNSUPPORTED view identifies the schemas and tables (and columns in those tables) that contain unsupported datatypes. Use this view when you are preparing to create a logical standby database. This view contains the following columns:

Column	Datatype	Description
`OWNER`	`VARCHAR2(30)`	Schema name of the unsupported table
`TABLE_NAME`	`VARCHAR2(30)`	Name of the unsupported table
`COLUMN_NAME`	`VARCHAR2(30)`	Name of the unsupported column
`DATA_TYPE`	`VARCHAR2(106)`	Datatype of the unsupported column

V$ARCHIVE_DEST

The V$ARCHIVE_DEST view describes, for the current instance, all the archived redo log destinations, their current value, mode, and status.

Note:

The information in this view does not persist across an instance shutdown.

The V$ARCHIVE_DEST view contains the following columns:

Column	Description
`DEST_ID`	Identifies the log archive destination parameter
`STATUS`	Identifies the current status of the destination. Possible values are: `VALID` - initialized and available `INACTIVE` - no destination information `DEFERRED` - manually disabled by the user `ERROR` - error during open or copy `DISABLED` - disabled after error `BAD PARAM` - parameter has errors `ALTERNATE` - destination is in an alternate state `FULL` - exceeded quota size for the destination
`BINDING`	Specifies how failure will affect the archival operation. Possible values are: `OPTIONAL` - successful archival operation is not required `MANDATORY` - successful archival operation is required
`NAME_SPACE`	Identifies the scope of parameter setting. Possible values are: `SYSTEM` - system definition `SESSION` - session definition
`TARGET`	Specifies whether the archive destination is local or remote to the primary database. Possible values are: `PRIMARY` - local `STANDBY` - remote
`ARCHIVER`	Identifies the archiver process relative to the database where the query is issued. Possible values are: `ARC``n` `FOREGROUND` `LGWR` `RFS`
`SCHEDULE`	Indicates whether the archiving of this destination is `INACTIVE`, `PENDING`, `ACTIVE`, or `LATENT`
`DESTINATION`	Displays the location where the archived redo logs are to be archived
`LOG_SEQUENCE`	Identifies the sequence number of the last archived redo log to be archived
`REOPEN_SECS`	Identifies the retry time, in seconds, after error
`DELAY_MINS`	Identifies the delay interval, in minutes, before the archived redo log is automatically applied to a standby database
`PROCESS`	Identifies the archiver process relative to the primary database, even if the query is issued on the standby database. Possible values are: `ARC``n` `FOREGROUND` `LGWR`
`REGISTER`	Indicates whether the archived redo log is registered in the remote destination control file. If the archived redo log is registered, it is available to the managed recovery operation. Possible values are: `YES` `NO`
`FAIL_DATE`	Indicates the date and time of error
`FAIL_SEQUENCE`	Indicates the sequence number of the archived redo log being archived when the last error occurred
`FAIL_BLOCK`	Indicates the block number of the archived redo log being archived when the last error occurred
`FAILURE_COUNT`	Identifies the current number of consecutive archival operation failures that have occurred for the destination
`MAX_FAILURE`	Allows you to control the number of times log transport services will attempt to reestablish communication and resume archival operations with a failed destination
`ERROR`	Displays the error text
`ALTERNATE`	Identifies the alternate destination, if any
`DEPENDENCY`	Identifies the dependent archive destination, if any
`REMOTE_TEMPLATE`	Displays the template to be used to derive the location to be recorded
`QUOTA_SIZE`	Identifies the destination quotas, expressed in bytes
`QUOTA_USED`	Identifies the size of all archived redo logs currently residing on the specified destination
`MOUNTID`	Identifies the instance mount identifier
`AFFIRM`	Displays disk I/O mode
`ASYNC_BLOCKS`	Specifies the number of blocks for the `ASYNC` attribute
`TRANSMIT_MODE`	Displays network transmission mode. Possible values are: `SYNC=PARALLEL` `SYNC=NOPARALLEL` `ASYNC[=blocks]`
`TYPE`	Indicates whether the archived log destination definition is `PUBLIC` or `PRIVATE`. Only `PUBLIC` destinations can be modified at runtime using the `ALTER SYSTEM SET` or `ALTER SESSION SET` statements. By default, all archived log destinations are `PUBLIC`.
`NET_TIMEOUT`	Specifies the number of seconds the log writer process will wait for status from the network server of a network operation issued by the log writer process

V$ARCHIVE_DEST_STATUS

The V$ARCHIVE_DEST_STATUS view displays runtime and configuration information for the archived redo log destinations.

Note:

The information in this view does not persist across an instance shutdown.

The V$ARCHIVE_DEST_STATUS view contains the following columns:

Column	Description
`DEST_ID`	Identifies the log archive destination parameter
`STATUS`	Identifies the current status of the destination. Possible values are: `VALID` - initialized and available `INACTIVE` - no destination information `DEFERRED` - manually disabled by the user `ERROR` - error during open or copy `DISABLED` - disabled after error `BAD PARAM` - parameter has errors `ALTERNATE` - destination is in an alternate state `FULL` - exceeded quota size for the destination
`TYPE`	Identifies the type of archival destination database. Possible values are: `LOCAL` - local to primary instance `PHYSICAL` - physical standby database `CROSS-INSTANCE` - an instance of the primary database
`DATABASE_MODE`	Identifies the current mode of the archival destination database. Possible values are: `STARTED` - instance started, not mounted `MOUNTED` - mounted `MOUNTED-STANDBY` - mounted standby `OPEN` - open read/write `OPEN_READ-ONLY` - open read-only
`RECOVERY_MODE`	Identifies the current mode of media recovery at the archival destination database. Possible values are: `IDLE` - managed recovery is not active `MANUAL` - manual media recovery is active `MANAGED` - managed recovery is active
`DESTINATION`	Displays the location where the archived redo logs are to be archived
`ARCHIVED_THREAD#`	Identifies the thread number of the most recent archived redo log received at the destination
`ARCHIVED_SEQ#`	Identifies the log sequence number of the most recent archived redo log received at the destination
`APPLIED_THREAD#`	Identifies the thread number of the most recent applied redo log received at the destination
`APPLIED_SEQ#`	Identifies the log sequence number of the most recent applied redo log received at the destination
`ERROR`	Displays the error text
`STANDBY_LOGFILE_COUNT`	Indicates the total number of standby redo logs created on the standby database
`STANDBY_LOGFILE_ACTIVE`	Indicates the total number of standby redo logs on the standby database that are active and contain primary database online redo log information
`PROTECTION_MODE`	Indicates whether the database is protected. Possible values are: `MAXIMUM PROTECTED` `MAXIMUM AVAILABILITY` `RESYNCHRONIZATION` `MAXIMUM PERFORMANCE` `UNPROTECTED`
`SRL`	Indicates the use of standby redo logs on the standby database. Possible values are: `YES` `NO`

V$ARCHIVE_GAP

The V$ARCHIVE_GAP view displays information to help you identify an archive gap. The V$ARCHIVE_GAP view contains the following columns:

Column	Description
`THREAD#`	Specifies the thread number
`LOW_SEQUENCE#`	Specifies the low number of the log file
`HIGH_SEQUENCE#`	Specifies the high number of the log file

V$ARCHIVED_LOG

The V$ARCHIVED_LOG view displays archived redo log information from the control file, including archived log names. This view contains the following columns:

Column	Description
`RECID`	Archived log record ID
`STAMP`	Archived log record stamp
`NAME`	Archived log filename. If set to `NULL`, the log file was cleared before it was archived.
`DEST_ID`	The original destination from which the archived log was generated. Value is 0 if the destination identifier is not available.
`THREAD#`	Redo thread number
`SEQUENCE#`	Redo log sequence number
`RESETLOGS_CHANGE#`	Resetlogs change number of the database when this log was written
`RESETLOGS_TIME`	Resetlogs time of the database when this log was written
`FIRST_CHANGE#`	First change number in the archived log
`FIRST_TIME`	Timestamp of the first change
`NEXT_CHANGE#`	First change in the next log
`NEXT_TIME`	Timestamp of the next change
`BLOCKS`	Size of the archived log in blocks
`BLOCK_SIZE`	Redo log block size. This is the logical block size of the archived log, which is the same as the logical block size of the online log from which this archived log was copied. The online log logical block size is a platform-specific value that is not adjustable by the user.
`CREATOR`	Identifies the creator of the archived log
`REGISTRAR`	Identifies the registrar of the entry
`STANDBY_DEST`	Indicates if the entry is an archived log destination
`ARCHIVED`	Indicates that the online redo log was archived or that RMAN only inspected the log and created a record for future application of redo logs during recovery
`APPLIED`	Indicates whether the archived log has been applied to its corresponding standby database
`DELETED`	Specifies 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
`STATUS`	The status of this archived log. Possible values are: `A` - Available `D` - Deleted `U` - Unavailable `X` - Expired
`COMPLETION_TIME`	Indicates the time when the archiving completed
`DICTIONARY_BEGIN`	Indicates whether this log contains the start of a LogMiner dictionary
`DICTIONARY_END`	Indicates whether this log contains the end of a LogMiner dictionary
`BACKUP_COUNT`	Indicates the number of times this file has been backed up. Values range from 0 to 15. If the file has been backed up more than 15 times, the value remains 15.
`END_OF_REDO`	Indicates whether this archived redo log contains the end of all redo information from the primary database. Values are `YES` and `NO`.
`ARCHIVAL_THREAD#`	Indicates the redo thread number of the instance that performed the archival operation. This column differs from the `THREAD#` column only when a closed thread is archived by another instance.
`ACTIVATION#`	Indicates the number assigned to the database instantiation.

V$DATABASE

The V$DATABASE view provides database information from the control file. This view contains the following columns:

Column	Description
`DBID`	The database identifier that is calculated when the database is created. This identifier is stored in all file headers.
`NAME`	Name of the database
`CREATED`	Creation date
`RESETLOGS_CHANGE#`	Change number at open resetlogs
`RESETLOGS_TIME`	Timestamp of open resetlogs
`PRIOR_RESETLOGS_CHANGE#`	Change number at prior resetlogs
`PRIOR_RESETLOGS_TIME`	Timestamp of prior resetlogs
`LOG_MODE`	Archive log mode
`CHECKPOINT_CHANGE#`	Last SCN checkpointed
`ARCHIVE_CHANGE#`	Last SCN archived
`CONTROLFILE_TYPE`	The type of control file. Possible values are: `STANDBY` - indicates database is in standby mode `LOGICAL` - indicates the database is a logical standby database `CLONE` - indicates a clone database `BACKUP \| CREATED` - indicates database is being recovered using a backup or created control file `CURRENT` - indicates the database is available for general use
`CONTROLFILE_CREATED`	Control file creation timestamp
`CONTROLFILE_SEQUENCE#`	Control file sequence number incremented by control file transactions
`CONTROLFILE_CHANGE#`	Last change number in the backup control file. Set to `NULL` if the control file is not a backup.
`CONTROLFILE_TIME`	Last timestamp in the backup control file. Set to `NULL` if the control file is not a backup.
`OPEN_RESETLOGS`	Indicates whether the next database open allows or requires the resetlogs option
`VERSION_TIME`	The version time
`OPEN_MODE`	Open mode information
`PROTECTION_MODE`	Indicates whether the database is protected. Possible values are: `MAXIMUM PROTECTED` `MAXIMUM AVAILABILITY` `RESYNCHRONIZATION` `MAXIMUM PERFORMANCE` `UNPROTECTED`
`PROTECTION_LEVEL`	Displays the aggregated protection mode currently in effect on the primary or standby database. Possible values are: `MAXIMUM PROTECTION` `MAXIMUM AVAILABILITY` `RESYNCHRONIZATION` `MAXIMUM PERFORMANCE` `UNPROTECTED`
`REMOTE_ARCHIVE`	The value of the `REMOTE_ARCHIVE_ENABLE` initialization parameter. Possible values are: `true` `false` `send` `receive`
`ACTIVATION#`	Number assigned to the database instantiation.
`DATABASE_ROLE`	Current role of the database; either primary or standby
`ARCHIVELOG_CHANGE#`	Highest `NEXT_CHANGE#` (from the `V$ARCHIVED_LOG` view) for an archived log
`SWITCHOVER_STATUS`	Specifies whether switchover is allowed. Possible values are: `NOT ALLOWED` - Either this is a standby database and the primary database has not been switched first or this is a primary database and there are no standby databases. `SESSIONS ACTIVE` - Indicates that there are active SQL sessions attached to the primary or standby database that need to be disconnected before the switchover operation is permitted. Query the `V$SESSION` view to identify the specific processes that need to be terminated. `SWITCHOVER PENDING` - This is a standby database and the primary database switchover request has been received but not processed. `SWITCHOVER LATENT` - The switchover was in pending mode, but did not complete and went back to the primary database. `TO PRIMARY` - This is a standby database and is allowed to switch over to a primary database. `TO STANDBY` - This is a primary database and is allowed to switch over to a standby database. `RECOVERY NEEDED` - This is a standby database that has not received the switchover request.
`GUARD_STATUS`	Protects data from being changed. Possible values are: `ALL` - Indicates all users other than `SYS` are prevented from making changes to any data in the database. `STANDBY` - Indicates all users other than `SYS` are prevented from making changes to any database object being maintained by logical standby. `NONE` - Indicates normal security for all data in the database.
`SUPPLEMENTAL_LOG_DATA_MIN`	Ensures that LogMiner will have sufficient information to support chained rows and various storage arrangements such as cluster tables. See Oracle9i SQL Reference for additional information about the `ALTER DATABASE ADD SUPPLEMENTAL LOG DATA` statement.
`SUPPLEMENTAL_LOG_DATA_PK`	For all tables with a primary key, ensures that all columns of the primary key are placed into the redo log whenever an update operation is performed. See Oracle9i SQL Reference for additional information about the `ALTER DATABASE ADD SUPPLEMENTAL LOG DATA` statement.
`SUPPLEMENTAL_LOG_DATA_UI`	For all tables with a unique key, ensures that if any unique key columns are modified, all other columns belonging to the unique key are also placed into the redo log. See Oracle9i SQL Reference for additional information about the `ALTER DATABASE ADD SUPPLEMENTAL LOG DATA` statement.
`FORCE_LOGGING`	Redo generation is forced even for `NOLOGGING` operations. Possible values are: `YES` `NO`
`DATAGUARD_BROKER`	Indicates whether the Data Guard configuration is being managed by the broker. Possible values are: `ENABLED` indicates the configuration is under the control of the broker `DISABLED` indicates the configuration is not under the control of the broker

V$DATAFILE

The V$DATAFILE view provides datafile information from the control file. This view contains the following columns:

Column	Description
`FILE#`	File identification number
`CREATION_CHANGE#`	Change number at which the datafile was created
`CREATION_TIME`	Timestamp of the datafile creation
`TS#`	Tablespace number
`RFILE#`	Tablespace relative datafile number
`STATUS`	Type of file (system or user) and its status. Possible values are: `OFFLINE` - cannot be written to `ONLINE` - can be written to `SYSTEM` - system datafile `RECOVER` - needs recovery `SYSOFF` - offline system
`ENABLED`	Describes how accessible the file is from SQL. Possible values are: `DISABLED` - no SQL access allowed `READ ONLY` - no SQL updates allowed `READ WRITE` - full access allowed
`CHECKPOINT_CHANGE#`	SCN at last checkpoint
`CHECKPOINT_TIME`	Timestamp of the last checkpoint
`UNRECOVERABLE_CHANGE#`	Last unrecoverable change number made to this datafile. This column is always updated when an unrecoverable operation completes.
`UNRECOVERABLE_TIME`	Timestamp of the last unrecoverable change
`LAST_CHANGE#`	Last change number made to this datafile. Set to `NULL` if the datafile is being changed.
`LAST_TIME`	Timestamp of the last change
`OFFLINE_CHANGE#`	Offline change number of the last offline range. This column is updated only when the datafile is brought online.
`ONLINE_CHANGE#`	Online change number of the last offline range
`ONLINE_TIME`	Online timestamp of the last offline range
`BYTES`	Current datafile size in bytes; 0 if inaccessible
`BLOCKS`	Current datafile size in blocks; 0 if inaccessible
`CREATE_BYTES`	Size when created, in bytes
`BLOCK_SIZE`	Block size of the datafile
`NAME`	Datafile name
`PLUGGED_IN`	Describes whether the tablespace is plugged in. The value is 1 if the tablespace is plugged in and has not been made read/write; 0 if not.
`BLOCK1_OFFSET`	The offset from the beginning of the file to where the Oracle generic information begins. The exact length of the file can be computed as follows: `BYTES + BLOCK1_OFFSET`
`AUX_NAME`	The auxiliary name that has been set for this file

V$DATAGUARD_STATUS

The V$DATAGUARD_STATUS view displays and logs events that would typically be triggered by any message to the alert log or server process trace files.

Note:

The information in this view does not persist across an instance shutdown.

The V$DATAGUARD_STATUS view contains the following columns:

Column	Description
`INST_ID`	The ID of the instance encountering the event. This column is present in the `GV$DATAGUARD_STATUS` view and not in the `V$DATAGUARD_STATUS` view.
`FACILITY`	Facility that encountered the event. Possible values are: `CRASH RECOVERY` `LOG TRANSPORT SERVICES` `LOG APPLY SERVICES` `ROLE MANAGEMENT SERVICES` `REMOTE FILE SERVER` `FETCH ARCHIVE LOG` `DATA GUARD` `NETWORK SERVICES`
`SEVERITY`	The severity of the event. Possible values are: `INFORMATIONAL` - informational message `WARNING` - warning message `ERROR` - indicates the process has failed `FATAL` `CONTROL` - an expected change in state, such as the start or completion of an archival, log recovery, or switchover operation
`DEST_ID`	The destination ID number to which the event pertains. If the event does not pertain to a particular destination, the value is 0.
`MESSAGE_NUM`	A chronologically increasing number giving each event a unique number
`ERROR_CODE`	The error ID pertaining to the event
`CALLOUT`	Indicates whether the current entry is a callout event. Possible values are: `YES` `NO` A `YES` value indicates that this event may require the DBA to perform some action. Examine the `ERROR_CODE` and `MESSAGE` columns for more information. A `NO` value generally corresponds to an `INFORMATIONAL` or `WARNING` event that does not require any action by the DBA.
`TIMESTAMP`	The date and time when the entry was created.
`MESSAGE`	A text message describing the event

V$LOG

The V$LOG view contains log file information from the online redo logs. This view contains the following columns:

Column	Description
`GROUP#`	Log group number
`THREAD#`	Log thread number
`SEQUENCE#`	Log sequence number
`BYTES`	Size of the log in bytes
`MEMBERS`	Number of members in the log group
`ARCHIVED`	Archive status
`STATUS`	Indicates the log status. Possible values are: `UNUSED` - The online redo log has never been written to. This is the status of a redo log that was just added, or just after specifying a `RESETLOGS` option when it is not the current redo log. `CURRENT` - This is the current redo log. This implies that the redo log is active. The redo log could be open or closed. `ACTIVE` - The log is active but is not the current log. It is needed for failure recovery. It may be in use for block recovery. It might or might not be archived. `CLEARING` - The log is being re-created as an empty log after an `ALTER DATABASE CLEAR LOGFILE` statement. After the log is cleared, the status changes to `UNUSED`. `CLEARING_CURRENT` - The current log is being cleared of a closed thread. The log can stay in this status if there is some failure in the switch, such as an I/O error writing the new log header. `INACTIVE` - The log is no longer needed for instance recovery. It may be in use for managed recovery. It might or might not be archived. `INVALIDATED` - Archived the current redo log without a log switch
`FIRST_CHANGE#`	Lowest SCN in the log
`FIRST_TIME`	Time of first SCN in the log

V$LOGFILE

The V$LOGFILE view contains information about the online redo logs. This view contains the following columns:

Column	Description
`GROUP#`	Redo log group identifier number
`STATUS`	Status of this log member. Possible values are: `INVALID` - file is inaccessible `STALE` - contents are incomplete `DELETED` - file is no longer used blank (no value listed) - file is in use
`MEMBER`	Redo log member name
`TYPE`	Specifies whether this is a standby log or an online log. Possible values are: `STANDBY` `ONLINE`

V$LOG_HISTORY

The V$LOG_HISTORY view contains log history information from the control file. This view contains the following columns:

Column	Description
`RECID`	Control file record ID
`STAMP`	Control file record stamp
`THREAD#`	Thread number of the archived log
`SEQUENCE#`	Sequence number of the archived log
`FIRST_CHANGE#`	Lowest SCN in the log
`FIRST_TIME`	Time of first entry (lowest SCN) in the log
`NEXT_CHANGE#`	Highest SCN in the log

V$LOGSTDBY (Logical Standby Databases Only)

The V$LOGSTDBY view provides dynamic information about what is happening to log apply services. This view is very helpful when you are diagnosing performance problems during the logical application of archived redo logs to the standby database, and it can be helpful for other problems. The V$LOGSTDBY view contains the following columns:

Column	Datatype	Description
`SERIAL#`	`NUMBER`	Contains the SQL session serial number. This data is used when joining this view with `V$SESSION` and `V$PX_SESSION` views.
`LOGSTDBY_ID`	`NUMBER`	Contains the parallel query slave ID
`PID`	`VARCHAR2(9)`	Contains the process ID
`TYPE`	`VARCHAR2(30)`	Indicates the task being performed by the process: `COORDINATOR`, `APPLIER`, `ANALYZER`, `READER`, `PREPARER`, `BUILDER`
`STATUS_CODE`	`NUMBER`	Contains the status number (or Oracle error code) belonging to the `STATUS` message
`STATUS`	`VARCHAR2(256)`	Description of the current activity of the process
`HIGH_SCN`	`NUMBER`	Contains the highest SCN seen by the process. This column is used to confirm the progress of the individual process.

V$LOGSTDBY_STATS (Logical Standby Databases Only)

The V$LOGSTDBY_STATS view displays LogMiner statistics, current state, and status information for a logical standby database during SQL apply operations. If log apply services are not running, the values for the statistics are cleared. This view contains the following columns:

Column Datatype Description

Column	Datatype	Description
`NAME`	`VARCHAR2(64)`	Name of the statistic, state, or status: Note: Many of the following statistics are subject to change or deletion; programmers should write application code to tolerate missing or extra statistics. Number of preparers Number of appliers Maximum SGA for LCR cache Parallel servers in use Transaction consistency Coodinator state Transactions scheduled Transactions applied Preparer memory allocation failures Builder memory allocation failures Attempts to handle low memory Successful low memory recovery Memory spills avoided Rollback attempts Successful rollbacks Memory spill attempts Successful memory spills Preparer ignored memory low water mark Builder ignored memory low water mark Mining resumed
`VALUE`	`VARCHAR2(64)`	The value of the statistic or state information

NAME

VARCHAR2(64)

Name of the statistic, state, or status:

Note: Many of the following statistics are subject to change or deletion; programmers should write application code to tolerate missing or extra statistics.

Number of preparers
Number of appliers
Maximum SGA for LCR cache
Parallel servers in use
Transaction consistency
Coodinator state
Transactions scheduled
Transactions applied
Preparer memory allocation failures
Builder memory allocation failures
Attempts to handle low memory
Successful low memory recovery
Memory spills avoided
Rollback attempts
Successful rollbacks
Memory spill attempts
Successful memory spills
Preparer ignored memory low water mark
Builder ignored memory low water mark
Mining resumed

VALUE

VARCHAR2(64)

The value of the statistic or state information

V$MANAGED_STANDBY (Physical Standby Databases Only)

The V$MANAGED_STANDBY view displays current and status information for Oracle database server processes related to the Data Guard environment. Use this view to query physical standby database only. The information in this view does not persist after an instance shutdown. The V$MANAGED_STANDBY view contains the columns shown in the following table:

Column	Description
`PROCESS`	Type of process whose information is being reported. Possible values are: `ARCH` - archiver process `RFS` - remote file server `MRP0` - detached recovery server process `MR(fg)` - foreground recovery session
`PID`	Operating system identifier of the process
`STATUS`	Current process status. Possible values are: `UNUSED` - no active process `ALLOCATED` - process is active but not currently connected to a primary database `CONNECTED` - network connection is established to a primary database `ATTACHED` - process is attached to, and communicating with, a primary database `IDLE` - process is not performing any activities `ERROR` - process has failed `OPENING` - process is opening the archived redo log `CLOSING` - process has completed the archival operation and is closing the archived redo log `WRITING` - process is actively writing archived redo log data `RECEIVING` - process is receiving network communication `ANNOUNCING` - process is announcing the existence of a potential dependent archived redo log `REGISTERING` - process is registering the existence of a completed dependent archived redo log `WAIT_FOR_LOG` - process is waiting for the archived redo log to be completed `WAIT_FOR_GAP` - process is waiting for the archive gap to be resolved `APPLYING_LOG` - process is applying the archived redo log to the standby database
`CLIENT_PROCESS`	Identifies the corresponding primary database process. Possible values are: `ARCHIVAL` - foreground (manual) archival process (SQL) `ARCH` - background ARCn process `LGWR` - background LGWR process
`CLIENT_PID`	Operating system identifier of the client process
`CLIENT_DBID`	Database identifier of the primary database
`GROUP#`	Standby redo log group
`THREAD#`	Archived redo log thread number
`SEQUENCE#`	Archived redo log sequence number
`BLOCK#`	Last processed archived redo log block number
`BLOCKS`	Size of the archived redo log in 512-byte blocks
`DELAY_MINS`	Archived redo log delay interval in minutes
`KNOWN_AGENTS`	Total number of standby database agents processing an archived redo log
`ACTIVE_AGENTS`	Number of standby database agents actively processing an archived redo log

V$STANDBY_LOG

The V$STANDBY_LOG view contains the following columns:

Column	Description
`GROUP#`	Log group number
`THREAD#`	Log thread number
`SEQUENCE#`	Log sequence number
`BYTES`	Size of the log in bytes
`USED`	Number of bytes used in the log
`ARCHIVED`	Archive status
`STATUS`	Indicates the log status. Possible values are: `UNUSED` - The online redo log has never been written to. This is the status of a redo log that was just added, or just after specifying a `RESETLOGS` option when it is not the current redo log. `CURRENT` - This is the current redo log. This implies that the redo log is active. The redo log could be open or closed. `ACTIVE` - The log is active but is not the current log. It is needed for failure recovery. It may be in use for block recovery. It might or might not be archived. `CLEARING` - The log is being re-created as an empty log after an `ALTER DATABASE CLEAR LOGFILE` statement. After the log is cleared, the status changes to `UNUSED`. `CLEARING_CURRENT` - The current log is being cleared of a closed thread. The log can stay in this status if there is some failure in the switch, such as an I/O error writing the new log header. `INACTIVE` - The log is no longer needed for instance recovery. It may be in use for managed recovery. It might or might not be archived. `INVALIDATED` - Archived the current redo log without a log switch.
`FIRST_CHANGE#`	Lowest SCN in the log
`FIRST_TIME`	Time of first SCN in the log
`LAST_CHANGE#`	Last change number made to this datafile. Set to `NULL` if the datafile is being changed.
`LAST_TIME`	Timestamp of the last change

14 Views

About Views

DBA_LOGSTDBY_EVENTS (Logical Standby Databases Only)

DBA_LOGSTDBY_LOG (Logical Standby Databases Only)

DBA_LOGSTDBY_NOT_UNIQUE (Logical Standby Databases Only)

DBA_LOGSTDBY_PARAMETERS (Logical Standby Databases Only)

DBA_LOGSTDBY_PROGRESS (Logical Standby Databases Only)

DBA_LOGSTDBY_SKIP (Logical Standby Databases Only)

DBA_LOGSTDBY_SKIP_TRANSACTION (Logical Standby Databases Only)

DBA_LOGSTDBY_UNSUPPORTED (Logical Standby Databases Only)

V$ARCHIVE_DEST

V$ARCHIVE_DEST_STATUS

V$ARCHIVE_GAP

V$ARCHIVED_LOG

V$DATABASE

V$DATAFILE

V$DATAGUARD_STATUS

V$LOG

V$LOGFILE

V$LOG_HISTORY

V$LOGSTDBY (Logical Standby Databases Only)

V$LOGSTDBY_STATS (Logical Standby Databases Only)

V$MANAGED_STANDBY (Physical Standby Databases Only)

V$STANDBY_LOG

14
Views