DBID

NUMBER

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

NAME

VARCHAR2(9)

Name of the database

CREATED

DATE

Creation date

RESETLOGS_CHANGE#

NUMBER

Change number at open resetlogs

RESETLOGS_TIME

DATE

Timestamp of open resetlogs

PRIOR_RESETLOGS_CHANGE#

NUMBER

Change number at prior resetlogs

PRIOR_RESETLOGS_TIME

DATE

Timestamp of prior resetlogs

LOG_MODE

VARCHAR2(12)

Archive log mode (NOARCHIVELOG or ARCHIVELOG)

CHECKPOINT_CHANGE#

NUMBER

Last SCN checkpointed

ARCHIVE_CHANGE#

NUMBER

Last SCN archived

CONTROLFILE_TYPE

VARCHAR2(7)

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

Control file creation timestamp

CONTROLFILE_SEQUENCE#

NUMBER

Control file sequence number incremented by control file transactions

CONTROLFILE_CHANGE#

NUMBER

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

CONTROLFILE_TIME

DATE

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

OPEN_RESETLOGS

VARCHAR2(11)

(NOT ALLOWED | ALLOWED | REQUIRED) Indicates whether the next database open allows or requires the resetlogs option

VERSION_TIME

DATE

Version time

OPEN_MODE

VARCHAR2(10)

Open mode information

PROTECTION_MODE

VARCHAR2(20)

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)

PROTECTION_LEVEL

VARCHAR2(20)

Aggregated 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)

Note:This column is an aggregation of the PROTECTION_MODE of all standby archivelog destinations.

REMOTE_ARCHIVE

VARCHAR2(8)

Value of the REMOTE_ARCHIVE_ENABLE initialization parameter

ACTIVATION#

NUMBER

Number assigned to the database instantiation

DATABASE_ROLE

VARCHAR2(16)

Current role of the database; either primary or standby

ARCHIVELOG_CHANGE#

NUMBER

Highest NEXT_CHANGE# (from the V$ARCHIVED_LOG view) for an archived log

SWITCHOVER_STATUS

VARCHAR2(18)

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 - Indicates that 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

VARCHAR2(7)

Protects data from being changed:

• ALL - Indicates all users other than SYS are prevented from making changes to any data in the database.
• STANDBY - Indicates all users other than SYS are prevented from making changes to any database object being maintained by logical standby.
• NONE - Indicates normal security for all data in the database.

SUPPLEMENTAL_LOG_DATA_MIN

VARCHAR2(3)

Ensures that LogMiner will have sufficient information to support chained rows and various storage arrangements such as cluster tables.

See Oracle9i SQL Reference for additional information about the ALTER DATABASE ADD SUPPLEMENTAL LOG DATA statement.

SUPPLEMENTAL_LOG_DATA_PK

VARCHAR2(3)

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

See Oracle9i SQL Reference for additional information about the ALTER DATABASE ADD SUPPLEMENTAL LOG DATA statement.

SUPPLEMENTAL_LOG_DATA_UI

VARCHAR2(3)

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

See Oracle9i SQL Reference for additional information about the ALTER DATABASE ADD SUPPLEMENTAL LOG DATA statement.

FORCE_LOGGING

VARCHAR2(3)

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