TutorialDBA - Support | Training | Consultant

Make sure these parameters properly set on primary/standby database. standby_file_management=AUTO fal_client=Host DB name fal_server=Remote DB name local_listener=Host Listener name remote_listener=Remote Listener name standby_archive_dest=archive destination on standby database db_unique_name=should be different for primary and standby log_file_name_convert=‘primary destination’,’standby destination’ RAC services should be created using db_unique_name TNSNAMES.ORA entries:- STDBY =   (DESCRIPTION =     (ADDRESS_LIST =       (ADDRESS = (PROTOCOL = TCP)(HOST =   )(PORT =   ))       (ADDRESS = (PROTOCOL = TCP)(HOST =   )(PORT =   ))       (LOAD_BALANCE = yes)     )     (CONNECT_DATA =       (SERVICE_NAME = PROD)     )   ) PROD =   (DESCRIPTION =     (AD...

Enable fast_start failover you must have a working set of primary / standby databases. Both databases must be in flashback mode. Verify your Data Guard configuration with OEM.  You will need to review your Data Guard property. p1  my primary,  S1  my standby edit database p1 set LogXptMode='SYNC'; edit database p1 set FastStartFailoverTarget= 'S1' edit database S1set LogXptMode='SYNC'; edit database S1set FastStartFailoverTarget= 'p1' Edit Configuration Set Protection Mode As Maxavailability; Next, you need to start the fast_start failover observer  (using the Data Guard dgmgrl -silent "start observer" command.  You submit this dgmgrl command in the background with the nohup command so it is always running as a daemon process.: nohup dgmgrl -silent sys/*** "start observer" & note: it does not work if you connect with /. You will get DGM-16979 if you use / or if you use different passwords in st...