ORA-16693: requirements not met for enabling fast-start failover

1.Fast star failover mode is not enabled, even the logxptmode of both the standby and primary database ins async as per the protection mode requirement of maxprotection mode.

DGMGRL>  enable fast_start failover
Error: ORA-16693: requirements not met for enabling fast-start failover
Failed.
DGMGRL> show database orcl_us logxptmode
  LogXptMode = 'ASYNC'
DGMGRL> show database orcl_in logxptmode
  LogXptMode = 'ASYNC'
DGMGRL> show database 'orcl_us'

Database - orcl_us

  Role:              PHYSICAL STANDBY
  Intended State:    APPLY-ON
  Transport Lag:     0 seconds (computed 1 second ago)
  Apply Lag:         0 seconds (computed 1 second ago)
  Apply Rate:        83.00 KByte/s
  Real Time Query:   ON
  Instance(s):
    orcl2

Database Status:
SUCCESS

2.The dataguard logs message shows the flashback mode is not enabled in target standby

version check on database orcl_us detected stale metadata,
      requesting update from primary database
Creating process RSM0
07/28/2014 12:42:29
ORA-16693, FSFO requires the target standby to be in flashback mode

3.Enabled the flashback mode in standby database

DGMGRL> connect sys/sys123@orcl_us
Connected as SYSDBA.

DGMGRL> edit database 'orcl_us' set state='apply-off';
Succeeded.
DGMGRL>  sql "alter database flashback on";
Succeeded.
DGMGRL> enable fast_start failover
Enabled.
DGMGRL> edit database 'orcl_us' set state='apply-on';
Succeeded.
DGMGRL> show configuration

Configuration - broker1

  Protection Mode: MaxPerformance
  Databases:
  orcl_in - Primary database
    Warning: ORA-16819: fast-start failover observer not started

    orcl_us - (*) Physical standby database
      Warning: ORA-16819: fast-start failover observer not started

Fast-Start Failover: ENABLED

Configuration Status:
WARNING

4. Fast start failover is enabled, with a warning message of observer process is not started.

ORA-16647: could not start more than one observer

1. Error while starting the fsfo observer in new node.

[W000 07/20 22:41:58.95] Failed to start the Observer.
Error: ORA-16647: could not start more than one observer

2.Stop the observer and start the observer in the new node

DGMGRL> show fast_start failover

Fast-Start Failover: ENABLED

  Threshold:          30 seconds
  Target:             orcl_uk
  Observer:           ol6-112-rac1.localdomain
  Lag Limit:          20 seconds
  Shutdown Primary:   TRUE
  Auto-reinstate:     TRUE
  Observer Reconnect: (none)
  Observer Override:  FALSE

Configurable Failover Conditions
  Health Conditions:
    Corrupted Controlfile          YES
    Corrupted Dictionary           YES
    Inaccessible Logfile            NO
    Stuck Archiver                  NO
    Datafile Offline               YES

  Oracle Error Conditions:
    (none)

DGMGRL> stop observer
Done.
DGMGRL> show fast_start failover

Fast-Start Failover: ENABLED

  Threshold:          30 seconds
  Target:             orcl_uk
  Observer:           (none)
  Lag Limit:          20 seconds
  Shutdown Primary:   TRUE
  Auto-reinstate:     TRUE
  Observer Reconnect: (none)
  Observer Override:  FALSE

Configurable Failover Conditions
  Health Conditions:
    Corrupted Controlfile          YES
    Corrupted Dictionary           YES
    Inaccessible Logfile            NO
    Stuck Archiver                  NO
    Datafile Offline               YES

  Oracle Error Conditions:
    (none)

3.Start the observer process

]$ dgmgrl -logfile '/u03/app/oracle/diag/rdbms/orcl_uk/orcl2/trace/observer.log'  'sys/sys123@orcl_uk' 'start observer' &
[1] 12870
[oracle@ol6-112-rac2 trace]$ DGMGRL for Linux: Version 12.1.0.1.0 - 64bit Production

Copyright (c) 2000, 2012, Oracle. All rights reserved.

Welcome to DGMGRL, type "help" for information.
Connected as SYSDBA.

ORA-16693: requirements not met for enabling fast-start failover

1.Error while enabling the fast start failover

 dgmgrl -echo 'sys/sys123@orcl_uk'
DGMGRL for Linux: Version 12.1.0.1.0 - 64bit Production

Copyright (c) 2000, 2012, Oracle. All rights reserved.

Welcome to DGMGRL, type "help" for information.
Connected as SYSDBA.
DGMGRL> show configuration
show configuration

Configuration - broker1

  Protection Mode: MaxPerformance
  Databases:
  orcl_in - Primary database
    orcl_uk - Physical standby database

Fast-Start Failover: DISABLED

Configuration Status:
SUCCESS

DGMGRL> enable fast_start failover
enable fast_start failover
Error: ORA-16693: requirements not met for enabling fast-start failover

2.Checked the dataguard logfile for any more detail on the error message

/u03/app/oracle/diag/rdbms/orcl_in/orcl1/trace
[oracle@ol6-112-rac1 trace]$ tail -100f drcorcl1.log
.............
ENABLE FAST_START FAILOVER
MaxPerformance FSFO requires LogXptMode=ASYNC for primary and target standby databases, and no Far Sync is allowed between primary andtarget standby databases.
..................

3.Checked and changed the logxptmode from the sync to async, enabled the fsfo

dgmgrl sys/sys123@orcl_in
DGMGRL for Linux: Version 12.1.0.1.0 - 64bit Production

Copyright (c) 2000, 2012, Oracle. All rights reserved.

Welcome to DGMGRL, type "help" for information.
Connected as SYSDBA.
DGMGRL> show database 'orcl_in' logxptmode
  LogXptMode = 'sync'
DGMGRL> show database 'orcl_uk' logxptmode
  LogXptMode = 'sync'
DGMGRL> edit database 'orcl_uk' set property logxptmode='async';
Property "logxptmode" updated
DGMGRL> edit database 'orcl_in' set property logxptmode='async';
Property "logxptmode" updated
DGMGRL> enable fast_start failover
Enabled.