14
Views Relevant to Oracle Data Guard

This chapter describes the views that are significant in a Data Guard environment. The view described in this chapter are a subset of the views that are available for Oracle databases.

Table 14-1 describes the views and indicates if a view applies to physical standby databases, logical standby databases, or primary databases.See Oracle Database Reference for complete information about views.

Table 14-1 Views That Are Pe rtinent to Data Guard Configurations

View	Database	Description
< a name="88136"> `DBA_LOGSTDBY_EVENTS`	Logical only	Contains information about the activity of the logical standby database system. It can be used to determine the cause of failures that occur when SQL Apply is applying redo to logical standby databases.
`DBA_LOGSTDBY_LOG`	Logical only	Shows the log files registered for logica l standby databases.
`DBA_LOGSTDBY_NOT_UNIQUE`	Logical only	Identifies tables that have no primary and no non-null unique indexes.
`DBA_LOGSTDBY_PARAMETERS`	Logic al only	Contains the list of parameters used by SQL apply.
`DBA_LOGSTDBY_PROGRESS`	Logical only	Describes the progress of SQL Apply on the logical standby database.
`DBA_LO GSTDBY_SKIP`	Logical only	Lists the tables that will be skipped by SQL Apply.
`DBA_LOGSTDBY_SKIP_TRANSACTION`	Logical only	Lists the skip settings chosen.
`DBA_LOGSTDBY_UNSUPPORTED`	Logical only	Identifies the schemas and tabl es (and columns in those tables) that contain unsupported datatypes. Use this view when you are preparing to create a logical standby database.
`< a class="xlinkSRC REFRN30007" href="../../server$101/b10755/dynviews_1011.htm#REFRN30007">V$ARCHIVE_DEST`	Primary, physical, and logical	Describes, for the current instance, all of the destinations in the Data Guard configuration, including each destination's c urrent value, mode, and status. Note: The information in this vi ew does not persist across an instance shutdown.
`V$ARC HIVE_DEST_STATUS`	Primary, physical, and logical
`V$ARCHIVE_GAP`	Physical and logical	< p class="TB">Displays information to help you identify a gap in the archived redo log files.
`V$ARCHIVED_LOG`	Primary, physical, and logical
`V$DATABASE`	Primary, physical, and logical	Provides databa se information from the control file.
`V$DATABASE_INCA RNATION`	Primary, physical, and logical	Displays information about all database incarnations. Oracle Database creates a new in carnation whenever a database is opened with the `RESETLOGS` option. Records about the current and the previous incarnatio n are also contained in the `V$DATABASE` view.
`V$DATAFILE`	Primary, physical, and logical	Provides datafile information from the control file.
`V$DATAGUARD_CONFIG`	Primary, physical, and logical	Lists the unique database names defined with the `DB_UNIQUE_NAME` and `LOG_ARCHIVE_CONFIG` initialization parameters.
`V$DATAGUARD_STATUS`	Primary, physical, and logical	Displays and reco rds events that would typically be triggered by any message to the alert log or server process trace files.
`V$LOG`	Primary, physical, and logical	Contains log file information from t he online redo log files.
`V$LOGFILE`	< /a> Primary, physical, and logical	Contains informatio n about the online redo log files and standby redo log files.
`V$LOG_HISTORY`	Primary, physical, and logical	Contains log history information from the control file.
`V$LOGSTDBY`	Logical only	Provides dynamic information about what is happening with SQL Apply. This view is very helpful when you are diagnosing performance problems during SQL Apply on the logical sta ndby database, and it can be helpful for other problems.
`V$LOGSTDBY_STATS`	Logical only	Displays LogMiner statistics, current state, and status information for a logical standby data base during SQL Apply. If SQL Apply is not running, the values for the statistics are cleared.
`V$MANAGED_STANDBY`	Physical only	Displays current status information for Oracle database processes related to physical standb y databases. Note: The information in this view does not persist across an instance shutdown.
`V$STANDBY_LOG`	Physical and logical	Contains log file information from the standby redo log files.

View

Database

Description

< a name="88136">

DBA_LOGSTDBY_EVENTS

Logical only

Contains information about the activity of the logical standby database system. It can be used to determine the cause of failures that occur when SQL Apply is applying redo to logical standby databases.

DBA_LOGSTDBY_LOG

Logical only

Shows the log files registered for logica l standby databases.

DBA_LOGSTDBY_NOT_UNIQUE

Logical only

Identifies tables that have no primary and no non-null unique indexes.

DBA_LOGSTDBY_PARAMETERS

Logic al only

Contains the list of parameters used by SQL apply.

DBA_LOGSTDBY_PROGRESS

Logical only

Describes the progress of SQL Apply on the logical standby database.

DBA_LO GSTDBY_SKIP

Logical only

Lists the tables that will be skipped by SQL Apply.

DBA_LOGSTDBY_SKIP_TRANSACTION

Logical only

Lists the skip settings chosen.

DBA_LOGSTDBY_UNSUPPORTED

Logical only

Identifies the schemas and tabl es (and columns in those tables) that contain unsupported datatypes. Use this view when you are preparing to create a logical standby database.

< a class="xlinkSRC REFRN30007" href="../../server$101/b10755/dynviews_1011.htm#REFRN30007">V$ARCHIVE_DEST