Shulou(Shulou.com)06/01 Report--

Main library:

V$managed_standby

V$archive_dest_status

V$archive_dest

Prepare the library:

V$archived_log

Explanation: explanation of V$ARCHIVED_LOG:

V $ARCHIVED_LOG

V$ARCHIVED_LOG displays archive log information in the control file, including the archive log name. Insert the archive log record after successfully archiving or clearing the online redo log (NULL, the name column if the log has been cleared). If the log is archived twice, it will appear with two identical archive log records THREAD#, SEQUENCE#, and FIRST_CHANGE#, but with different names. Archived log records are also inserted when you restore an archived log from a backup set or copy, and when you create a log copy using the RMAN COPY command.

The column data type describes the log record of the RECIDNUMBER archive the log record stamp of the IDSTAMPNUMBER archive the log file name of the NAMEVARCHAR2 archive. If set to NULL, the log files are cleared before archiving, or a RMAN backup command with the Delete input option is executed to back up archivelog all (RMAN > backup archivelog all delete input;). The original target where the DEST_IDNUMBER generated the archived log. Value means that the target identifier is not available. THREAD#NUMBER redo thread number SEQUENCE#NUMBER redo log sequence number RESETLOGS_CHANGE#NUMBER rewrite log change database number RESETLOGS_TIMEDATE when writing log reset logging database time RESETLOGS_IDNUMBER associated with archived redo log Resetlogs identifier FIRST_CHANGE#NUMBER first change number FIRST_TIMEDATE first change timestamp NEXT_CHANGE#NUMBER in archived log first in the next log The time stamp of the next change in the NEXT_TIMEDATE the size of the BLOCKSNUMBER archive log in blocks the BLOCK_SIZENUMBER redo log block size. This is the logical block size of the archive log, which is the same size as the online log from which the archive log was copied. The online log logical block size is platform-specific and cannot be adjusted by the user. Creator of CREATORVARCHAR2 (7) Archive Log:

ARCH-Archiving proc

FGRD-foreground process

RMAN-recovery Manager

SRMN-RMAN stand by

LGWR-Recorder proc

The registry of the REGISTRARVARCHAR2 (7) Registry:

RFS-remote File Server process

ARCH-Archiving proc

FGRD-foreground process

RMAN-recovery Manager

SRMN-RMAN stand by

LGWR-Recorder proc

STANDBY_DESTVARCHAR2 (3) indicates whether the entry is an archivelog target (YES) or not (NO) ARCHIVEDVARCHAR2 (3) indicates whether the online redo log has been archived (YES) or whether the RMAN only examines the log and creates a record for future application of the redo log during recovery (NO).

See also the Oracle Database backup and recovery user Guide.

APPLIEDVARCHAR2 (9) indicates whether the archive redo log file has been applied to the corresponding physical standby database. This value is always a local destination for NO.

For a physical standby database with row REGISTRAR =, this column makes sense RFS:

If REGISTRAR = RFS and APPLIED = NO, the log file has been received but has not been applied.

If REGISTRAR = RFS and APPLIED = IN-MEMORY, the log file has been applied to memory, but the data file has not been updated.

If REGISTRAR = RFS and APPLIED = YES, apply the log file and update the data file.

This column can be used to identify log files that can be backed up and deleted. When used for this purpose, IN-MEMORY should treat this value as an as-is NO.

DELETEDVARCHAR2 (3) indicates whether the RMAN DELETE command has physically deleted the archive log file from disk and whether it (NO) STATUSVARCHAR2 (1) archive log status has been logically deleted from the control file and recovery directory (YES) of the target database:

A-availabl

D-deleted

U-unavailabl

X-expired

Time the COMPLETION_TIMEDATE archive completed DICTIONARY_BEGINVARCHAR2 (3) indicates whether the log contains the beginning of the LogMiner dictionary (YES) or not (NO) DICTIONARY_ENDVARCHAR2 (3) indicates whether the log contains the end of the LogMiner dictionary (YES) or does not contain (NO) END_OF_REDOVARCHAR2 (3) indicates whether the archived redo log contains all redo information from the autonomous database (YES) the end (NO) BACKUP_COUNTNUMBER 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 is still 15. ARCHIVAL_THREAD#NUMBER redoes the thread number of the instance that performed the archiving operation. THREAD# this column is different from the column only if the closed thread is archived by another instance. The number IS_RECOVERY_DEST_FILEVARCHAR2 (3) assigned by ACTIVATION#NUMBER to the database instance indicates whether the file is created in the fast recovery area (YES) (NO) COMPRESSEDVARCHAR2 (3) reserved for internal use FALVARCHAR2 (3) indicates whether the archive log is generated as a result of the FAL request (YES) END_OF_REDO_TYPEVARCHAR2 (10) available values are as follows:

SWITCHOVER-displays the archive redo log files generated at the end of the switch

TERMINAL-displays archive redo log files generated after failover

RESETLOGS-displays the online redo log files archived on the primary database after the ALTER DATABASE OPEN RESETLOGS release statement

ACTIVATION-displays all log files archived on the physical standby database after ALTER DATABASE ACTIVATE STANDBY DATABASE issued the statement

"empty string"-any empty string indicates that the log is just a normal archive and is not archived due to any other event

BACKED_BY_VSSVARCHAR2 (3) whether the file was backed up by the Volume Shadow copy Service (VSS). This column is reserved for internal use.

With regard to V$ARCHIVE_DEST 's explanation:

V $ARCHIVE_DEST

V$ARCHIVE_DEST displays all targets in the Data Guard configuration in the current instance, including the current value, mode, and status of each target.

The column data type describes the DEST_IDNUMBER log archive target parameter identifier (1 to 31) DEST_NAMEVARCHAR2 (256) records the archive target parameter name STATUSVARCHAR2 (9) identifies the current state of the target:

VALID-initialization and availability

INACTIVE-No destination information

DEFERRED-manually disabled by the user

ERROR-error during opening or copying

DISABLED-disable after error

BAD PARAM-error in the parameter

ALTERNATE-destination is in standby state

FULL-quota size that exceeds the destination

BINDINGVARCHAR2 (9) specifies how the failure will affect the archive operation:

MANDATORY-successful archiving is required

OPTIONAL-No successful archiving is required (depending on LOG_ARCHIVE_MIN_SUCCEED_DEST)

NAME_SPACEVARCHAR2 (7) identifies the range of parameter settings:

SYSTEM-system definition

SESSION-session definition

TARGETVARCHAR2 (7) specifies whether the archive target is the local destination of the primary database or the remote database:

PRIMARY-Local

STANDBY-remote

ARCHIVERVARCHAR2 (10) identifies the archiving process associated with the database that issued the query:

ARC n

FOREGROUND

LGWR

RFS

SCHEDULEVARCHAR2 (8) indicates that the files for this target are INACTIVE, PENDING, ACTIVE. Or LATENTDESTINATIONVARCHAR2 specify the archiving location of the archived redo log LOG_SEQUENCENUMBER identifies the sequence number of the last archived redo log to be archived the retry time (in seconds) DELAY_MINSNUMBER identifies the delay interval (in minutes) before the archived redo log is automatically applied to the standby database) the maximum number of MAX_CONNECTIONSNUMBER connections the NET_TIMEOUTNUMBER log writer process will wait from the log Number of seconds PROCESSVARCHAR2 (10) identifies the archiving process relative to the main database of the status of the network server of the network operation issued by the writer process Even if the query is issued on the standby database:

ARC n

FOREGROUND

LGWR

REGISTERVARCHAR2 (3) indicates whether the archived redo log is registered (NO) in the remote destination control file (YES). If you have registered to archive redo logs, you can use the log application service. Date and time of FAIL_DATEDATE last error FAIL_SEQUENCENUMBER sequence number of archived redo log archived at last error FAIL_BLOCKNUMBER number of block number of archived redo log being archived at last error FAILURE_COUNTNUMBER target number of current consecutive archive operation failures MAX_FAILURENUMBER allows you to control the number of times the log transfer service attempts to re-establish communication and resume target failed archive operations ERRORVARCHAR2 displays error text ALTERNATEVARCHAR2 instead of destination If available, DEPENDENCYVARCHAR2 is reserved for future use of REMOTE_TEMPLATEVARCHAR2 to specify the template QUOTA_SIZENUMBER target quota for deriving the location to be recorded, representing in bytes the size of all archived redo logs that QUOTA_USEDNUMBER currently resides on the specified destination. MOUNTIDNUMBER instance mount identifier TRANSMIT_MODEVARCHAR2 (12) specifies the network transfer mode:

SYNCHRONOUS

PARALLELSYNC

ASYNCHRONOUS

ASYNC_BLOCKSNUMBER specifies the number of blocks for the ASYNC attribute AFFIRMVARCHAR2 (3) specifies that the disk I / O mode TYPEVARCHAR2 (7) represents the archive log destination, defining whether it is PUBLIC or PRIVATE. Only PUBLIC can use the ALTER SYSTEM SET or ALTER SESSION SET statement to modify the target at run time. By default, all archived log targets are PUBLIC. VALID_NOWVARCHAR2 (16) indicates whether the target is currently valid for archiving operations:

YES-the redo log type and database role for this target are valid for the current database

WRONG VALID_TYPE-the redo log type specified for this target is not valid for the current database role. For example, WRONG VALID_TYPE will return this value if it runs in the standby database role using the target specified by the VALID_FOR= (STANDBY_LOGFILE,STANDBY_ROLE) property but does not implement the standby redo log.

WRONG VALID_ROLE-the database role specified for this goal is not the one that the database is currently running. For example, VALID_ROLE returns WRONG when the target defined using the VALID_FOR= (ONLINE_LOGFILE,STANDBY_ROLE) property runs in the primary database role.

INACTIVE-destination is inactive, possibly due to an error

VALID_TYPEVARCHAR2 (15) redo log types or types that are valid for the target:

ONLINE_LOGFILE

STANDBY_LOGFILE

ALL_LOGFILES

VALID_ROLEVARCHAR2 (12) Database roles or roles that are valid for the target:

PRIMARY_ROLE

STANDBY_ROLE

ALL_ROLES

The DB_UNIQUE_NAMEVARCHAR2 (30) unique database name VERIFYVARCHAR2 (3) indicates whether the VERIFY attribute value on the parameter is LOG_ARCHIVE_DEST_ n validated (YES) or unverified (NO) COMPRESSIONVARCHAR2 (7) indicates whether the network compression is ENABLED or DISABLED. APPLIED_SCN foot 1NUMBER for the target corresponding to the physical or logical standby database, the last redone SCN applied. For the target corresponding to the snapshot standby database, the last redone SCN applied before converting to the snapshot standby database. This column is valid only for enabled and active standby database targets on the primary database or cascading standby database.

Explanation of v$archive_dest_status:

V $ARCHIVE_DEST_STATUS

V$ARCHIVE_DEST_STATUS displays runtime and configuration information for the archive redo log target. The information in this view does not persist for the duration of the instance shutdown.

The column data type describes the current status of the DEST_IDNUMBER identifying log archiving target parameters (1 to 31) DEST_NAMEVARCHAR2 (256) recording the archiving target parameter name STATUSVARCHAR2 (9) destination:

VALID-initialization and availability

INACTIVE-No destination information

DEFERRED-manually disabled by the user

ERROR-error during opening or copying

DISABLED-disable after error

BAD PARAM-error in the parameter

ALTERNATE-destination is in standby state

FULL-quota size that exceeds the destination

Type of TYPEVARCHAR2 (14) Archive destination database:

LOCAL-Local to master database

PHYSICAL-physical standby

CROSS-INSTANCE-Primary instance

LOGICAL-logical standby

SNAPSHOT-Snapshot standby database

DOWNSTREAM-Streams downstream capture database

DATABASE_MODEVARCHAR2 (15) Archive the current mode of the target database:

STARTED-instance started, not installed

MOUNTED-installed

MOUNTED-STANDBY-standby installed

OPEN-Open read / write

OPEN_READ-ONLY-Open as read-only

Current application mode of RECOVERY_MODEVARCHAR2 (23) file destination:

IDLE-managed restore is not activated

MANAGED-managed restore is activ

MANAGED REAL TIME APPLY-Log Application Service recovers redo data from the standby redo log while writing to the log, rather than from the archived redo log when a log switch occurs

LOGICAL REAL TIME APPLY-Real-time SQL application

LOGICAL APPLY-SQL Apply

PROTECTION_MODEVARCHAR2 (20) indicates whether the database is protected:

MAXIMUM PROTECTION

MAXIMUM AVAILABILITY

RESYNCHRONIZATION

MAXIMUM PERFORMANCE

UNPROTECTED

DESTINATIONVARCHAR2 specifies where to archive redo data STANDBY_LOGFILE_COUNTNUMBER represents the total number of standby redo logs created on the standby database STANDBY_LOGFILE_ACTIVENUMBER represents the total number of standby redo logs active on the standby database Contains primary database online redo log information ARCHIVED_THREAD#NUMBER identifies the latest archived redo log received on the target thread number ARCHIVED_SEQ#NUMBER identifies the latest archived redo log received on the target log sequence number APPLIED_THREAD#NUMBER identifies the latest application redo log received on the target thread number APPLIED_SEQ#NUMBER identifies the log order of the latest application redo log received on the target The column number ERRORVARCHAR2 displays the error text SRLVARCHAR2 (3) indicating whether to use the alternate redo log file (NO) DB_UNIQUE_NAMEVARCHAR2 (30) on the standby database (YES) to specify the unique database name of the current instance defined by DB_UNIQUE_NAME using the attribute of the LOG_ARCHIVE_DEST_ n parameter SYNCHRONIZATION_STATUSVARCHAR2 (22) the possible values for this column are as follows:

CHECK CONFIGURATION-cannot synchronize with this target because the database is not in data protection mode MAXIMUM PROTECTION or MAXIMUM PERFORMANCE data protection mode, or LOG_ARCHIVE_DEST_ n did not configure the parameters associated with this target using the SYNC and AFFIRM properties.

CHECK STANDBY REDO LOG-the standby redo log for this target is not configured correctly.

CHECK NETWORK-one or more instances of this database cannot send redo data to this destination.

DESTINATION HAS A GAP-this target lacks the redo data required to synchronize with this database.

OK-this target is synchronized with this database.

NOT AVAILABLE-synchronization status is not available.

See also: Oracle Data Guard Concepts and Management for more information about redo transport configuration

Possible values for SYNCHRONIZEDVARCHAR2 (3) are:

YES-this target is synchronized with the primary database.

NO-the target is not synchronized with the primary database.

UNKNOWN-unable to determine the synchronization status of this destination.

GAP_STATUSVARCHAR2 (24) redo gap status:

NO GAP-there is no redo gap at the destination.

LOG SWITCH GAP-the target has not received all redo from the previous log file.

RESOLVABLE GAP-Destination has a redo gap that can be resolved automatically by fetching the missing redo from this database.

UNRESOLVABLE GAP-the target has a redo gap that cannot be automatically resolved by extracting the lost redo from this database, and no other target can get redo from it.

LOCALLY UNRESOLVABLE GAP-Destination has a redo gap that cannot be resolved automatically by getting the missing redo from this database. The gap can be resolved by getting a lost redo from another destination.

Explanation of V$MANAGED_STANDBY:

V $MANAGED_STANDBY

V$MANAGED_STANDBY displays current state information for some Oracle database processes related to physical standby databases in the Data Guard environment. This view is not retained when the instance is closed.

The column data type describes the type of process whose information PROCESSVARCHAR2 (9) is reporting:

RFS-remote file server

MRP0-detached recovery server process

MR (fg)-Front desk resume meeting

ARCH-Archiving proc

FGRD

LGWR

RFS (FAL)

RFS (NEXP)

LNS-Network server process

Process identifier of the PIDNUMBER operating system process STATUSVARCHAR2 (12) current process status:

UNUSED-No active process

ALLOCATED-the process is active but not currently connected to the primary database

CONNECTED-establish a network connection to the master database

ATTACHED-the process actively connects and communicates with the master database

IDLE-No activity was performed by the process

ERROR-process failed

OPENING-the process is opening the archived redo log

CLOSING-the process has finished archiving and is closing the archived redo log

WRITING-the process is actively writing redo data to the archive redo log

RECEIVING-the process is receiving network traffic

ANNOUNCING-the process declares the existence of potentially related archive redo logs

REGISTERING-the process is registering the existence of completed dependent archive redo logs

WAIT_FOR_LOG-the process is waiting for the archived redo log to complete

WAIT_FOR_GAP-the process is waiting to resolve the archiving gap

APPLYING_LOG-the process is actively applying archived redo logs to the standby database

CLIENT_PROCESSVARCHAR2 (8) identifies the corresponding master database process:

Archival-Front desk (manual) archiving process (SQL)

ARCH-background ARC n process

LGWR-background LGWR process

CLIENT_PIDVARCHAR2 (40) process identifier of the operating system client process CLIENT_DBIDVARCHAR2 (40) Database identifier of the primary database GROUP#VARCHAR2 (40) alternate redo log group RESETLOG_IDNUMBERResetlogs archive redo log identifier THREAD#NUMBER archived redo log sequence number SEQUENCE#NUMBER archived redo log sequence number BLOCK#NUMBER last processed archive redo log block number BLOCKSNUMBER calculation (in 512 byte block) Expected final read count of write redo logs at one time or recovery process redo log latency interval (in minutes) for DELAY_MINSNUMBER archives total number of standby database agents for KNOWN_AGENTSNUMBER to process archived redo logs ACTIVE_AGENTSNUMBER

Number of standby database agents that actively process archived redo logs

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.