|
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 logical standby databases. |
|
DBA_LOGSTDBY_NOT_UNIQUE
|
Logical only |
Identifies tables that have no primary and no non-null unique indexes. |
|
DBA_LOGSTDBY_PARAMETERS
|
Logical 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_LOGSTDBY_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 tables (and columns in those tables) that contain unsupported datatypes. Use this view when you are preparing to create a logical standby database. |
|
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 current value, mode, and status.
Note: The information in this view does not persist across an instance shutdown. |
|
V$ARCHIVE_DEST_STATUS
|
Primary, physical, and logical |
Displays runtime and configuration information for the archived redo log destinations.
Note: The information in this view does not persist across an instance shutdown. |
|
V$ARCHIVE_GAP
|
Physical and logical |
Displays information to help you identify a gap in the archived redo log files. |
|
V$ARCHIVED_LOG
|
Primary, physical, and logical |
Displays archive redo log information from the control file, including names of the archived redo log files. |
|
V$DATABASE
|
Primary, physical, and logical |
Provides database information from the control file. |
|
V$DATABASE_INCARNATION
|
Primary, physical, and logical |
Displays information about all database incarnations. Oracle Database creates a new incarnation whenever a database is opened with the RESETLOGS option. Records about the current and the previous incarnation 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 records 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 the online redo log files. |
|
V$LOGFILE
|
Primary, physical, and logical |
Contains information 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 standby 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 database 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 standby 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. |
