This discussion is archived
1 Reply Latest reply: Dec 5, 2013 9:11 AM by mseberg RSS

ORA-16829: fast-start failover configuration is lagging

Jimbo Explorer
Currently Being Moderated

I have configured my Fast Start Failover, enabled it ( and have the Observer running ). I have shutdown abort my Primary ( PRIMARYP ) and the system has failed over to my nominated physical standby ( STANDBYP ). I have reinstated PRIMARYP ( so it is now the physical standby ).


However I also had a logical standby ( STANDBYL ). When I tried to reinstate it I got


DGMGRL> reinstate database 'STANDBYL';
Reinstating database "STANDBYL", please wait...
Operation requires shutdown of instance "STANDBYL" on database "STANDBYL"
Shutting down instance "STANDBYL"...
Unable to connect to database
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor

Warning: You are no longer connected to ORACLE.

Please complete the following steps and reissue the REINSTATE command:
        shut down instance "STANDBYL" of database "STANDBYL"
        start up and mount instance "STANDBYL" of database "STANDBYL"


I shutdown STANDBYL and mounted the instance. I then ran from the new primary

DGMGRL> reinstate database 'STANDBYL';


ERROR: ORA-16795: the standby database needs to be recreated


DGMGRL> show configuration;

Configuration - broker1

  Protection Mode: MaxPerformance
    STANDBYP - Primary database
    PRIMARYP - (*) Physical standby database
    STANDBYL - Logical standby database (disabled)
      ORA-16795: the standby database needs to be re-created


Q1. What has happened to my Logical Standby and why ? I though a logical standby of a primary can stay a standby of a new primary, when that new primary was a physical standby of the old primary !


any help greatly appreciated



  • Correct Answers - 10 points
  • Helpful Answers - 5 points