Column

Description

Instance ID

Instance ID

Database ID

Database ID calculated when the database is created and stored in all file headers

Name

Name of the database

Created (Date)

Creation date

Created (Time)

Creation time

Resetlogs change#

Change number at open resetlogs

Resetlogs (Date)

Date of open resetlogs

Resetlogs (Time)

Time of open resetlogs

Prior resetlogs change#

Change number at prior open resetlogs

Prior resetlogs (Date)

Date of prior open resetlogs

Prior resetlogs (Time)

Time of prior open resetlogs

Log mode

Archive log mode (NOARCHIVELOG or ARCHIVELOG)

Checkpoint change

Last SCN checkpointed

Archive change #

Last SCN archived

Controlfile type

Type of control file:

·        STANDBY – Indicates that the database is in standby mode

·        CLONE – indicates a clone database

·        BACKUP | CREATED – indicates the database is being recovered using a backup or created control file

·        CURRENT – the control file changes to this type following a standby database activate or database open after recovery

Controlfile created (date)

Date that control file was created

Controlfile created (time)

Time that control file was created

Controlfile sequence#

Control file sequence number incremented by control file transactions

Controlfile change#

Last change number in backup control file (null if the control file is not a backup)

Controlfile (date)

Last date in backup control file (null if the control file is not a backup)

Controlfile (time)

Last time in backup control file (null if the control file is not a backup)

Open Resetlogs

Indicates whether the next database open allows or requires the resetlogs option:

NOT ALLOWED, ALLOWED, or REQUIRED

Version (Date)

Version date

Version (Time)

Version time

Open mode

Open mode information

Protection mode

Protection mode currently in effect for the database:

·        MAXIMUM PROTECTION  Database is running in maximized protection mode

·        MAXIMUM AVAILABILITY – Database is running in maximized availability mode

·        RESYNCHRONIZATION – Database is running in resynchronization mode

·        MAXIMUM PERFORMANCE – database is running in maximized protection mode

·        UNPROTECTED – Database is unprotected (this normally occurs when the primary database is mounted and not open)

Remote archive

Value of the REMOTE_ARCHIVE_ENABLE initialization parameter

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

Indicates whether switchover is allowed:

·        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 – 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:

·        ALL – all users other than SYS are prevented from making changes to any data in the database.

·        STANDBY – all users other than SYS are prevented from making changes to any database object being maintained by logical standby.

NONE – normal security for all data in the database

Supplemental log data min

Makes sure that LogMiner has sufficient information to support chained rows and various storage arrangements such as cluster tables.

Supplemental log data pk

For all tables with a primary key, makes sure that all columns of the primary key are placed into the redo log whenever an update operation is performed.

Supplemental log data ui

For all tables with a unique key, makes sure that if any unique key columns are modified, all other columns belonging to the unique key are also placed into the redo log.

Force logging

Whether the database is under force logging mode (YES) or not (NO)

Column

Description

Instance ID

Instance ID

Facility

Facility that encountered the event. Possible values are:

·        CRASH RECOVERY

·        LTS

·        LAS

·        RMS

·        REMOTE FILE SERVER

·        FETCH ARCHIVE LOG

·        DATA GUARD

·        NETWORK SERVICES

Severity

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

Destination ID

Destination ID number of the event. If the event does not have a particular destination, the value is 0.

Message number

A chronologically increasing number giving each event a unique number

Error code

Error ID of the event

Callout

Indicates whether the current entry is a callout event (YES) or not (NO)

·        YES means that this event may require the DBA to perform some action. Examine the ERROR_CODE and MESSAGE columns for more information.

·        NO generally corresponds to an INFORMATIONAL or WARNING event, which does not require any action.

Date

Date of the event

Time

Time of the event

Message

Text message describing the event

Column

Description

Instance ID

Instance ID

Process

Type of process for which information is being reported:

·        ARCH – archiver process

·        RFS – remote file server

·        MRP0 – detached recovery server process

·        MR(fg) ­– foreground recovery session

Process ID

Operating system process identifier of process

Status

Current process status. Possible values are:

·        UNUSED – no active process

·        ALLOCATED – process is active but not currently connected to a primary database client

·        CONNECTED – network connection established to a primary database client

·        ATTACHED – process is actively attached and communicating to a primary database client

·        IDLE – process is not performing any activities

·        ERROR – process has failed

·        OPENING – process is opening the archived redo log

·        CLOSING – process has completed archival 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 actively 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 process 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 (min)

Archived redo log delay interval in minutes

Know 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