How many people out there actually use Flashback database?
My curiosity led me to discover that flashback database works great with data guard broker because there is to need to rebuild the standby database following a failover.
The following is a very simple scenario demonstrating flashback and data guard.
Perform graceful switchover to standby database – kite_o10gr2.
Since the operation is a graceful swithover, the standby database does not need to be rebuilt.
The standby database becomes primary and the primary becomes standby.
Perform failover to standby database – hawk_o10gr2.
Note: this should be executed at the current standby server.
The standby database is now disabled.
At this point, the standby database would need to be recreated.
Using flashback database saves the day as the standby database can be enable with a simple “reinstate” command.
Startup former primary database in mount mode.
The former primary database – kite_o10gr2 is still online.
Now go back and reinstate the standby database.
LOG_ARCHIVE_START parameter is deprecated in Oracle 10g.
Also, LOG_ARCHIVE_FORMAT must be in the format: %s,%t,%r.
I am currently running Oracle 9.2.0.8.0 SE on RHEL4 (Nahant Update 3).
Can’t find init file for Database “TIGGER”.
No parameter file exists in the directory $ORACLE_HOME/dbs, i.e. only orapwTIGGER and spfileTIGGER.ora exist.
Manually, start the database and create pfile from spfile.
dbstart requires pfile (initTIGGER.ora) even though spfile (spfileTIGGER.ora) already exists.