V$ARCHIVE_DEST_STATUS

V$ARCHIVE_DEST_STATUS displays runtime and configuration information for the archived redo log destinations. The information in this view does not persist across an instance shutdown.

Column	Datatype	Description
DEST_ID	NUMBER	Identifies the log archive destination parameter (1 to 10)
DEST_NAME	VARCHAR2(256)	Log archive destination parameter name
STATUS	VARCHAR2(9)	Current status of the destination: 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	VARCHAR2(14)	Type of archival destination database: LOCAL - Local to primary database PHYSICAL - Physical standby CROSS-INSTANCE - An instance of the primary LOGICAL - Logical standby
DATABASE_MODE	VARCHAR2(15)	Current mode of the archival destination database: STARTED - Instance started, not mounted MOUNTED - Mounted MOUNTED-STANDBY - Mounted standby OPEN - Open read/write OPEN_READ-ONLY - Open read-only
RECOVERY_MODE	VARCHAR2(23)	Current mode of media recovery at the archival destination database: IDLE - Managed recovery is not active MANUAL - Manual media recovery active MANAGED - Managed recovery is active MANAGED REAL TIME APPLY - Log apply services recover redo data from standby redo logs at the same time the logs are being written to, as opposed to recovering redo from archived redo logs when a log switch occurs
PROTECTION_MODE	VARCHAR2(20)	Indicates whether the database is protected: MAXIMUM PROTECTION MAXIMUM AVAILABILITY RESYNCHRONIZATION MAXIMUM PERFORMANCE UNPROTECTED
DESTINATION	VARCHAR2(256)	Specifies the location where the redo data is to be archived
STANDBY_LOGFILE_COUNT	NUMBER	Indicates the total number of standby redo logs created on the standby database
STANDBY_LOGFILE_ACTIVE	NUMBER	Indicates the total number of standby redo logs on the standby database that are active and contain primary database online redo log information
ARCHIVED_THREAD#	NUMBER	Identifies the thread number of the most recent archived redo log received at the destination
ARCHIVED_SEQ#	NUMBER	Identifies the log sequence number of the most recent archived redo log received at the destination
APPLIED_THREAD#	NUMBER	Identifies the thread number of the most recent applied redo log received at the destination
APPLIED_SEQ#	NUMBER	Identifies the log sequence number of the most recent applied redo log received at the destination
ERROR	VARCHAR2(256)	Displays the error text
SRL	VARCHAR2(3)	Indicates whether standby redo logfiles are used on the standby database (YES) or not (NO)
DB_UNIQUE_NAME	VARCHAR2(30)	Specifies the unique database name of the current instance that was defined with the DB_UNIQUE_NAME attribute on the LOG_ARCHIVE_DEST_n parameter
SYNCHRONIZATION_STATUS	VARCHAR2(22)	Possible values for this column are as follows: CHECK CONFIGURATION - This database or destination does not support synchronization. CHECK STANDBY REDO LOG - The standby redo log at this destination is configured improperly. CHECK NETWORK - One or more instances of this database cannot send redo data to this destination. DESTINATION HAS A GAP - This destination is missing redo data needed for synchronization with this database. OK - This destination is synchronized with this database. NOT AVAILABLE - Synchronization status is not available.
SYNCHRONIZED	VARCHAR2(3)	Possible values are: YES - This destination is synchronized with the primary database. NO - The destination is not synchronized with the primary database. UNKNOWN - The synchronization status of this destination cannot be determined.

Note:

1.       Scripts using V$ARCHIVE_DEST_STATUS

select dest_name, status, type, database_mode, recovery_mode,        protection_mode, destination, applied_seq#, error from   V$ARCHIVE_DEST_STATUS order by 2 desc;

Oracle data dictionary views

Oracle dynamic performance views

Last updated: 2009-11-24 Tuesday

V$ARCHIVE_GAP

V$ARCHIVE_GAP displays information about archive gaps on a standby database. This view can be used to find out the current archive gap that is blocking recovery for the current recovery incarnation.

Column	Datatype	Description
THREAD#	NUMBER	Thread number of the missing archived redo log files. The number is 1 for a single instance. For Real Application Clusters, this column will contain different numbers.
LOW_SEQUENCE#	NUMBER	Lowest sequence number of the log files received on the standby system
HIGH_SEQUENCE#	NUMBER	Highest sequence number of the log files received on the standby system

Oracle data dictionary views

Oracle dynamic performance views

Last updated: 2009-11-24 Tuesday

V$ARCHIVE_PROCESSES

V$ARCHIVE_PROCESSES displays the state of the various ARCH processes for the instance.

Column	Datatype	Description
PROCESS	NUMBER	Identifier for the ARCH process for the instance, numbered from 0-9
STATUS	VARCHAR2(10)	Status of the ARCH process, displayed as a keyword. Possible values are: STOPPED, SCHEDULED, STARTING, ACTIVE, STOPPING, and TERMINATED.
LOG_SEQUENCE	NUMBER	This is the online redo log sequence number currently being archived, if STATE="BUSY"
STATE	VARCHAR2(4)	This is the current state of the ARCH process, displayed as a keyword. Possible keywords are IDLE or BUSY.

Oracle data dictionary views

Oracle dynamic performance views

Last updated: 2009-11-24 Tuesday

V$CLUSTER_INTERCONNECTS

V$CLUSTER_INTERCONNECTS displays one or more interconnects that are being used for cluster communication.

Column	Datatype	Description
NAME	VARCHAR2(15)	Name of the interconnect (such as eth0)
IP_ADDRESS	VARCHAR2(16)	IP address of the interconnect
IS_PUBLIC	VARCHAR2(4)	If the value is YES, the interface is known to the public. If the value is NO, the interface is known to be private. Note that if the CLUSTER_INTERCONNETS initialization parameter is also specified, then it is expected that the interconnect is private. Oracle expects cluster traffic to be run on private interconnects only. f the value is empty, it is unknown whether the interface is public or private. Oracle Corporation recommends that you set the interface for Real Application Clusters (RAC) communication in the Oracle Cluster Repository (OCR).
SOURCE	VARCHAR2(31)	Indicates where this interface was picked up from: Oracle Cluster Repository - Interface was configured in the OCR and Oracle Database found the interface in the OCR Operating-system dependent software - Oracle Database automatically detects this CLUSTER_INTERCONNECTS parameter - This initialization parameter was set

Oracle data dictionary views

Oracle dynamic performance views

Last updated: 2009-11-23 Monday

V$CONFIGURED_INTERCONNECTS

V$CONFIGURED_INTERCONNECTS displays all interconnects that Oracle is aware of. This view attempts to answer the question of where Oracle found the information about a specific interconnect.

Column	Datatype	Description
NAME	VARCHAR2(15)	Name of the interconnect (such as eth0)
IP_ADDRESS	VARCHAR2(16)	IP address of the interconnect
IS_PUBLIC	VARCHAR2(4)	If the value is YES, the interface is known to the public. If the value is NO, the interface is known to be private. Note that if the CLUSTER_INTERCONNETS initialization parameter is also specified, then it is expected that the interconnect is private. Oracle expects cluster traffic to be run on private interconnects only. If the value is empty, it is unknown whether the interface is public or private. Oracle Corporation recommends that you set the interface for Real Application Clusters (RAC) communication in the Oracle Cluster Repository (OCR).
SOURCE	VARCHAR2(31)	Indicates where this interface was picked up from: Oracle Cluster Repository - Interface was configured in the OCR and Oracle Database found the interface in the OCR Operating-system dependent software - Oracle Database automatically detects this CLUSTER_INTERCONNECTS parameter - This initialization parameter was set

Oracle data dictionary views

Oracle dynamic performance views

Last updated: 2009-11-23 Monday

V$CORRUPT_XID_LIST

V$CORRUPT_XID_LIST displays all corrupted XIDs.

Column	Datatype	Description
CORRUPT_XID	VARCHAR2(256)	Name of corrupt XID

Note:

1.        Oracle 11g introduced a new feature called health monitor, which check undo segment integrity. This check finds logical undo corruptions. After locating an undo corruption, this check uses PMON and SMON to try to recover the corrupted transaction. If this recovery fails, then Health Monitor stores information about the corruption in V$CORRUPT_XID_LIST. Most undo corruptions can be resolved by forcing a commit.

Oracle data dictionary views

Oracle dynamic performance views

Last updated: 2009-11-23 Monday