advertisements
_____________________________________________________________________________________________________________________
Error Description
Even after setting up all parameters, the data guard enable fast_start failover gives following error.
DGMGRL> enable fast_start failover Error: ORA-16693: requirements not met for enabling fast-start failover Failed.
Make sure you have set all the required parameters for the fast_start failover using show fast_start failover.
Make sure your both primary and standby database are running flashback_on mode.
Solution in both primary & standby
SQL> Select flashback_on from gv$database; FLASHBACK_ON ------------------ NO NO SQL> show parameter flashb NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ db_flashback_retention_target integer 1440 SQL> ALTER SYSTEM SET DB_FLASHBACK_RETENTION_TARGET=2880; System altered. SQL> ALTER SYSTEM SET DB_FLASHBACK_RETENTION_TARGET=2880 scope=both sid='*'; System altered. SQL> alter database recover managed standby database cancel; Database altered. SQL> alter database flashback ON; Database altered. SQL> Select flashback_on from gv$database; FLASHBACK_ON ------------------ YES YES
Also check the data guard log file and you have set the LogXptMode mode properly as per your protection mode.
Content of drcCRMPROD1.log having an error like below.
When CRMPRODSTBY is a primary database and Fast-Start Failover (FSFO) is enabled in maximum performance protection mode, the redo transport mode for CRMPROD should be ASYNC, ORA-16693.
DGMGRL> edit database 'CRMPRODSTBY' set property 'LogXptMode'='async'; Property "LogXptMode" updated DGMGRL> edit database 'CRMPROD' set property 'LogXptMode'='async'; Property "LogXptMode" updated DGMGRL> enable fast_start failover Enabled. DGMGRL> show fast_start failover Fast-Start Failover: ENABLED Threshold: 180 seconds Target: ADMPRODSTBY Observer: (none) Lag Limit: 30 seconds (not in use) 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)s
_____________________________________________________________________________________________________________________
0 comments:
Post a Comment