How to flashback primary database in standby configuration.

Solution
To Flashback primary database execute following steps :

1. Shutdown primary database .
SQL> SHUTDOWN IMMEDIATE
2. Start primary database in mount stage
SQL> STARTUP MOUNT
3. Flashback primary database to specified scn
SQL> FLASHBACK DATABASE TO SCN ;
4. Open primary database with reset logs.
SQL> ALTER DATABASE OPEN RESETLOGS;
5. Cancel media recovery on the standby database.
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
6. Check current_scn on the standby database, If flashback scn is greater then current_scn then skip next step (step 7).
SQL> SELECT CURRENT_SCN FROM V$DATABASE;
7. Flashback Standby database
SQL> FLASHBACK STANDBY DATABASE TO SCN ; (on standby database)
8. Start managed recovery on the standby database .
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;

Comments

Post a Comment

Popular posts from this blog

How to Configure Logging for EM 12c Management Agent

The goal of this article is to provide instruction on how to enable logging for the Enterprise Manager 12c Management Agent. ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- The logging properties for the agent are stored in $EMSTATE/sysman/config/emd.properties file, same as in 11.1. But the properties that control logging follow the log4j configuration syntax instead of the syntax supported by the 11.1 agent. To active changes to the logging parameters, you can use either of the emctl commands: emctl reload agent emctl setproperty agent Overview Agent logging entries look similar to the standard log4j logging, with the only significant difference being the prefix 'Logger.' that you will see on each line. For example: # logging properties Logger.log4j.appender.Rolling=org.apache.log4j.RollingFileAppender Logger.log
Read more

Stop Oracle Clusterware or Cluster Ready Services Processes

               Stop Oracle Clusterware or Cluster Ready Services Processes If you are modifying an Oracle Clusterware or Oracle Cluster Ready Services (CRS) installation, then shut down the following Oracle Database 10g services. Step to Stop RAC System. 1.        Shut down any processes in the Oracle home on each node that might be accessing a database; for example, shut down Oracle Enterprise Manager Database Control. 2.        Shut down all Oracle RAC instances on all nodes. To shut down all Oracle RAC instances for a database, enter the following command, where db_name is the name of the database: ORACLE_HOME \BIN\srvctl stop database -d <Database Name> 3.        Shut down all ASM instances on all nodes. To shut down an ASM instance, enter the following command, where node is the name of the node where the ASM instance is running: ORCALE_HOME \bin\srvctl stop asm -n node 4.        Stop all node applications on all nodes. To stop node applications running on a node, enter
Read more

Steps to HandlingBlock Corruption in Large Partitioned tables using EXCHANGE PARTITION method when no Backups available Metalink Note ID 1324772.1]

Goal of this DOC------- When a corruption is identified in a huge table partition block (e.g. ORA-01578), and we don't have backups (e.g. RMAN, OS level, Export, or any external resource) to recover the corruption, we can still try to salvage the remaining data in the table using 10231 event (with some possible data loss and inconsistency by skipping corrupted data blocks). One method to achieve this is: a) create a salvage table (using 10231 event) and insert data from corrupted partition (using CTAS or INSERT INTO SELECT...) : b) truncate the partition (using alter table truncate partition ) or DELETE the rows in partition c) Insert the data from salvage table to truncated corrupted partition (using INSERT INTO SELECT...) In above method, step c) will take significant amount of time depending on the number of rows in the partition i.e. if the table partition contains large number of rows. We can significantly reduce the time taken in step c) above by using EXCHANG
Read more