{"id":37571,"date":"2022-04-05T09:38:01","date_gmt":"2022-04-05T09:38:01","guid":{"rendered":"https:\/\/dbtut.com\/?p=37571"},"modified":"2022-04-05T09:40:36","modified_gmt":"2022-04-05T09:40:36","slug":"switchover-from-primary-database-to-physical-standby-database-with-sqlplus-commands","status":"publish","type":"post","link":"https:\/\/dbtut.com\/index.php\/2022\/04\/05\/switchover-from-primary-database-to-physical-standby-database-with-sqlplus-commands\/","title":{"rendered":"Switchover from Primary Database to Physical Standby Database with SQLPLUS Commands"},"content":{"rendered":"

In today’s article, we will talk about Switchover from Primary Database to Physical Standby Database with SQLPLUS Commands.<\/p>\n

Before Switchover, there are a series of checks to see if the system is suitable for Switchover. Some of these controls are general and made for our entire Data Guard Environment, while others are specific to Switchover.<\/p>\n

PRE-CONTROLS<\/h4>\n

1.We check if the cluster services are running.<\/p>\n

[grid@primary1 ~]$ crs_stat -t\r\nName           Type           Target    State     Host        \r\n------------------------------------------------------------\r\nora.DATA.dg    ora....up.type ONLINE    ONLINE    primary1    \r\nora.FRA.dg     ora....up.type ONLINE    ONLINE    primary1    \r\nora....ER.lsnr ora....er.type ONLINE    ONLINE    primary1    \r\nora....N1.lsnr ora....er.type ONLINE    ONLINE    primary2    \r\nora....N2.lsnr ora....er.type ONLINE    ONLINE    primary1    \r\nora....N3.lsnr ora....er.type ONLINE    ONLINE    primary1    \r\nora....VOTE.dg ora....up.type ONLINE    ONLINE    primary1    \r\nora.asm        ora.asm.type   ONLINE    ONLINE    primary1    \r\nora.cvu        ora.cvu.type   ONLINE    ONLINE    primary1    \r\nora.gsd        ora.gsd.type   OFFLINE   OFFLINE               \r\nora....network ora....rk.type ONLINE    ONLINE    primary1    \r\nora.oc4j       ora.oc4j.type  ONLINE    ONLINE    primary1    \r\nora.ons        ora.ons.type   ONLINE    ONLINE    primary1    \r\nora.primary.db ora....se.type ONLINE    ONLINE    primary1    \r\nora....SM1.asm application    ONLINE    ONLINE    primary1    \r\nora....Y1.lsnr application    ONLINE    ONLINE    primary1    \r\nora....ry1.gsd application    OFFLINE   OFFLINE               \r\nora....ry1.ons application    ONLINE    ONLINE    primary1    \r\nora....ry1.vip ora....t1.type ONLINE    ONLINE    primary1    \r\nora....SM2.asm application    ONLINE    ONLINE    primary2    \r\nora....Y2.lsnr application    ONLINE    ONLINE    primary2    \r\nora....ry2.gsd application    OFFLINE   OFFLINE               \r\nora....ry2.ons application    ONLINE    ONLINE    primary2    \r\nora....ry2.vip ora....t1.type ONLINE    ONLINE    primary2    \r\nora....ry.acfs ora....fs.type ONLINE    ONLINE    primary1    \r\nora.scan1.vip  ora....ip.type ONLINE    ONLINE    primary2    \r\nora.scan2.vip  ora....ip.type ONLINE    ONLINE    primary1    \r\nora.scan3.vip  ora....ip.type ONLINE    ONLINE    primary1<\/pre>\n
[grid@standby1 ~]$ crs_stat -t\r\nName           Type           Target    State     Host        \r\n------------------------------------------------------------\r\nora.DATA.dg    ora....up.type ONLINE    ONLINE    standby1    \r\nora.FRA.dg     ora....up.type ONLINE    ONLINE    standby1    \r\nora....ER.lsnr ora....er.type ONLINE    ONLINE    standby1    \r\nora....N1.lsnr ora....er.type ONLINE    ONLINE    standby1    \r\nora....N2.lsnr ora....er.type ONLINE    ONLINE    standby2    \r\nora....N3.lsnr ora....er.type ONLINE    ONLINE    standby2    \r\nora....VOTE.dg ora....up.type ONLINE    ONLINE    standby1    \r\nora.asm        ora.asm.type   ONLINE    ONLINE    standby1    \r\nora.cvu        ora.cvu.type   ONLINE    ONLINE    standby2    \r\nora.gsd        ora.gsd.type   OFFLINE   OFFLINE               \r\nora....network ora....rk.type ONLINE    ONLINE    standby1    \r\nora.oc4j       ora.oc4j.type  ONLINE    ONLINE    standby2    \r\nora.ons        ora.ons.type   ONLINE    ONLINE    standby1    \r\nora....ry.acfs ora....fs.type ONLINE    ONLINE    standby1    \r\nora.scan1.vip  ora....ip.type ONLINE    ONLINE    standby1    \r\nora.scan2.vip  ora....ip.type ONLINE    ONLINE    standby2    \r\nora.scan3.vip  ora....ip.type ONLINE    ONLINE    standby2    \r\nora.standby.db ora....se.type ONLINE    ONLINE    standby1    \r\nora....SM1.asm application    ONLINE    ONLINE    standby1    \r\nora....Y1.lsnr application    ONLINE    ONLINE    standby1    \r\nora....by1.gsd application    OFFLINE   OFFLINE               \r\nora....by1.ons application    ONLINE    ONLINE    standby1    \r\nora....by1.vip ora....t1.type ONLINE    ONLINE    standby1    \r\nora....SM2.asm application    ONLINE    ONLINE    standby2    \r\nora....Y2.lsnr application    ONLINE    ONLINE    standby2    \r\nora....by2.gsd application    OFFLINE   OFFLINE               \r\nora....by2.ons application    ONLINE    ONLINE    standby2    \r\nora....by2.vip ora....t1.type ONLINE    ONLINE    standby2<\/pre>\n
[grid@logical1 ~]$ crs_stat -t\r\nName           Type           Target    State     Host        \r\n------------------------------------------------------------\r\nora.DATA.dg    ora....up.type ONLINE    ONLINE    logical1    \r\nora.FRA.dg     ora....up.type ONLINE    ONLINE    logical1    \r\nora....ER.lsnr ora....er.type ONLINE    ONLINE    logical1    \r\nora....N1.lsnr ora....er.type ONLINE    ONLINE    logical1    \r\nora....N2.lsnr ora....er.type ONLINE    ONLINE    logical2    \r\nora....N3.lsnr ora....er.type ONLINE    ONLINE    logical2    \r\nora....VOTE.dg ora....up.type ONLINE    ONLINE    logical1    \r\nora.asm        ora.asm.type   ONLINE    ONLINE    logical1    \r\nora.cvu        ora.cvu.type   ONLINE    ONLINE    logical2    \r\nora.gsd        ora.gsd.type   OFFLINE   OFFLINE               \r\nora.logical.db ora....se.type ONLINE    ONLINE    logical1    \r\nora....SM1.asm application    ONLINE    ONLINE    logical1    \r\nora....L1.lsnr application    ONLINE    ONLINE    logical1    \r\nora....al1.gsd application    OFFLINE   OFFLINE               \r\nora....al1.ons application    ONLINE    ONLINE    logical1    \r\nora....al1.vip ora....t1.type ONLINE    ONLINE    logical1    \r\nora....SM2.asm application    ONLINE    ONLINE    logical2    \r\nora....L2.lsnr application    ONLINE    ONLINE    logical2    \r\nora....al2.gsd application    OFFLINE   OFFLINE               \r\nora....al2.ons application    ONLINE    ONLINE    logical2    \r\nora....al2.vip ora....t1.type ONLINE    ONLINE    logical2    \r\nora....network ora....rk.type ONLINE    ONLINE    logical1    \r\nora.oc4j       ora.oc4j.type  ONLINE    ONLINE    logical2    \r\nora.ons        ora.ons.type   ONLINE    ONLINE    logical1    \r\nora....ry.acfs ora....fs.type ONLINE    ONLINE    logical1    \r\nora.scan1.vip  ora....ip.type ONLINE    ONLINE    logical1    \r\nora.scan2.vip  ora....ip.type ONLINE    ONLINE    logical2    \r\nora.scan3.vip  ora....ip.type ONLINE    ONLINE    logical2    \r\n<\/pre>\n
2.We check the status of instances.<\/p>\n
[grid@primary1 ~]$ srvctl status database -d primary\r\nInstance primary1 is running on node primary1\r\nInstance primary2 is running on node primary2\r\n<\/pre>\n
[grid@standby1 ~]$ srvctl status database -d standby\r\nInstance primary1 is running on node standby1\r\nInstance primary2 is running on node standby2\r\n<\/pre>\n
[grid@logical1 ~]$ srvctl status database -d logical\r\nInstance primary1 is running on node logical1\r\nInstance primary2 is running on node logical2\r\n<\/pre>\n
3. We check if the Listeners are working properly. For this, we login to all instances from a third party client.<\/p>\n
\n
\n
\n
\"\"<\/p>\n<\/div>\n<\/div>\n<\/div>\n
4. We are trying to connect to the new Physical Standby DB and Logical Standby DB from the new Primary DB, which will be after the switchover.<\/p>\n
[oracle@standby1 ~]$ sqlplus sys\/Passw0rd4@PRIMARY1 as sysdba\r\n\r\nSQL*Plus: Release 11.2.0.4.0 Production on Thu Jan 19 11:18:35 2017\r\n\r\nCopyright (c) 1982, 2013, Oracle.  All rights reserved.\r\n\r\n\r\nConnected to:\r\nOracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production\r\nWith the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,\r\nData Mining and Real Application Testing options\r\n\r\n[Physical-1] SQL> show parameter name\r\n\r\nNAME                                 TYPE        VALUE\r\n------------------------------------ ----------- ------------------------------\r\ncell_offloadgroup_name               string\r\ndb_file_name_convert                 string      standby, primary\r\ndb_name                              string      primary\r\ndb_unique_name                       string      primary\r\nglobal_names                         boolean     FALSE\r\ninstance_name                        string      primary2\r\nlock_name_space                      string\r\nlog_file_name_convert                string      standby, primary\r\nprocessor_group_name                 string\r\nservice_names                        string      primary\r\n<\/pre>\n
[oracle@standby1 ~]$ sqlplus sys\/Passw0rd4@PRIMARY2 as sysdba\r\n\r\nSQL*Plus: Release 11.2.0.4.0 Production on Thu Jan 19 11:19:14 2017\r\n\r\nCopyright (c) 1982, 2013, Oracle.  All rights reserved.\r\n\r\n\r\nConnected to:\r\nOracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production\r\nWith the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,\r\nData Mining and Real Application Testing options\r\n\r\n[Physical-1] SQL> show parameter name\r\n\r\nNAME                                 TYPE        VALUE\r\n------------------------------------ ----------- ------------------------------\r\ncell_offloadgroup_name               string\r\ndb_file_name_convert                 string      standby, primary\r\ndb_name                              string      primary\r\ndb_unique_name                       string      primary\r\nglobal_names                         boolean     FALSE\r\ninstance_name                        string      primary2\r\nlock_name_space                      string\r\nlog_file_name_convert                string      standby, primary\r\nprocessor_group_name                 string\r\nservice_names                        string      primary\r\n<\/pre>\n
[oracle@standby1 ~]$ sqlplus sys\/Passw0rd4@PRIMARY as sysdba\r\n\r\nSQL*Plus: Release 11.2.0.4.0 Production on Thu Jan 19 11:19:38 2017\r\n\r\nCopyright (c) 1982, 2013, Oracle.  All rights reserved.\r\n\r\n\r\nConnected to:\r\nOracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production\r\nWith the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,\r\nData Mining and Real Application Testing options\r\n\r\n[Physical-1] SQL> show parameter name\r\n\r\nNAME                                 TYPE        VALUE\r\n------------------------------------ ----------- ------------------------------\r\ncell_offloadgroup_name               string\r\ndb_file_name_convert                 string      standby, primary\r\ndb_name                              string      primary\r\ndb_unique_name                       string      primary\r\nglobal_names                         boolean     FALSE\r\ninstance_name                        string      primary2\r\nlock_name_space                      string\r\nlog_file_name_convert                string      standby, primary\r\nprocessor_group_name                 string\r\nservice_names                        string      primary\r\n<\/pre>\n
[oracle@standby1 ~]$ sqlplus sys\/Passw0rd4@LOGICAL as sysdba\r\n\r\nSQL*Plus: Release 11.2.0.4.0 Production on Thu Jan 19 11:20:03 2017\r\n\r\nCopyright (c) 1982, 2013, Oracle.  All rights reserved.\r\n\r\n\r\nConnected to:\r\nOracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production\r\nWith the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,\r\nData Mining and Real Application Testing options\r\n\r\n[Physical-1] SQL> show parameter name\r\n\r\nNAME                                 TYPE        VALUE\r\n------------------------------------ ----------- ------------------------------\r\ncell_offloadgroup_name               string\r\ndb_file_name_convert                 string      logical, primary\r\ndb_name                              string      logical\r\ndb_unique_name                       string      logical\r\nglobal_names                         boolean     FALSE\r\ninstance_name                        string      primary1\r\nlock_name_space                      string\r\nlog_file_name_convert                string      primary, logical\r\nprocessor_group_name                 string\r\nservice_names                        string      logical\r\n<\/pre>\n
[oracle@standby1 ~]$ sqlplus sys\/Passw0rd4@LOGICAL1 as sysdba\r\n\r\nSQL*Plus: Release 11.2.0.4.0 Production on Thu Jan 19 11:20:27 2017\r\n\r\nCopyright (c) 1982, 2013, Oracle.  All rights reserved.\r\n\r\n\r\nConnected to:\r\nOracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production\r\nWith the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,\r\nData Mining and Real Application Testing options\r\n\r\n[Physical-1] SQL> show parameter name\r\n\r\nNAME                                 TYPE        VALUE\r\n------------------------------------ ----------- ------------------------------\r\ncell_offloadgroup_name               string\r\ndb_file_name_convert                 string      logical, primary\r\ndb_name                              string      logical\r\ndb_unique_name                       string      logical\r\nglobal_names                         boolean     FALSE\r\ninstance_name                        string      primary1\r\nlock_name_space                      string\r\nlog_file_name_convert                string      primary, logical\r\nprocessor_group_name                 string\r\nservice_names                        string      logical\r\n<\/pre>\n
[oracle@standby1 ~]$ sqlplus sys\/Passw0rd4@LOGICAL2 as sysdba\r\n\r\nSQL*Plus: Release 11.2.0.4.0 Production on Thu Jan 19 11:20:48 2017\r\n\r\nCopyright (c) 1982, 2013, Oracle.  All rights reserved.\r\n\r\n\r\nConnected to:\r\nOracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production\r\nWith the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,\r\nData Mining and Real Application Testing options\r\n\r\n[Physical-1] SQL> show parameter name\r\n\r\nNAME                                 TYPE        VALUE\r\n------------------------------------ ----------- ------------------------------\r\ncell_offloadgroup_name               string\r\ndb_file_name_convert                 string      logical, primary\r\ndb_name                              string      logical\r\ndb_unique_name                       string      logical\r\nglobal_names                         boolean     FALSE\r\ninstance_name                        string      primary2\r\nlock_name_space                      string\r\nlog_file_name_convert                string      primary, logical\r\nprocessor_group_name                 string\r\nservice_names                        string      logical\r\n<\/pre>\n
In the same way, we try one by one from Standby-2.<\/p>\n
5. We are questioning which Standby Online Redo Logs are used or not, and their status.<\/p>\n
[Primary-1] SQL> set linesize 9000\r\n[Primary-1] SQL> column dbid format a15\r\n[Primary-1] SQL> SELECT group#, thread#, sequence#, dbid, archived, status FROM v$standby_log;\r\n\r\n    GROUP#    THREAD#  SEQUENCE# DBID            ARC STATUS\r\n---------- ---------- ---------- --------------- --- ----------\r\n         5          1          0 UNASSIGNED      YES UNASSIGNED\r\n         6          1          0 UNASSIGNED      YES UNASSIGNED\r\n         7          1          0 UNASSIGNED      YES UNASSIGNED\r\n         8          2          0 UNASSIGNED      YES UNASSIGNED\r\n         9          2          0 UNASSIGNED      YES UNASSIGNED\r\n        10          2          0 UNASSIGNED      YES UNASSIGNED\r\n\r\n6 rows selected.\r\n<\/pre>\n
[Physical-1] SQL> set linesize 9000\r\n[Physical-1] SQL> column dbid format a15\r\n[Physical-1] SQL> SELECT group#, thread#, sequence#, dbid, archived, status FROM v$standby_log;\r\n\r\n    GROUP#    THREAD#  SEQUENCE# DBID            ARC STATUS\r\n---------- ---------- ---------- --------------- --- ----------\r\n         5          1          0 UNASSIGNED      NO  UNASSIGNED\r\n         6          1        673 1769705496      YES ACTIVE\r\n         7          1          0 UNASSIGNED      YES UNASSIGNED\r\n         8          2          0 UNASSIGNED      NO  UNASSIGNED\r\n         9          2        422 1769705496      YES ACTIVE\r\n        10          2          0 UNASSIGNED      YES UNASSIGNED\r\n\r\n6 rows selected.\r\n<\/pre>\n
[Logical-1] SQL> set linesize 9000\r\n[Logical-1] SQL> column dbid format a15\r\n[Logical-1] SQL> SELECT group#, thread#, sequence#, dbid, archived, status FROM v$standby_log;\r\n\r\n    GROUP#    THREAD#  SEQUENCE# DBID            ARC STATUS\r\n---------- ---------- ---------- --------------- --- ----------\r\n         5          1          0 UNASSIGNED      NO  UNASSIGNED\r\n         6          1        673 1769705496      YES ACTIVE\r\n         7          1          0 UNASSIGNED      NO  UNASSIGNED\r\n         8          2        422 1769705496      YES ACTIVE\r\n         9          2          0 UNASSIGNED      NO  UNASSIGNED\r\n        10          2          0 UNASSIGNED      NO  UNASSIGNED\r\n\r\n6 rows selected.\r\n<\/pre>\n
Combinations of ARCHIVED and STATUS columns here mean the following.<\/p>\n
ARC\u00a0\u00a0\u00a0 STATUS<\/p>\n\n\n\n\n\n\n
NO\u00a0\u00a0\u00a0\u00a0\u00a0 UNASSIGNED<\/td>\nStandby Redo Log means archived and suitable for reuse.<\/td>\n<\/tr>\n
YES\u00a0\u00a0\u00a0\u00a0 UNASSIGNED<\/td>\nStandby Redo Log means it has never been used and is ready to use.<\/td>\n<\/tr>\n
NO\u00a0\u00a0\u00a0\u00a0 ACTIVE<\/td>\nIndicates that writing to the Standby Redo Log has finished and is waiting for the Standby Redo Log to be archived.<\/td>\n<\/tr>\n
YES\u00a0\u00a0\u00a0 ACTIVE<\/td>\nIndicates that the Standby Redo Log is actively used and has not been archived yet.<\/p>\n
\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
6. We check the Role, Type and suitability of archive destinations. This process is important for the archives to go to the Standby Database properly after Switchover.<\/p>\n
[Primary-1] SQL> SELECT dest_id,valid_type,valid_role,valid_now FROM v$archive_dest;\r\n\r\n   DEST_ID VALID_TYPE      VALID_ROLE   VALID_NOW\r\n---------- --------------- ------------ ----------------\r\n         1 ALL_LOGFILES    ALL_ROLES    YES\r\n         2 ALL_LOGFILES    PRIMARY_ROLE YES\r\n         3 ALL_LOGFILES    PRIMARY_ROLE YES\r\n<\/pre>\n
[Physical-1] SQL> SELECT dest_id,valid_type,valid_role,valid_now FROM v$archive_dest;\r\n\r\n   DEST_ID VALID_TYPE      VALID_ROLE   VALID_NOW\r\n---------- --------------- ------------ ----------------\r\n         1 ALL_LOGFILES    ALL_ROLES    YES\r\n         2 ALL_LOGFILES    PRIMARY_ROLE WRONG VALID_ROLE\r\n         3 ALL_LOGFILES    PRIMARY_ROLE WRONG VALID_ROLE\r\n<\/pre>\n
[Logical-1] SQL> SELECT dest_id,valid_type,valid_role,valid_now FROM v$archive_dest;\r\n\r\n   DEST_ID VALID_TYPE      VALID_ROLE   VALID_NOW\r\n---------- --------------- ------------ ----------------\r\n         1 ALL_LOGFILES    ALL_ROLES    YES\r\n<\/pre>\n
7. We check whether there is an error in the archive destinations.<\/p>\n
[Primary-1] SQL> column destination format a30\r\n[Primary-1] SQL> column error format a20\r\n[Primary-1] SQL> set linesize 9000\r\n[Primary-1] SQL> SELECT DEST_ID, STATUS, DESTINATION, ERROR FROM V$ARCHIVE_DEST WHERE DEST_ID <=5;\r\n\r\n   DEST_ID STATUS    DESTINATION                    ERROR\r\n---------- --------- ------------------------------ --------------------\r\n         1 VALID     USE_DB_RECOVERY_FILE_DEST\r\n         2 VALID     standby\r\n         3 VALID     logical\r\n         4 INACTIVE\r\n         5 INACTIVE\r\n<\/pre>\n
[Physical-1] SQL> column destination format a30\r\n[Physical-1] SQL> column error format a20\r\n[Physical-1] SQL> set linesize 9000\r\n[Physical-1] SQL> SELECT DEST_ID, STATUS, DESTINATION, ERROR FROM V$ARCHIVE_DEST WHERE DEST_ID <=5;\r\n\r\n   DEST_ID STATUS    DESTINATION                    ERROR\r\n---------- --------- ------------------------------ --------------------\r\n         1 VALID     USE_DB_RECOVERY_FILE_DEST\r\n         2 VALID     primary\r\n         3 VALID     logical\r\n         4 INACTIVE\r\n         5 INACTIVE\r\n<\/pre>\n
[Logical-1] SQL> column destination format a30\r\n[Logical-1] SQL> column error format a20\r\n[Logical-1] SQL> set linesize 9000\r\n[Logical-1] SQL> SELECT DEST_ID, STATUS, DESTINATION, ERROR FROM V$ARCHIVE_DEST WHERE DEST_ID <=5;\r\n\r\n   DEST_ID STATUS    DESTINATION                    ERROR\r\n---------- --------- ------------------------------ --------------------\r\n         1 VALID     USE_DB_RECOVERY_FILE_DEST\r\n         2 INACTIVE\r\n         3 INACTIVE\r\n         4 INACTIVE\r\n         5 INACTIVE\r\n<\/pre>\n
8. We check for Redo Transport and Redo Apply LAG.<\/p>\n
[Physical-1] SQL> set linesize 9000\r\n[Physical-1] SQL> column name format a25\r\n[Physical-1] SQL> column value format a20\r\n[Physical-1] SQL> column time_computed format a25\r\n[Physical-1] SQL> SELECT name, value, time_computed FROM v$dataguard_stats;\r\n\r\nNAME                      VALUE                TIME_COMPUTED\r\n------------------------- -------------------- -------------------------\r\ntransport lag             +00 00:00:00         01\/19\/2017 13:58:52\r\napply lag                 +00 00:00:00         01\/19\/2017 13:58:52\r\napply finish time         +00 00:00:00.000     01\/19\/2017 13:58:52\r\nestimated startup time    27                   01\/19\/2017 13:58:52\r\n<\/pre>\n
[Logical-1] SQL> set linesize 9000\r\n[Logical-1] SQL> column name format a25\r\n[Logical-1] SQL> column value format a20\r\n[Logical-1] SQL> column time_computed format a25\r\n[Logical-1] SQL> SELECT name, value, time_computed FROM v$dataguard_stats;\r\n\r\nNAME                      VALUE                TIME_COMPUTED\r\n------------------------- -------------------- -------------------------\r\ntransport lag             +00 00:00:00         01\/19\/2017 13:58:52\r\napply lag                 +00 00:00:00         01\/19\/2017 13:58:52\r\napply finish time         +00 00:00:00.000     01\/19\/2017 13:58:52\r\nestimated startup time    25                   01\/19\/2017 13:58:52\r\n<\/pre>\n
9. We learn whether there are ERROR and GAP in Redo Transport transactions.<\/p>\n
[Primary-1] SQL> column DEST_NAME format a20\r\n[Primary-1] SQL> column error format a15\r\n[Primary-1] SQL> SELECT DEST_NAME, STATUS, GAP_STATUS, ERROR FROM V$ARCHIVE_DEST_STATUS;\r\n\r\nDEST_NAME            STATUS    GAP_STATUS               ERROR\r\n-------------------- --------- ------------------------ ---------------\r\nLOG_ARCHIVE_DEST_1   VALID\r\nLOG_ARCHIVE_DEST_2   VALID     NO GAP\r\nLOG_ARCHIVE_DEST_3   VALID     NO GAP\r\n<\/pre>\n
10. We check whether the archives created in the primary are processed in all standbys.<\/p>\n
[Primary-1] SQL> alter system switch logfile;\r\n\r\nSystem altered.\r\n\r\n[Primary-1] SQL> alter system switch logfile;\r\n\r\nSystem altered.\r\n<\/pre>\n
[Primary-2] SQL> alter system switch logfile;\r\n\r\nSystem altered.\r\n\r\n[Primary-2] SQL> alter system switch logfile; \r\n\r\nSystem altered.\r\n<\/pre>\n
[Primary-1] SQL>  select max(sequence#),thread# from v$archived_log group by thread#;\r\n\r\nMAX(SEQUENCE#)    THREAD#\r\n-------------- ----------\r\n           675          1\r\n           424          2\r\n<\/pre>\n
[Physical-1] SQL>  select max(sequence#),thread# from v$archived_log group by thread#;\r\n\r\nMAX(SEQUENCE#)    THREAD#\r\n-------------- ----------\r\n           675          1\r\n           424          2\r\n<\/pre>\n
[Logical-1] SQL> SELECT max(sequence#),thread#,applied FROM dba_logstdby_log group by thread#, applied;\r\n\r\nMAX(SEQUENCE#)    THREAD# APPLIED\r\n-------------- ---------- --------\r\n           675          1 YES\r\n           424          2 YES\r\n<\/pre>\n
11. We check if the Tempfiles are on the Primary and Standby sides.<\/p>\n
[Primary-1] SQL> column name format a45\r\n[Primary-1] SQL> select name from v$tempfile;\r\n\r\nNAME\r\n---------------------------------------------\r\n+DATA\/primary\/tempfile\/temp.263.932222817\r\n<\/pre>\n
[Physical-1] SQL> column name format a45\r\n[Physical-1] SQL> select name from v$tempfile;\r\n\r\nNAME\r\n---------------------------------------------\r\n+DATA\/standby\/tempfile\/temp.276.932286709<\/pre>\n
[Logical-1] SQL> column name format a45\r\n[Logical-1] SQL> select name from v$tempfile;\r\n\r\nNAME\r\n---------------------------------------------\r\n+DATA\/logical\/tempfile\/temp.280.932895541<\/pre>\n
12. We check the LOG_ARCHIVE_DEST_n parameters so that the archives can be moved correctly after the switchover.<\/p>\n
After this check, if the locations where the new Primary Database will send archives are missing after Switchover, it is defined with the ALTER SYSTEM SET LOG_ARCHIVE_DEST_2=’\u2026’ command.<\/p>\n
[Primary-1] SQL> column name format a30 \r\n[Primary-1] SQL> column value format a94\r\n[Primary-1] SQL> set linesize 9000\r\n[Primary-1] SQL> select name, value from v$parameter where lower(name) like '%log_archive_dest%' and lower(name) not like '%log_archive_dest_state%' and value is not null;\r\n\r\nNAME                           VALUE\r\n------------------------------ ----------------------------------------------------------------------------------------------\r\nlog_archive_dest_1             LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=primary\r\nlog_archive_dest_2             service=\"standby\", LGWR ASYNC NOAFFIRM delay=0 optional compression=disable max_failure=0 max_\r\n                               connections=1 reopen=300 db_unique_name=\"standby\", valid_for=(all_logfiles,primary_role)\r\n\r\nlog_archive_dest_3             service=\"logical\", LGWR ASYNC NOAFFIRM delay=0 optional compression=disable max_failure=0 max_\r\n                               connections=1 reopen=300 db_unique_name=\"logical\", valid_for=(all_logfiles,primary_role)\r\n<\/pre>\n
[Physical-1] SQL> column name format a30 \r\n[Physical-1] SQL> column value format a94\r\n[Physical-1] SQL> set linesize 9000\r\n[Physical-1] SQL> select name, value from v$parameter where lower(name) like '%log_archive_dest%' and lower(name) not like '%log_archive_dest_state%' and value is not null;\r\n\r\nNAME                           VALUE\r\n------------------------------ ----------------------------------------------------------------------------------------------\r\nlog_archive_dest_1             LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=standby\r\nlog_archive_dest_2             service=\"primary\", LGWR ASYNC NOAFFIRM delay=0 optional compression=disable max_failure=0 max_\r\n                               connections=1 reopen=300 db_unique_name=\"primary\", valid_for=(all_logfiles,primary_role)\r\n\r\nlog_archive_dest_3             service=\"logical\", LGWR ASYNC NOAFFIRM delay=0 optional compression=disable max_failure=0 max_\r\n                               connections=1 reopen=300 db_unique_name=\"logical\", valid_for=(all_logfiles,primary_role)\r\n<\/pre>\n
[Logical-1] SQL> column name format a30 \r\n[Logical-1] SQL> column value format a94\r\n[Logical-1] SQL> set linesize 9000\r\n[Logical-1] SQL> select name, value from v$parameter where lower(name) like '%log_archive_dest%' and lower(name) not like '%log_archive_dest_state%' and value is not null;\r\n\r\nNAME                           VALUE\r\n------------------------------ ----------------------------------------------------------------------------------------------\r\nlog_archive_dest_1             LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=logical\r\n<\/pre>\n
13. We check information such as roles, open modes, modes of databases.<\/p>\n
[Primary-1] SQL> select d.open_mode, d.database_role, a.database_mode, a.recovery_mode, a.protection_mode from v$archive_dest_status a, v$database d where a.database_mode <> 'UNKNOWN';\r\n\r\nOPEN_MODE            DATABASE_ROLE    DATABASE_MODE   RECOVERY_MODE           PROTECTION_MODE\r\n-------------------- ---------------- --------------- ----------------------- --------------------\r\nREAD WRITE           PRIMARY          OPEN            IDLE                    MAXIMUM PERFORMANCE\r\nREAD WRITE           PRIMARY          MOUNTED-STANDBY MANAGED REAL TIME APPLY MAXIMUM PERFORMANCE\r\nREAD WRITE           PRIMARY          OPEN            LOGICAL REAL TIME APPLY MAXIMUM PERFORMANCE\r\n<\/pre>\n
[Physical-1] SQL> select d.open_mode, d.database_role, a.database_mode, a.recovery_mode, a.protection_mode from v$archive_dest_status a, v$database d where a.database_mode <> 'UNKNOWN';\r\n\r\nOPEN_MODE            DATABASE_ROLE    DATABASE_MODE   RECOVERY_MODE           PROTECTION_MODE\r\n-------------------- ---------------- --------------- ----------------------- --------------------\r\nMOUNTED              PHYSICAL STANDBY MOUNTED-STANDBY MANAGED REAL TIME APPLY MAXIMUM PERFORMANCE\r\n<\/pre>\n
[Logical-1] SQL> select d.open_mode, d.database_role, a.database_mode, a.recovery_mode, a.protection_mode from v$archive_dest_status a, v$database d where a.database_mode <> 'UNKNOWN';\r\n\r\nOPEN_MODE            DATABASE_ROLE    DATABASE_MODE   RECOVERY_MODE           PROTECTION_MODE\r\n-------------------- ---------------- --------------- ----------------------- --------------------\r\nREAD WRITE           LOGICAL STANDBY  OPEN            LOGICAL REAL TIME APPLY MAXIMUM PERFORMANCE\r\n<\/pre>\n
SWITCHOVER OPERATION<\/h4>\n
After the preliminary checks are completed successfully, we proceed to the Switchover process.<\/p>\n
1. It will be useful to perform a Log Switch operation in the Primary Database in order to apply the Redo’s that are created in the system in which the Protection Mode is Maximum Performance and the Redo Apply is in Archived Apply mode, to the Standby side in the fastest time.<\/p>\n
Even though we use Real-Time Apply, we do Log Switch to get used to it.<\/p>\n
[Primary-1] SQL> alter system switch logfile;\r\n\r\nSystem altered.\r\n\r\n[Primary-1] SQL> alter system switch logfile;\r\n\r\nSystem altered.\r\n<\/pre>\n
[Primary-2] SQL> alter system switch logfile;\r\n\r\nSystem altered.\r\n\r\n[Primary-2] SQL> alter system switch logfile; \r\n\r\nSystem altered.\r\n<\/pre>\n
2. It is questioned whether the Primary Database is suitable for Switchover.<\/p>\n
[Primary-1] SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;\r\n\r\nSWITCHOVER_STATUS\r\n--------------------\r\nSESSIONS ACTIVE\r\n<\/pre>\n
When the SWITCHOVER_STATUS column is TO STANDBY or SESSIONS ACTIVE, it is suitable for Switchover. Apart from these, we have to repeat the pre-checks.<\/p>\n
3. Switch to the Primary Database Standby role.<\/p>\n
[Primary-1] SQL> ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY WITH SESSION SHUTDOWN;\r\n\r\nDatabase altered.\r\n<\/pre>\n
The reason for using WITH SESSION SHUTDOWN is that SWITCHOVER STATUS is SESSIONS ACTIVE. If SWITCHOVER STATUS TO_STANDBY came, then WITH SESSION SHUTDOWN would not need to be written.<\/p>\n
As a result of this process, the logs falling to the instances are as follows.<\/p>\n[Primary-1]—–>ALERT LOG<\/p>\n
Thu Jan 19 14:24:55 2017\r\nALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY WITH SESSION SHUTDOWN\r\nALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY [Process Id: 28820] (primary1)\r\nWaiting for all non-current ORLs to be archived...\r\nAll non-current ORLs have been archived.\r\nWaiting for all FAL entries to be archived...\r\nAll FAL entries have been archived.\r\nWaiting for potential Physical Standby switchover target to become synchronized...\r\nActive, synchronized Physical Standby switchover target has been identified\r\nSwitchover End-Of-Redo Log thread 1 sequence 676 has been fixed\r\nSwitchover End-Of-Redo Log thread 2 sequence 425 has been fixed\r\nSwitchover: Primary highest seen SCN set to 0x0.0x6c28fe\r\nARCH: Noswitch archival of thread 2, sequence 425\r\nARCH: End-Of-Redo Branch archival of thread 2 sequence 425\r\nARCH: LGWR is actively archiving destination LOG_ARCHIVE_DEST_3\r\nARCH: LGWR is actively archiving destination LOG_ARCHIVE_DEST_2\r\nARCH: Standby redo logfile selected for thread 2 sequence 425 for destination LOG_ARCHIVE_DEST_3\r\nARCH: Standby redo logfile selected for thread 2 sequence 425 for destination LOG_ARCHIVE_DEST_2\r\nArchived Log entry 2748 added for thread 2 sequence 425 ID 0x69915472 dest 1:\r\nARCH: Noswitch archival of thread 1, sequence 676\r\nARCH: End-Of-Redo Branch archival of thread 1 sequence 676\r\nARCH: LGWR is actively archiving destination LOG_ARCHIVE_DEST_3\r\nARCH: LGWR is actively archiving destination LOG_ARCHIVE_DEST_2\r\nARCH: Standby redo logfile selected for thread 1 sequence 676 for destination LOG_ARCHIVE_DEST_3\r\nARCH: Standby redo logfile selected for thread 1 sequence 676 for destination LOG_ARCHIVE_DEST_2\r\nArchived Log entry 2751 added for thread 1 sequence 676 ID 0x69915472 dest 1:\r\nARCH: Archiving is disabled due to current logfile archival\r\nPrimary will check for some target standby to have received alls redo\r\nFinal check for a synchronized target standby. Check will be made once.\r\nLOG_ARCHIVE_DEST_2 is a potential Physical Standby switchover target\r\nLOG_ARCHIVE_DEST_3 is not a Physical Standby \r\nActive, synchronized target has been identified\r\nTarget has also received all redo\r\nBackup controlfile written to trace file \/u01\/app\/oracle\/diag\/rdbms\/primary\/primary1\/trace\/primary1_ora_28820.trc\r\nClearing standby activation ID 1771132018 (0x69915472)\r\nThe primary database controlfile was created using the\r\n'MAXLOGFILES 192' clause.\r\nThere is space for up to 188 standby redo logfiles\r\nUse the following SQL commands on the standby database to create\r\nstandby redo logfiles that match the primary database:\r\nALTER DATABASE ADD STANDBY LOGFILE 'srl1.f' SIZE 52428800;\r\nALTER DATABASE ADD STANDBY LOGFILE 'srl2.f' SIZE 52428800;\r\nALTER DATABASE ADD STANDBY LOGFILE 'srl3.f' SIZE 52428800;\r\nALTER DATABASE ADD STANDBY LOGFILE 'srl4.f' SIZE 52428800;\r\nALTER DATABASE ADD STANDBY LOGFILE 'srl5.f' SIZE 52428800;\r\nArchivelog for thread 1 sequence 676 required for standby recovery\r\nArchivelog for thread 2 sequence 425 required for standby recovery\r\nSwitchover: Primary controlfile converted to standby controlfile succesfully.\r\nThu Jan 19 14:25:02 2017\r\nReconfiguration started (old inc 4, new inc 6)\r\nList of instances:\r\n 1 (myinst: 1) \r\n Global Resource Directory frozen\r\n * dead instance detected - domain 0 invalid = TRUE \r\n Communication channels reestablished\r\n Master broadcasted resource hash value bitmaps\r\n Non-local Process blocks cleaned out\r\nThu Jan 19 14:25:02 2017\r\n LMS 0: 0 GCS shadows cancelled, 0 closed, 0 Xw survived\r\nThu Jan 19 14:25:02 2017\r\n LMS 1: 0 GCS shadows cancelled, 0 closed, 0 Xw survived\r\n Set master node info \r\n Submitted all remote-enqueue requests\r\n Dwn-cvts replayed, VALBLKs dubious\r\n All grantable enqueues granted\r\n Post SMON to start 1st pass IR\r\nThu Jan 19 14:25:02 2017\r\nProcess (ospid 24298) is suspended due to switchover to physical standby operation.\r\nThu Jan 19 14:25:02 2017\r\nInstance recovery: looking for dead threads\r\nProcess (ospid 24302) is suspended due to switchover to physical standby operation.\r\n Submitted all GCS remote-cache requests\r\n Post SMON to start 1st pass IR\r\n Fix write in gcs resources\r\nSwitchover: Complete - Database shutdown required\r\nUSER (ospid: 28820): terminating the instance\r\nInstance terminated by USER, pid = 28820\r\nCompleted: ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY WITH SESSION SHUTDOWN\r\nShutting down instance (abort)\r\nLicense high water mark = 13\r\nThu Jan 19 14:25:03 2017\r\nInstance shutdown complete\r\n<\/pre>\n[Primary-2]—–>ALERT LOG<\/p>\n
Thu Jan 19 14:25:06 2017\r\nSwitchover in progress in another database instance - Database is shutdown automatically\r\nLGWR (ospid: 13956): terminating the instance due to error 16456\r\nInstance terminated by LGWR, pid = 13956\r\n<\/pre>\n[Standby-1]—–>ALERT LOG<\/p>\n
–<\/p>\n[Standby-2]—–>ALERT LOG<\/p>\n
Thu Jan 19 14:25:05 2017\r\nRFS[5]: Assigned to RFS process 26883\r\nRFS[5]: Selected log 8 for thread 2 sequence 425 dbid 1769705496 branch 932222810\r\nThu Jan 19 14:25:05 2017\r\nArchived Log entry 1162 added for thread 2 sequence 425 ID 0x69915472 dest 1:\r\nRFS[5]: Selected log 5 for thread 1 sequence 676 dbid 1769705496 branch 932222810\r\nThu Jan 19 14:25:05 2017\r\nArchived Log entry 1163 added for thread 1 sequence 676 ID 0x69915472 dest 1:\r\nThu Jan 19 14:25:06 2017\r\nRFS[3]: Possible network disconnect with primary database\r\nThu Jan 19 14:25:06 2017\r\nRFS[6]: Assigned to RFS process 21794\r\nRFS[6]: Possible network disconnect with primary database\r\nThu Jan 19 14:25:08 2017\r\nRFS[7]: Assigned to RFS process 26878\r\nRFS[7]: Possible network disconnect with primary database\r\nThu Jan 19 14:25:08 2017\r\nRFS[4]: Possible network disconnect with primary database\r\n<\/pre>\n[Logical-1]—–>ALERT LOG<\/p>\n
Thu Jan 19 14:24:34 2017\r\nRFS LogMiner: RFS id [6492] assigned as thread [1] PING handler\r\nRFS LogMiner: RFS id [6492] assigned as thread [1] PING handler\r\nThu Jan 19 14:24:35 2017\r\nNOTE: Deferred communication with ASM instance\r\nNOTE: deferred map free for map id 34593\r\nThu Jan 19 14:24:36 2017\r\nNOTE: Deferred communication with ASM instance\r\nNOTE: deferred map free for map id 34574\r\nThu Jan 19 14:24:38 2017\r\nRFS[57]: Assigned to RFS process 6508\r\nRFS[57]: Selected log 9 for thread 2 sequence 425 dbid 1769705496 branch 932222810\r\nRFS[57]: Selected log 6 for thread 1 sequence 676 dbid 1769705496 branch 932222810\r\nThu Jan 19 14:24:38 2017\r\nRFS LogMiner: Registered logfile [+FRA\/logical\/foreign_archivelog\/primary\/2017_01_19\/thread_2_seq_425.1244.933690279] to LogMiner session id [1]\r\nThu Jan 19 14:24:38 2017\r\nRFS LogMiner: Registered logfile [+FRA\/logical\/foreign_archivelog\/primary\/2017_01_19\/thread_1_seq_676.1245.933690279] to LogMiner session id [1]\r\nThu Jan 19 14:24:39 2017\r\nRFS[56]: Possible network disconnect with primary database\r\nThu Jan 19 14:24:39 2017\r\nRFS[58]: Assigned to RFS process 13840\r\nRFS[58]: Possible network disconnect with primary database\r\nRFS[59]: Assigned to RFS process 6492\r\nRFS[59]: Possible network disconnect with primary database\r\nThu Jan 19 14:24:42 2017\r\nRFS[54]: Possible network disconnect with primary database\r\n<\/pre>\n
4. The new Physical Standby Database (Old Primary Database) is mounted.<\/p>\n
[Primary-1] SQL> exit    \r\nDisconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production\r\nWith the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,\r\nData Mining and Real Application Testing options\r\nYou have new mail in \/var\/spool\/mail\/oracle\r\n[oracle@primary1 ~]$ sqlplus \/ as sysdba\r\n\r\nSQL*Plus: Release 11.2.0.4.0 Production on Thu Jan 19 14:27:08 2017\r\n\r\nCopyright (c) 1982, 2013, Oracle.  All rights reserved.\r\n\r\nConnected to an idle instance.\r\n<\/pre>\n
[Primary-2] SQL> exit    \r\nDisconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production\r\nWith the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,\r\nData Mining and Real Application Testing options\r\n[oracle@primary2 ~]$ sqlplus \/ as sysdba\r\n\r\nSQL*Plus: Release 11.2.0.4.0 Production on Thu Jan 19 14:27:22 2017\r\n\r\nCopyright (c) 1982, 2013, Oracle.  All rights reserved.\r\n\r\nConnected to an idle instance.\r\n<\/pre>\n
If we pay attention, both of the instances were closed automatically during the process of converting the current Primary to Physical Standby.<\/p>\n
[Primary-1] SQL> startup mount;\r\nORACLE instance started.\r\n\r\nTotal System Global Area 6480490496 bytes\r\nFixed Size                  2265384 bytes\r\nVariable Size            1241517784 bytes\r\nDatabase Buffers         5217714176 bytes\r\nRedo Buffers               18993152 bytes\r\nDatabase mounted.\r\n<\/pre>\n
5. The suitability of the new Primary Database (Old Physical Standby Database) for Switchover is questioned.<\/p>\n
[Physical-2] SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;\r\n\r\nSWITCHOVER_STATUS\r\n--------------------\r\nSESSIONS ACTIVE\r\n<\/pre>\n
6. Old Physical Standby Database, Primary Database is created.<\/p>\n
[Physical-2] SQL> ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY WITH SESSION SHUTDOWN;\r\n\r\nDatabase altered.<\/pre>\n
As a result of this process, the logs falling into the Alert Log are as follows.<\/p>\n[Standby-2]—–>ALERT LOG<\/p>\n
Thu Jan 19 14:32:06 2017\r\nalter database recover managed standby database using current logfile disconnect\r\nAttempt to start background Managed Standby Recovery process (primary2)\r\nThu Jan 19 14:32:06 2017\r\nMRP0 started with pid=34, OS id=28023 \r\nMRP0: Background Managed Standby Recovery process started (primary2)\r\n started logmerger process\r\nThu Jan 19 14:32:11 2017\r\nManaged Standby Recovery starting Real Time Apply\r\nParallel Media Recovery started with 4 slaves\r\nThu Jan 19 14:32:12 2017\r\nBlock change tracking file is current.\r\nStarting background process CTWR\r\nThu Jan 19 14:32:12 2017\r\nCTWR started with pid=48, OS id=28081 \r\nBlock change tracking service is active.\r\nWaiting for all non-current ORLs to be archived...\r\nAll non-current ORLs have been archived.\r\nMedia Recovery Log +FRA\/standby\/archivelog\/2017_01_19\/thread_2_seq_425.702.933690305\r\nIdentified End-Of-Redo (switchover) for thread 2 sequence 425 at SCN 0x0.6c28fe\r\nMedia Recovery Log +FRA\/standby\/archivelog\/2017_01_19\/thread_1_seq_676.703.933690305\r\nIdentified End-Of-Redo (switchover) for thread 1 sequence 676 at SCN 0x0.6c28fe\r\nCompleted: alter database recover managed standby database using current logfile disconnect\r\nResetting standby activation ID 1771132018 (0x69915472)\r\nMedia Recovery End-Of-Redo indicator encountered\r\nMedia Recovery Continuing\r\nMedia Recovery Waiting for thread 1 sequence 677\r\nThu Jan 19 14:33:15 2017\r\nALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY WITH SESSION SHUTDOWN\r\nALTER DATABASE SWITCHOVER TO PRIMARY (primary2)\r\nMaximum wait for role transition is 15 minutes.\r\nSwitchover: Media recovery is still active\r\nRole Change: Canceling MRP - no more redo to apply\r\nThu Jan 19 14:33:16 2017\r\nMRP0: Background Media Recovery cancelled with status 16037\r\nErrors in file \/u01\/app\/oracle\/diag\/rdbms\/standby\/primary2\/trace\/primary2_pr00_28055.trc:\r\nORA-16037: user requested cancel of managed recovery operation\r\nThu Jan 19 14:33:16 2017\r\nManaged Standby Recovery not using Real Time Apply\r\nRecovery interrupted!\r\nThu Jan 19 14:33:16 2017\r\nBlock change tracking service stopping.\r\nStopping background process CTWR\r\nThu Jan 19 14:33:17 2017\r\nMRP0: Background Media Recovery process shutdown (primary2)\r\nRole Change: Canceled MRP\r\nBackup controlfile written to trace file \/u01\/app\/oracle\/diag\/rdbms\/standby\/primary2\/trace\/primary2_ora_27589.trc\r\nSwitchOver after complete recovery through change 7088382\r\nOnline log +DATA\/standby\/onlinelog\/group_1.263.932283679: Thread 1 Group 1 was previously cleared\r\nOnline log +FRA\/standby\/onlinelog\/group_1.256.932283681: Thread 1 Group 1 was previously cleared\r\nOnline log +DATA\/standby\/onlinelog\/group_2.264.932283681: Thread 1 Group 2 was previously cleared\r\nOnline log +FRA\/standby\/onlinelog\/group_2.257.932283681: Thread 1 Group 2 was previously cleared\r\nOnline log +DATA\/standby\/onlinelog\/group_3.265.932283681: Thread 2 Group 3 was previously cleared\r\nOnline log +FRA\/standby\/onlinelog\/group_3.258.932283681: Thread 2 Group 3 was previously cleared\r\nOnline log +DATA\/standby\/onlinelog\/group_4.266.932283681: Thread 2 Group 4 was previously cleared\r\nOnline log +FRA\/standby\/onlinelog\/group_4.259.932283681: Thread 2 Group 4 was previously cleared\r\nStandby became primary SCN: 7088380\r\nSwitchover: Complete - Database mounted as primary\r\nCompleted: ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY WITH SESSION SHUTDOWN\r\n<\/pre>\n
7. The new Primary Database is set to OPEN mode.<\/p>\n
[Physical-2] SQL> ALTER DATABASE OPEN;\r\n\r\nDatabase altered.<\/pre>\n
8. We start the Redo-Apply process in the new Physical Standby Database.<\/p>\n
[Primary-1] SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT;\r\n\r\nDatabase altered.\r\n<\/pre>\n[Primary-1]—–>ALERT LOG<\/p>\n
Thu Jan 19 14:34:26 2017\r\nPrimary database is in MAXIMUM PERFORMANCE mode\r\nRFS[2]: Assigned to RFS process 6174\r\nRFS[2]: Selected log 8 for thread 2 sequence 428 dbid 1769705496 branch 932222810\r\nThu Jan 19 14:34:31 2017\r\nRFS[3]: Assigned to RFS process 6189\r\nRFS[3]: Selected log 9 for thread 2 sequence 427 dbid 1769705496 branch 932222810\r\nThu Jan 19 14:34:31 2017\r\nArchived Log entry 2755 added for thread 2 sequence 427 ID 0x69914a7d dest 1:\r\nThu Jan 19 14:36:52 2017\r\nALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT\r\nAttempt to start background Managed Standby Recovery process (primary1)\r\nThu Jan 19 14:36:52 2017\r\nMRP0 started with pid=47, OS id=6768 \r\nMRP0: Background Managed Standby Recovery process started (primary1)\r\n started logmerger process\r\nThu Jan 19 14:36:58 2017\r\nManaged Standby Recovery starting Real Time Apply\r\nParallel Media Recovery started with 4 slaves\r\nThu Jan 19 14:36:58 2017\r\nCHANGE TRACKING change stream 1 is open.\r\nCHANGE TRACKING change stream 2 is open.\r\nCHANGE TRACKING file is not usable. The above change\r\nstream(s) are open. Change tracking was not closed\r\ncleanly the last time it was shutdown.\r\nCHANGE TRACKING is reinitializing the change tracking file.\r\nStarting background process CTWR\r\nThu Jan 19 14:36:58 2017\r\nCTWR started with pid=53, OS id=6808 \r\nBlock change tracking service is active.\r\nWaiting for all non-current ORLs to be archived...\r\nAll non-current ORLs have been archived.\r\nClearing online redo logfile 1 +DATA\/primary\/onlinelog\/group_1.261.932222811\r\nClearing online log 1 of thread 1 sequence number 677\r\nClearing online redo logfile 1 complete\r\nClearing online redo logfile 2 +DATA\/primary\/onlinelog\/group_2.262.932222811\r\nClearing online log 2 of thread 1 sequence number 675\r\nCompleted: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT\r\nClearing online redo logfile 2 complete\r\nClearing online redo logfile 3 +DATA\/primary\/onlinelog\/group_3.266.932223145\r\nClearing online log 3 of thread 2 sequence number 428\r\nClearing online redo logfile 3 complete\r\nClearing online redo logfile 4 +DATA\/primary\/onlinelog\/group_4.267.932223147\r\nClearing online log 4 of thread 2 sequence number 427\r\nClearing online redo logfile 4 complete\r\nMedia Recovery Log +FRA\/primary\/archivelog\/2017_01_19\/thread_2_seq_425.948.933690299\r\nIdentified End-Of-Redo (switchover) for thread 2 sequence 425 at SCN 0x0.6c28fe\r\nMedia Recovery Log +FRA\/primary\/archivelog\/2017_01_19\/thread_1_seq_675.947.933688887\r\nMedia Recovery Log +FRA\/primary\/archivelog\/2017_01_19\/thread_1_seq_676.949.933690299\r\nIdentified End-Of-Redo (switchover) for thread 1 sequence 676 at SCN 0x0.6c28fe\r\nResetting standby activation ID 0 (0x0)\r\nMedia Recovery End-Of-Redo indicator encountered\r\nMedia Recovery Continuing\r\nMedia Recovery Waiting for thread 1 sequence 677\r\nThu Jan 19 14:37:20 2017\r\nRFS[4]: Assigned to RFS process 6964\r\nRFS[4]: Opened log for thread 1 sequence 677 dbid 1769705496 branch 932222810\r\nArchived Log entry 2756 added for thread 1 sequence 677 rlc 932222810 ID 0x0 dest 2:\r\nThu Jan 19 14:37:21 2017\r\nMedia Recovery Log +FRA\/primary\/archivelog\/2017_01_19\/thread_1_seq_677.952.933691041\r\nMedia Recovery Log +FRA\/primary\/archivelog\/2017_01_19\/thread_2_seq_426.950.933690859\r\nMedia Recovery Log +FRA\/primary\/archivelog\/2017_01_19\/thread_2_seq_427.951.933690871\r\nMedia Recovery Waiting for thread 2 sequence 428 (in transit)\r\nRecovery of Online Redo Log: Thread 2 Group 8 Seq 428 Reading mem 0\r\n  Mem# 0: +FRA\/primary\/onlinelog\/group_8.261.932225269<\/pre>\n
9. Switchover process finished. First, we query the modes of the databases.<\/p>\n
[Primary-1] SQL> select name, database_role, open_mode from gv$database;\r\n\r\nNAME      DATABASE_ROLE    OPEN_MODE\r\n--------- ---------------- --------------------\r\nPRIMARY   PHYSICAL STANDBY MOUNTED\r\n<\/pre>\n
[Physical-2] SQL> select name, database_role, open_mode from gv$database;  \r\n                                                                   \r\nNAME      DATABASE_ROLE    OPEN_MODE\r\n--------- ---------------- --------------------\r\nPRIMARY   PRIMARY          READ WRITE\r\nPRIMARY   PRIMARY          READ WRITE\r\n<\/pre>\n
[Logical-2] SQL> select name, database_role, open_mode from gv$database;\r\n\r\nNAME      DATABASE_ROLE    OPEN_MODE\r\n--------- ---------------- --------------------\r\nLOGICAL   LOGICAL STANDBY  READ WRITE\r\nLOGICAL   LOGICAL STANDBY  READ WRITE<\/pre>\n
10. The 2nd instance of the old Primary, which is automatically closed during switchover, opens.<\/p>\n
[Primary-2] SQL> startup mount;\r\nORACLE instance started.\r\n\r\nTotal System Global Area 6480490496 bytes\r\nFixed Size                  2265384 bytes\r\nVariable Size            1241517784 bytes\r\nDatabase Buffers         5217714176 bytes\r\nRedo Buffers               18993152 bytes\r\nDatabase mounted.\r\n<\/pre>\n
11. After the opened instances, we start the controls.<\/p>\n
a. Database roles are checked in all instances.<\/p>\n
[Physical-1] SQL> select name, database_role, open_mode from gv$database;\r\n\r\nNAME                           DATABASE_ROLE    OPEN_MODE\r\n------------------------------ ---------------- --------------------\r\nPRIMARY                        PRIMARY          READ WRITE\r\nPRIMARY                        PRIMARY          READ WRITE\r\n<\/pre>\n
[Primary-1] SQL> select name, database_role, open_mode from gv$database;\r\n\r\nNAME      DATABASE_ROLE    OPEN_MODE\r\n--------- ---------------- --------------------\r\nPRIMARY   PHYSICAL STANDBY MOUNTED\r\nPRIMARY   PHYSICAL STANDBY MOUNTED\r\n<\/pre>\n
[Logical-1] SQL> select name, database_role, open_mode from gv$database;\r\n\r\nNAME                           DATABASE_ROLE    OPEN_MODE\r\n------------------------------ ---------------- --------------------\r\nLOGICAL                        LOGICAL STANDBY  READ WRITE\r\nLOGICAL                        LOGICAL STANDBY  READ WRITE\r\n<\/pre>\n
b.Switchover operation is performed in the new Primary Database and it is seen whether the logs are processed or not.<\/p>\n
[Physical-1] SQL> alter system switch logfile;\r\n\r\nSystem altered.\r\n\r\n[Physical-1] SQL> alter system switch logfile;\r\n\r\nSystem altered.\r\n<\/pre>\n
[Physical-2] SQL> alter system switch logfile;\r\n\r\nSystem altered.\r\n\r\n[Physical-2] SQL> alter system switch logfile;\r\n\r\nSystem altered.\r\n<\/pre>\n
[Physical-1] SQL> select max(sequence#),thread# from v$archived_log group by thread#;\r\n\r\nMAX(SEQUENCE#)    THREAD#\r\n-------------- ----------\r\n           681          1\r\n           430          2\r\n<\/pre>\n
[Primary-1] SQL> select max(sequence#),thread# from v$archived_log group by thread#;\r\n\r\nMAX(SEQUENCE#)    THREAD#\r\n-------------- ----------\r\n           681          1\r\n           430          2\r\n<\/pre>\n
[Logical-1] SQL> SELECT max(sequence#),thread#,applied FROM dba_logstdby_log group by thread#, applied;\r\n\r\nMAX(SEQUENCE#)    THREAD# APPLIED\r\n-------------- ---------- --------\r\n           681          1 YES\r\n           430          2 YES\r\n<\/pre>\n
c. We check that Redo Transport and Apply Processes are working.<\/p>\n
[Primary-1] SQL> SELECT process, status, group#, thread#, sequence# FROM v$managed_standby order by process, group#, thread#, sequence#;\r\n\r\nPROCESS   STATUS       GROUP#        THREAD#  SEQUENCE#\r\n--------- ------------ ---------- ---------- ----------\r\nARCH      CLOSING      5                   1        678\r\nARCH      CLOSING      5                   1        680\r\nARCH      CLOSING      6                   1        681\r\nARCH      CLOSING      8                   2        428\r\nARCH      CLOSING      8                   2        430\r\nARCH      CLOSING      9                   2        429\r\nARCH      CONNECTED    N\/A                 0          0\r\nARCH      CONNECTED    N\/A                 0          0\r\nMRP0      APPLYING_LOG N\/A                 2        431\r\nRFS       IDLE         2                   1        682\r\nRFS       IDLE         4                   2        431\r\n\r\nPROCESS   STATUS       GROUP#        THREAD#  SEQUENCE#\r\n--------- ------------ ---------- ---------- ----------\r\nRFS       IDLE         N\/A                 0          0\r\nRFS       IDLE         N\/A                 0          0\r\nRFS       IDLE         N\/A                 0          0\r\nRFS       IDLE         N\/A                 0          0\r\nRFS       IDLE         N\/A                 0          0\r\nRFS       IDLE         N\/A                 0          0\r\n\r\n17 rows selected.\r\n<\/pre>\n
[Physical-1] SQL> column group# format a10\r\n[Physical-1] SQL> SELECT process, status, group#, thread#, sequence# FROM v$managed_standby order by process, group#, thread#, sequence#;\r\n\r\nPROCESS   STATUS       GROUP#        THREAD#  SEQUENCE#\r\n--------- ------------ ---------- ---------- ----------\r\nARCH      CLOSING      1                   1        679\r\nARCH      CLOSING      1                   1        681\r\nARCH      CLOSING      2                   1        680\r\nARCH      CONNECTED    N\/A                 0          0\r\nARCH      CONNECTED    N\/A                 0          0\r\nARCH      CLOSING      N\/A                 1        678\r\nARCH      CLOSING      N\/A                 1        679\r\nARCH      CLOSING      N\/A                 1        679\r\nLNS       WRITING      2                   1        682\r\nLNS       WRITING      2                   1        682\r\n\r\n10 rows selected.\r\n<\/pre>\n
[Logical-1] SQL> column spid format a7\r\n[Logical-1] SQL> column type format a12\r\n[Logical-1] SQL> column status format a57\r\n[Logical-1] SQL> set linesize 500\r\n[Logical-1] SQL> select sid, serial#, spid, type, status from v$logstdby_process;\r\n\r\n       SID    SERIAL# SPID    TYPE         STATUS\r\n---------- ---------- ------- ------------ ---------------------------------------------------------\r\n        79          3 7672    COORDINATOR  ORA-16116: no work available\r\n        71          9 7694    ANALYZER     ORA-16116: no work available\r\n       143          1 7698    APPLIER      ORA-16116: no work available\r\n       202          1 7702    APPLIER      ORA-16116: no work available\r\n        19          1 7711    APPLIER      ORA-16116: no work available\r\n        81          1 7715    APPLIER      ORA-16116: no work available\r\n       145          1 7719    APPLIER      ORA-16116: no work available\r\n       141          5 7682    READER       ORA-16242: Processing log file (thread# 1, sequence# 682)\r\n       200         11 7686    BUILDER      ORA-16116: no work available\r\n        15          3 7690    PREPARER     ORA-16116: no work available\r\n\r\n10 rows selected.\r\n<\/pre>\n
[Logical-2] SQL> column spid format a7\r\n[Logical-2] SQL> column type format a12\r\n[Logical-2] SQL> column status format a57\r\n[Logical-2] SQL> set linesize 500\r\n[Logical-2] SQL> select sid, serial#, spid, type, status from v$logstdby_process;\r\n\r\nno rows selected\r\n<\/pre>\n
d. We check if there is a GAP in the new Physical Standby Database.<\/p>\n
[Primary-1] SQL> set linesize 9000\r\n[Primary-1] SQL> column name format a25\r\n[Primary-1] SQL> column value format a20\r\n[Primary-1] SQL> column time_computed format a25\r\n[Primary-1] SQL> SELECT name, value, time_computed FROM v$dataguard_stats;\r\n\r\nNAME                      VALUE                TIME_COMPUTED\r\n------------------------- -------------------- -------------------------\r\ntransport lag             +00 00:00:00         01\/19\/2017 14:51:03\r\napply lag                 +00 00:00:00         01\/19\/2017 14:51:03\r\napply finish time         +00 00:00:00.000     01\/19\/2017 14:51:03\r\nestimated startup time    27                   01\/19\/2017 14:51:03\r\n<\/pre>\n
e.We check the validity of archive locations.<\/p>\n
[Physical-1] SQL> SELECT dest_id,valid_type,valid_role,valid_now FROM v$archive_dest;\r\n\r\n   DEST_ID VALID_TYPE      VALID_ROLE   VALID_NOW\r\n---------- --------------- ------------ ----------------\r\n         1 ALL_LOGFILES    ALL_ROLES    YES\r\n         2 ALL_LOGFILES    PRIMARY_ROLE YES\r\n         3 ALL_LOGFILES    PRIMARY_ROLE YES\r\n<\/pre>\n
[Primary-1] SQL> SELECT dest_id,valid_type,valid_role,valid_now FROM v$archive_dest;\r\n\r\n   DEST_ID VALID_TYPE      VALID_ROLE   VALID_NOW\r\n---------- --------------- ------------ ----------------\r\n         1 ALL_LOGFILES    ALL_ROLES    YES\r\n         2 ALL_LOGFILES    PRIMARY_ROLE WRONG VALID_ROLE\r\n         3 ALL_LOGFILES    PRIMARY_ROLE WRONG VALID_ROLE\r\n<\/pre>\n
While DEST_ID of 2 and 3 in Physical-1 before switchover was WRONG VALID_ROLE, now VALID_NOW parameter in Primary-1 has this value. The reason, of course, is the changing of roles.<\/p>\n
f.Finally, we make a general check of the databases.<\/p>\n
[Physical-1] SQL> set linesize 9000\r\n[Physical-1] SQL> select d.open_mode, d.database_role, a.database_mode, a.recovery_mode, a.protection_mode from v$archive_dest_status a, v$database d where a.database_mode <> 'UNKNOWN';\r\n\r\nOPEN_MODE            DATABASE_ROLE    DATABASE_MODE   RECOVERY_MODE           PROTECTION_MODE\r\n-------------------- ---------------- --------------- ----------------------- --------------------\r\nREAD WRITE           PRIMARY          OPEN            IDLE                    MAXIMUM PERFORMANCE\r\nREAD WRITE           PRIMARY          OPEN_READ-ONLY  MANAGED REAL TIME APPLY MAXIMUM PERFORMANCE\r\nREAD WRITE           PRIMARY          OPEN            LOGICAL REAL TIME APPLY MAXIMUM PERFORMANCE<\/pre>\n
 <\/p>\n
<\/div>\n
<\/path><\/svg><\/i> \"Loading\"<\/p>\n
<\/div>\n","protected":false},"excerpt":{"rendered":"
In today’s article, we will talk about Switchover from Primary Database to Physical Standby Database with SQLPLUS Commands. Before Switchover, there are a series of checks to see if the system is suitable for Switchover. Some of these controls are general and made for our entire Data Guard Environment, while others are specific to Switchover. …<\/p>\n
<\/div>\n
<\/path><\/svg><\/i> \"Loading\"<\/p>\n
<\/div>\n","protected":false},"author":484,"featured_media":37664,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_uf_show_specific_survey":0,"_uf_disable_surveys":false,"footnotes":""},"categories":[4],"tags":[],"class_list":["post-37571","post","type-post","status-publish","format-standard","has-post-thumbnail","","category-oracle"],"aioseo_notices":[],"a3_pvc":{"activated":true,"total_views":469,"today_views":0},"yoast_head":"\nSwitchover from Primary Database to Physical Standby Database with SQLPLUS Commands - Database Tutorials<\/title>\n<meta name=\"description\" content=\"In today's article, we will talk about Switchover from Primary Database to Physical Standby Database with SQLPLUS Commands.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/dbtut.com\/index.php\/2022\/04\/05\/switchover-from-primary-database-to-physical-standby-database-with-sqlplus-commands\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Switchover from Primary Database to Physical Standby Database with SQLPLUS Commands - Database Tutorials\" \/>\n<meta property=\"og:description\" content=\"In today's article, we will talk about Switchover from Primary Database to Physical Standby Database with SQLPLUS Commands.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/dbtut.com\/index.php\/2022\/04\/05\/switchover-from-primary-database-to-physical-standby-database-with-sqlplus-commands\/\" \/>\n<meta property=\"og:site_name\" content=\"Database Tutorials\" \/>\n<meta property=\"article:published_time\" content=\"2022-04-05T09:38:01+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2022-04-05T09:40:36+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/04\/Ekran-Alintisi-3.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"815\" \/>\n\t<meta property=\"og:image:height\" content=\"370\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Onur ARDAHANLI\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Onur ARDAHANLI\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"25 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/04\/05\/switchover-from-primary-database-to-physical-standby-database-with-sqlplus-commands\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/04\/05\/switchover-from-primary-database-to-physical-standby-database-with-sqlplus-commands\/\"},\"author\":{\"name\":\"Onur ARDAHANLI\",\"@id\":\"https:\/\/dbtut.com\/#\/schema\/person\/7fcd466cd0d347ec64aaa48f18f780c6\"},\"headline\":\"Switchover from Primary Database to Physical Standby Database with SQLPLUS Commands\",\"datePublished\":\"2022-04-05T09:38:01+00:00\",\"dateModified\":\"2022-04-05T09:40:36+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/04\/05\/switchover-from-primary-database-to-physical-standby-database-with-sqlplus-commands\/\"},\"wordCount\":811,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/dbtut.com\/#organization\"},\"image\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/04\/05\/switchover-from-primary-database-to-physical-standby-database-with-sqlplus-commands\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/04\/Ekran-Alintisi-3.jpg\",\"articleSection\":[\"ORACLE\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/dbtut.com\/index.php\/2022\/04\/05\/switchover-from-primary-database-to-physical-standby-database-with-sqlplus-commands\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/04\/05\/switchover-from-primary-database-to-physical-standby-database-with-sqlplus-commands\/\",\"url\":\"https:\/\/dbtut.com\/index.php\/2022\/04\/05\/switchover-from-primary-database-to-physical-standby-database-with-sqlplus-commands\/\",\"name\":\"Switchover from Primary Database to Physical Standby Database with SQLPLUS Commands - Database Tutorials\",\"isPartOf\":{\"@id\":\"https:\/\/dbtut.com\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/04\/05\/switchover-from-primary-database-to-physical-standby-database-with-sqlplus-commands\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/04\/05\/switchover-from-primary-database-to-physical-standby-database-with-sqlplus-commands\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/04\/Ekran-Alintisi-3.jpg\",\"datePublished\":\"2022-04-05T09:38:01+00:00\",\"dateModified\":\"2022-04-05T09:40:36+00:00\",\"description\":\"In today's article, we will talk about Switchover from Primary Database to Physical Standby Database with SQLPLUS Commands.\",\"breadcrumb\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/04\/05\/switchover-from-primary-database-to-physical-standby-database-with-sqlplus-commands\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/dbtut.com\/index.php\/2022\/04\/05\/switchover-from-primary-database-to-physical-standby-database-with-sqlplus-commands\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/04\/05\/switchover-from-primary-database-to-physical-standby-database-with-sqlplus-commands\/#primaryimage\",\"url\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/04\/Ekran-Alintisi-3.jpg\",\"contentUrl\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/04\/Ekran-Alintisi-3.jpg\",\"width\":815,\"height\":370},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/04\/05\/switchover-from-primary-database-to-physical-standby-database-with-sqlplus-commands\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/dbtut.com\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Switchover from Primary Database to Physical Standby Database with SQLPLUS Commands\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/dbtut.com\/#website\",\"url\":\"https:\/\/dbtut.com\/\",\"name\":\"Database Tutorials\",\"description\":\"MSSQL, Oracle, PostgreSQL, MySQL, MariaDB, DB2, Sybase, Teradata, Big Data, NOSQL, MongoDB, Couchbase, Cassandra, Windows, Linux\",\"publisher\":{\"@id\":\"https:\/\/dbtut.com\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/dbtut.com\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/dbtut.com\/#organization\",\"name\":\"dbtut\",\"url\":\"https:\/\/dbtut.com\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/dbtut.com\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2021\/02\/dbtutlogo.jpg\",\"contentUrl\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2021\/02\/dbtutlogo.jpg\",\"width\":223,\"height\":36,\"caption\":\"dbtut\"},\"image\":{\"@id\":\"https:\/\/dbtut.com\/#\/schema\/logo\/image\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\/\/dbtut.com\/#\/schema\/person\/7fcd466cd0d347ec64aaa48f18f780c6\",\"name\":\"Onur ARDAHANLI\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/dbtut.com\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/ecd20c3e1374ced4e1aefc82101cce4cd437be8fd957d1be3d106668b8a1b990?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/ecd20c3e1374ced4e1aefc82101cce4cd437be8fd957d1be3d106668b8a1b990?s=96&d=mm&r=g\",\"caption\":\"Onur ARDAHANLI\"},\"url\":\"https:\/\/dbtut.com\/index.php\/author\/onurardahanli\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Switchover from Primary Database to Physical Standby Database with SQLPLUS Commands - Database Tutorials","description":"In today's article, we will talk about Switchover from Primary Database to Physical Standby Database with SQLPLUS Commands.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/dbtut.com\/index.php\/2022\/04\/05\/switchover-from-primary-database-to-physical-standby-database-with-sqlplus-commands\/","og_locale":"en_US","og_type":"article","og_title":"Switchover from Primary Database to Physical Standby Database with SQLPLUS Commands - Database Tutorials","og_description":"In today's article, we will talk about Switchover from Primary Database to Physical Standby Database with SQLPLUS Commands.","og_url":"https:\/\/dbtut.com\/index.php\/2022\/04\/05\/switchover-from-primary-database-to-physical-standby-database-with-sqlplus-commands\/","og_site_name":"Database Tutorials","article_published_time":"2022-04-05T09:38:01+00:00","article_modified_time":"2022-04-05T09:40:36+00:00","og_image":[{"width":815,"height":370,"url":"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/04\/Ekran-Alintisi-3.jpg","type":"image\/jpeg"}],"author":"Onur ARDAHANLI","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Onur ARDAHANLI","Est. reading time":"25 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/dbtut.com\/index.php\/2022\/04\/05\/switchover-from-primary-database-to-physical-standby-database-with-sqlplus-commands\/#article","isPartOf":{"@id":"https:\/\/dbtut.com\/index.php\/2022\/04\/05\/switchover-from-primary-database-to-physical-standby-database-with-sqlplus-commands\/"},"author":{"name":"Onur ARDAHANLI","@id":"https:\/\/dbtut.com\/#\/schema\/person\/7fcd466cd0d347ec64aaa48f18f780c6"},"headline":"Switchover from Primary Database to Physical Standby Database with SQLPLUS Commands","datePublished":"2022-04-05T09:38:01+00:00","dateModified":"2022-04-05T09:40:36+00:00","mainEntityOfPage":{"@id":"https:\/\/dbtut.com\/index.php\/2022\/04\/05\/switchover-from-primary-database-to-physical-standby-database-with-sqlplus-commands\/"},"wordCount":811,"commentCount":0,"publisher":{"@id":"https:\/\/dbtut.com\/#organization"},"image":{"@id":"https:\/\/dbtut.com\/index.php\/2022\/04\/05\/switchover-from-primary-database-to-physical-standby-database-with-sqlplus-commands\/#primaryimage"},"thumbnailUrl":"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/04\/Ekran-Alintisi-3.jpg","articleSection":["ORACLE"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/dbtut.com\/index.php\/2022\/04\/05\/switchover-from-primary-database-to-physical-standby-database-with-sqlplus-commands\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/dbtut.com\/index.php\/2022\/04\/05\/switchover-from-primary-database-to-physical-standby-database-with-sqlplus-commands\/","url":"https:\/\/dbtut.com\/index.php\/2022\/04\/05\/switchover-from-primary-database-to-physical-standby-database-with-sqlplus-commands\/","name":"Switchover from Primary Database to Physical Standby Database with SQLPLUS Commands - Database Tutorials","isPartOf":{"@id":"https:\/\/dbtut.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/dbtut.com\/index.php\/2022\/04\/05\/switchover-from-primary-database-to-physical-standby-database-with-sqlplus-commands\/#primaryimage"},"image":{"@id":"https:\/\/dbtut.com\/index.php\/2022\/04\/05\/switchover-from-primary-database-to-physical-standby-database-with-sqlplus-commands\/#primaryimage"},"thumbnailUrl":"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/04\/Ekran-Alintisi-3.jpg","datePublished":"2022-04-05T09:38:01+00:00","dateModified":"2022-04-05T09:40:36+00:00","description":"In today's article, we will talk about Switchover from Primary Database to Physical Standby Database with SQLPLUS Commands.","breadcrumb":{"@id":"https:\/\/dbtut.com\/index.php\/2022\/04\/05\/switchover-from-primary-database-to-physical-standby-database-with-sqlplus-commands\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/dbtut.com\/index.php\/2022\/04\/05\/switchover-from-primary-database-to-physical-standby-database-with-sqlplus-commands\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/dbtut.com\/index.php\/2022\/04\/05\/switchover-from-primary-database-to-physical-standby-database-with-sqlplus-commands\/#primaryimage","url":"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/04\/Ekran-Alintisi-3.jpg","contentUrl":"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/04\/Ekran-Alintisi-3.jpg","width":815,"height":370},{"@type":"BreadcrumbList","@id":"https:\/\/dbtut.com\/index.php\/2022\/04\/05\/switchover-from-primary-database-to-physical-standby-database-with-sqlplus-commands\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/dbtut.com\/"},{"@type":"ListItem","position":2,"name":"Switchover from Primary Database to Physical Standby Database with SQLPLUS Commands"}]},{"@type":"WebSite","@id":"https:\/\/dbtut.com\/#website","url":"https:\/\/dbtut.com\/","name":"Database Tutorials","description":"MSSQL, Oracle, PostgreSQL, MySQL, MariaDB, DB2, Sybase, Teradata, Big Data, NOSQL, MongoDB, Couchbase, Cassandra, Windows, Linux","publisher":{"@id":"https:\/\/dbtut.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/dbtut.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/dbtut.com\/#organization","name":"dbtut","url":"https:\/\/dbtut.com\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/dbtut.com\/#\/schema\/logo\/image\/","url":"https:\/\/dbtut.com\/wp-content\/uploads\/2021\/02\/dbtutlogo.jpg","contentUrl":"https:\/\/dbtut.com\/wp-content\/uploads\/2021\/02\/dbtutlogo.jpg","width":223,"height":36,"caption":"dbtut"},"image":{"@id":"https:\/\/dbtut.com\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/dbtut.com\/#\/schema\/person\/7fcd466cd0d347ec64aaa48f18f780c6","name":"Onur ARDAHANLI","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/dbtut.com\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/ecd20c3e1374ced4e1aefc82101cce4cd437be8fd957d1be3d106668b8a1b990?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/ecd20c3e1374ced4e1aefc82101cce4cd437be8fd957d1be3d106668b8a1b990?s=96&d=mm&r=g","caption":"Onur ARDAHANLI"},"url":"https:\/\/dbtut.com\/index.php\/author\/onurardahanli\/"}]}},"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/posts\/37571","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/users\/484"}],"replies":[{"embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/comments?post=37571"}],"version-history":[{"count":0,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/posts\/37571\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/media\/37664"}],"wp:attachment":[{"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/media?parent=37571"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/categories?post=37571"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/tags?post=37571"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}