This discussion is archived
0 Replies Latest reply: Dec 5, 2013 8:31 AM by Jimbo RSS

Fast Start Failover has broken my Logical Standby and Flashback has not helped

Jimbo Explorer
Currently Being Moderated


I have a primary ( PRIMARYP ), a physical standby ( STANDBYP ) and a logical standby ( STANDBYL ).

 

I configured Fast Start Failover ( with STANDBYP as the target ) and started an Observer. I did a shutdown abort on my primary and the Fast Start Failover did make STANDBYP the primary. I was able to reinstate PRIMARYP as a physical standby.

 

However when I checked my broker config it gave for STANDBYL

ORA-16795: the standby database needs to be recreated

 

Strange I though, since I would have expected STANDBYL to survive ok given that the new primary, STANDBYP was a physical standby of PRIMARYP.

 

Not to worry I thought, I simply will flashback STANDBYL to the beginning of the day and SQL APPLY will reapply all the redo.

 

This is where the problem begins

 

I mount STANDBYL

 

RMAN> connect target /

connected to target database: STANDBYL (DBID=440422466, not open)

RMAN> flashback database to time "TO_DATE('05/12/13 09:30:00','DD-MM-YY HH24:MI:SS')";

Starting flashback at 05-DEC-13
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=11 device type=DISK


starting media recovery

archived log for thread 1 with sequence 24 is already on disk as file /home/app/oracle/fast_recovery_area/STANDBYL/archivelog/2013_12_04/o1_mf_1_24_99yqwog0_.arc
archived log for thread 1 with sequence 25 is already on disk as file /home/app/oracle/fast_recovery_area/STANDBYL/archivelog/2013_12_05/o1_mf_1_25_9b0mlyvr_.arc
media recovery complete, elapsed time: 00:00:04
Finished flashback at 05-DEC-13

RMAN> quit


Recovery Manager complete.
oraclel[STANDBYL]>dgmgrl
DGMGRL for Linux: Version 11.2.0.3.0 - Production

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

Welcome to DGMGRL, type "help" for information.
DGMGRL> connect sys/manager
Connected.
DGMGRL> shutdown;
ORA-01109: database not open

Database dismounted.
ORACLE instance shut down.
DGMGRL>
DGMGRL>
DGMGRL> startup;
ORACLE instance started.
Database mounted.
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open

 

 

ORA-01589 - that a nasty surprise ! I didn't think I would need to do anything with the log sequences after a flashback

Any ideas of what is going on ?

 

thanks,

Jim

Legend

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