PrimaryLostWriteAction

The PrimaryLostWriteAction configuration property determines what action is taken if a primary or standby database detects that a lost write has occurred at the primary database.

Note:

The PrimaryLostWriteAction configuration property is available only in Oracle Database 11g Release 2 (11.2.0.4) and in Oracle Database 12c Release 1 (12.1.0.2) and later.

The possible actions are as follows:

  • CONTINUE - The primary database continues operating even if a primary or standby database detects that a lost write has occurred at the primary database. This is the default action.

  • SHUTDOWN - If a primary or standby database detects that a lost write has occurred at the primary database, then fast-start failover is disabled and the primary database performs a shutdown abort. Automatic failover will not occur.

  • FAILOVER - If fast-start failover is enabled in maximum performance mode, and the configuration is within the acceptable limit specified for the FastStartFailoverLagLimit property, then the observer initiates a failover.

  • FORCEFAILOVER - If fast-start failover is enabled (in either maximum performance or maximum availability mode), then the observer initiates a failover. This option results in a data loss failover.

For both the FAILOVER and FORCEFAILOVER options, if fast-start failover is disabled then no failover occurs, but the primary is shut down.

If a primary or standby database detects that a lost write has occurred at the primary database, fast-start failover is disabled if any of the following conditions are true:

  • PrimaryLostWriteAction is set to CONTINUE
  • PrimaryLostWriteAction is set to SHUTDOWN
  • PrimaryLostWriteAction is set to FAILOVER and protection mode is set to either maximum availability or maximum protection

Diagnostic information is written to the database alert and broker logs at the primary database and at the standby database where the lost write was detected.

If a lost write occurs at the primary database, then follow the guidelines in "Resolving ORA-752 or ORA-600 [3020] During Standby Recovery" in My Oracle Support Note 1265884.1 located at https://support.oracle.com.

Note:

The DB_LOST_WRITE_PROTECT database initialization parameter must be set to TYPICAL or FULL at the primary database and at each standby database in the configuration to ensure that lost primary writes can be detected by all standby databases in the configuration.

Category Description

Datatype

String

Valid values

CONTINUE, SHUTDOWN, FAILOVER, or FORCEFAILOVER

Broker default

CONTINUE

Imported?

No

Parameter class

Not applicable

Role

Primary and standby

Standby type

Not applicable

Corresponds to

Not applicable

Scope

Broker configuration

Cloud Control name

Not applicable