GROUP BY resetlogs_id, thread#, dest_id) a, (SELECT MAX (resetlogs_id) FROM gv$archived_log) TO_CHAR (a.last_applied_time, 'YYYY-MM-DD HH24:MI:SS') Start Recovery Process SQL>alter database recover managed standby database using current logfile disconnect Ĭheck Dataguard GAP On Primary SQL> SELECT a.resetlogs_id, Try Again Converting Snapshot Standby To Physical Standby SQL> alter database convert to physical standby Ĭheck Database Status-Role SQL> select a.status, b.database_role from v$instance a, v$database b Stop Second Instance srvctl stop instance -d -i ![]() ORA-38777: database must not be started in any other instance ![]() Only single node should be open otherwise below error occurs SQL> alter database convert to physical standby Īlter database convert to physical standby This process will take a long time, it is necessary to wait without interrupting the command used.Ģ. Mount Database srvctl start database -d -o mountĬonvert Snapshot Standby To Physical Standbyġ. Shutdown Database srvctl stop database -d Note: It is created automatically! SQL> select NAME,GUARANTEE_FLASHBACK_DATABASE from v$restore_point ĬONVERT SNAPSHOT STANDBY TO PHYSICAL STANDBY Set job_queue_processes Value As 0 (Optional) SQL> alter system set job_queue_processes=0 scope=both sid='*' Ĭheck Database Status-Role-Open Mode SQL> select a.status, b.database_role, b.open_mode from v$instance a, v$database b Open Database On Both Node SQL> alter database open Please note that all operation will be done on standby database.ĬONVERT PHYSICAL STANDBY TO SNAPSHOT STANDBYĬheck Database Status-Role-MRP SQL> select a.status, b.database_role, c.process from v$instance a, v$database b, v$managed_standby c where c.process like 'MRP%' Ĭancel Recovery Process SQL>alter database recover managed standby database cancel Ĭonvert Physical Standby To Snapshot Standby SQL> alter database convert to snapshot standby Using a single command changes made while read-write mode can be discarded and quickly resynchronize the standby with the primary database. ![]() At the same time, it maintains protection by continuing to receive data from the production database, archiving it for later use. A Snapshot Standby Database is a fully update-able standby database that is created by converting a physical standby database into a snapshot standby database.Ī snapshot Standby is open in the read-write mode and hence it is possible to process transactions independently of the primary database. Since Oracle 11g, there is a new feature in this area called : Snapshot standby database. Perform the following steps to activate the physical standby database as a production database and later resynchronize it with the primary database. When the database is flashed back, Data Guard automatically synchronizes the standby database with the primary database, without the need to re-create the physical standby database from a backup copy of the primary database. Using a combination of Data Guard, restore points, and Flashback Database, a physical standby database can be opened temporarily in read/write mode for development, reporting, or testing purposes, and then flashed back to a point in the past to be reverted back to a physical standby database. This article is to open the Standby database in read write mode for any reporting or testing and then move it back to standby database using the flashback technology.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |