FastStartFailoverLagGraceTime
The FastStartFailoverLagGraceTime configuration property
specifies the maximum amount of time (in seconds) that can pass before the lag limit
(FastStartFailoverLagLimit) is reached when the primary database
requests permission to move to the lagging state.
| Category | Description |
|---|---|
|
Broker default |
0 |
|
Configuration Type |
Data Guard only |
|
Datatype |
Integer |
|
Property Type |
Configurable |
|
Scope |
Broker configuration |
|
Valid Role |
Primary and standby |
|
Valid value |
Integral number of seconds. |
If the primary has been granted permission to move to the lagging state (by the observer or target standby) before the lag limit is reached, the primary will not stall. If the lag limit is reached, the primary will stall until either permission is granted or the fast-start failover threshold (specified by the FastStartFailoverThreshold property) has expired. This property is used when fast-start failover is enabled and the configuration is operating in maximum performance mode.
If the limit is reached, then a fast-start failover is not allowed. The lowest possible value is 5 seconds. A default value of 0 indicates that no lag limit grace period is in effect.
Oracle recommends that this property be set in environments that are prone to transport or apply lags caused by periodic, but heavy workloads in otherwise healthy environments. Oracle does not recommend setting this property in environments with poor network performance.
Note:
A side effect of this property is that the primary may go to the lagging state when it may have not been necessary because the database characteristics are such that the lag approaches but never exceeds the lag limit.