V$FAST_START_FAILOVER_CONFIG
V$FAST_START_FAILOVER_CONFIG displays configuration details about Oracle Data Guard fast-start failover.
| Column | Datatype | Description |
|---|---|---|
FAST_START_FAILOVER_MODE |
VARCHAR2(19) |
Displays the current fast-start failover mode. Possible values are:
|
STATUS |
VARCHAR2(22) |
Fast-start failover status:
See Also: Oracle Data Guard Broker Concepts for detailed descriptions of these values Note: If the value of this column is |
CURRENT_TARGET |
VARCHAR2(30) |
DB_UNIQUE_NAME of the standby that is the current fail-safe failover observer target standby for the Data Guard configuration |
THRESHOLD |
NUMBER |
Time (in seconds) that the observer will attempt to reconnect with a disconnected primary before attempting fail-safe failover observer with the target standby |
OBSERVER_PRESENT |
VARCHAR2(7) |
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 |
OBSERVER_HOST |
VARCHAR2(512) |
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. |
PING_INTERVAL |
NUMBER |
This value specifies how frequently the observer must ping the primary database (in milliseconds). See Also: Oracle Data Guard Broker Concepts for more information about the |
PING_RETRY |
NUMBER |
This value specifies the number of times that the observer retries a failed ping before it initiates a failover to the target standby database. See Also: Oracle Data Guard Broker Concepts for more information about the |
PROTECTION_MODE |
VARCHAR2(120) |
Protection mode for the fast-start failover configuration:
See Also: Oracle Data Guard Broker Concepts for more information about protection modes |
LAG_LIMIT |
NUMBER |
This value establishes an acceptable limit (in seconds) that the standby is allowed to fall behind the primary in terms of redo applied. See Also: Oracle Data Guard Broker Concepts for more information about the |
AUTO_REINSTATE |
VARCHAR2(5) |
This value specifies whether the former primary database is to be automatically reinstated if a fast-start failover was initiated because the primary database was either isolated or had crashed. See Also: Oracle Data Guard Broker Concepts for more information about the |
OBSERVER_RECONNECT |
NUMBER |
This value specifies how often (in seconds) the observer establishes a new connection to the primary database. See Also: Oracle Data Guard Broker Concepts for more information about the |
OBSERVER_OVERRIDE |
VARCHAR2(5) |
This value specifies whether an automatic failover is allowed to occur when the observer has lost connectivity to the primary. See Also: Oracle Data Guard Broker Concepts for more information about the |
SHUTDOWN_PRIMARY |
VARCHAR2(5) |
This value specifies whether the primary database should shut down under certain conditions. See Also: Oracle Data Guard Broker Concepts for more information about the |
LAG_TYPE |
VARCHAR2(4000) |
This value specifies the type of lag (apply lag or transport lag) that is used to specify the data loss threshold. See Also: Oracle Data Guard Broker Concepts for more information about the |
LAG_GRACE_TIME |
NUMBER |
This value specifies the maximum amount of time (in seconds) that can pass before the lag limit ( See Also: Oracle Data Guard Broker Concepts for more information about the |
CON_ID |
NUMBER |
The ID of the container to which the data pertains. Possible values include:
|
Note: This view is available starting with Oracle AI Database 26ai.