8.153 V$DATABASE
V$DATABASE
displays information about the database from the control file.
Column | Datatype | Description |
---|---|---|
|
|
Database identifier calculated when the database is created and stored in all file headers |
|
|
Name of the database |
|
|
Creation date of the database. If the control file was re-created using the |
|
|
System change number (SCN) at open resetlogs |
|
|
Timestamp of open resetlogs |
|
|
SCN at prior resetlogs |
|
|
Timestamp of prior resetlogs |
|
|
Archive log mode:
|
|
|
Last SCN checkpointed |
|
|
Database force archiving SCN. Any redo log with a start SCN below this will be forced to archive out. |
|
|
Type of control file:
|
|
|
Creation date of the control file |
|
|
Control file sequence number incremented by control file transactions |
|
|
Last SCN in backup control file; null if the control file is not a backup |
|
|
Last timestamp in backup control file; null if the control file is not a backup |
|
|
( |
|
|
Version time |
|
|
Open mode information:
|
|
|
Protection mode currently in effect for the database:
|
|
|
Aggregated protection mode currently in effect for the database:
Note: This column is an aggregation of the |
|
|
Value of the |
|
|
Number assigned to the database instantiation |
|
|
Number assigned to the database switchover |
|
|
Current role of the database:
|
|
|
Highest |
|
|
Status of the archive log compression ( |
|
|
Indicates whether switchover is allowed:
|
|
|
Data Guard broker information:
|
|
|
Protects data from being changed:
|
|
|
Ensures that LogMiner (and any products building on LogMiner technology) will have sufficient information to support chained rows and various storage arrangements such as cluster tables:
See Also: Oracle Database SQL
Language Reference for additional information about the |
|
|
For all tables with a primary key, indicates whether all columns of the primary key are placed into the redo log whenever an update is performed ( When a value of When a value of See Also: Oracle Database SQL
Language Reference for more information about the |
|
|
For all tables with a unique key, indicates whether all other columns belonging to the unique key are placed into the redo log if any of the unique key columns are modified ( When a value of When a value of See Also: Oracle Database SQL
Language Reference for more information about the |
|
|
Indicates the type of logging mode that is currently in force. The valid values and their meanings are:
|
|
|
Platform identification number of the database |
|
|
Platform name of the database |
|
|
The incarnation number to which all datafiles would be recovered by the |
|
|
Record number of the incarnation in |
|
|
Current SCN; null if the database is not currently open. For a standby database, it is the checkpoint SCN of the mounted physical standby database during media recovery and is always less than the last applied SCN tracked in |
|
|
Possible values are as follows:
|
|
|
For all tables with a foreign key, indicates whether all other columns belonging to the foreign key are placed into the redo log if any foreign key columns are modified ( When a value of When a value of See Also: Oracle Database SQL
Language Reference for more information about the |
|
|
For all columns, indicates whether all the fixed-length maximum size columns of that row are placed into the redo log ( When a value of When a value of See Also: Oracle Database SQL
Language Reference for more information about the |
|
|
Unique database name |
|
|
SCN at which a physical standby database became a primary database. This SCN is useful for converting a failed primary database into a physical standby database after a forced failover. See Also: Oracle Data Guard Concepts and Administration for more information about Oracle Data Guard. |
|
|
Displays the current fast-start failover mode. Possible values are:
|
|
|
Fast-start failover status:
See Also: Oracle Data Guard Broker for detailed descriptions of these values Note: If the value of this column is |
|
|
|
|
|
Time (in seconds) that the observer will attempt to reconnect with a disconnected primary before attempting fail-safe failover observer with the target standby |
|
|
Indicates whether the master observer is currently connected to the local database ( Note: This column is consistent throughout an Oracle RAC environment; that is, if the observer is connected to any instance, then all instances will show a value of |
|
|
Machine name that is currently hosting the master observer process, if fast-start failover is enabled. If fast-start failover is not enabled, this column returns a NULL string. |
|
|
Indicates whether the control file was implicitly converted from its original type during restore ( This column will be set to This column will change to |
|
|
For any Standby database (Physical, Logical, or Snapshot), this column will contain the If this standby has not received any current redo since last being started, then this column will be null. For a Primary database that had previously been a Standby, this column will contain the For a Primary database that has never been a Standby, this column will be null. |
|
|
Indicates whether additional information is logged in the redo log ( When a value of When a value of See Also: Oracle Data Guard Concepts and Administration for a list of Oracle-supplied packages that are procedurally replicated to a logical standby database |
|
|
Minimum |
|
|
Possible values are:
|
|
|
The ID of the container to which the data pertains. Possible values include:
|
|
|
Tasks remaining after an Oracle Data Guard role change. Possible values:
|
|
|
The database ID of the PDB |
|
|
Indicates the status of the force full database caching feature in the database. Possible values:
See Also: Oracle Database SQL
Language Reference for information about the |
|
|
Indicates whether the database is enabled for subset database replication ( |
|
|
Reserved for future use |
See Also:
"DBA_SUPPLEMENTAL_LOGGING" for more information about supplemental logging in a PDB