ENABLE_FS_FAILOVER_CONDITION

The ENABLE_FS_FAILOVER_CONDITION function can be used to specify additional conditions for which a fast-start failover should be performed.

ENABLE_FS_FAILOVER_CONDITION Function

DBMS_DG.ENABLE_FS_FAILOVER_CONDITION (
     condition            IN VARCHAR2,
     severity             OUT BINARY_INTEGER)
RETURN BINARY_INTEGER;

Parameters

Parameter Description
condition A fast-start failover condition to enable.
severity The severity associated with the status returned by this function. Severity will be one of the following Oracle error numbers:
  • ORA-0: normal, successful completion
  • ORA-16501: The Oracle Data Guard broker operation failed.
  • ORA-16502: The Oracle Data Guard broker operation succeeded with warnings.

Usage Notes

  • This function returns a binary integer.

  • This function can also be used to enable initiating a fast-start failover when there is an ORA-240 error.
Health Condition Description
"Datafile Write Errors"

If fast-start failover is enabled and the Datafile Write Errors condition is specified, then a fast-start failover is initiated if write errors are encountered in any data files, including temp files, system data files, and undo files.

"Corrupted Controlfile"

Corrupted controlfile. This condition is enabled by default.

"Corrupted Dictionary" Dictionary corruption of a critical database object. This condition is enabled by default.
"Inaccessible Logfile" LGWR is unable to write to any member of a log group due to an I/O error.
"Stuck Archiver" Archiver is unable to archive a redo log because device is full or unavailable.

Return Values

Error Description
ORA-00000: normal, successful completion

Fast-start failover condition was enabled.

Other

The Data Guard broker was unable to enable the fast-start failover condition and the return value will indicate the reason for this failure.