{"id":22654,"date":"2023-02-17T14:25:08","date_gmt":"2023-02-17T13:25:08","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=22654"},"modified":"2023-02-17T14:27:47","modified_gmt":"2023-02-17T13:27:47","slug":"can-we-benefit-from-oracle-seha-relocate-and-failover-with-dbvisit-standbymp-switchover","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/can-we-benefit-from-oracle-seha-relocate-and-failover-with-dbvisit-standbymp-switchover\/","title":{"rendered":"Can we benefit from Oracle SEHA relocate and failover with dbvisit StandbyMP switchover?"},"content":{"rendered":"\n<p>I recently wrote an article about how to combine Oracle SEHA database running on ODA 2-HA and dbvisit StandbyMP solution. See my article here : <a href=\"https:\/\/www.dbi-services.com\/blog\/combine-oracle-seha-on-oda-with-dbvisit-standbymp\/\" target=\"_blank\" rel=\"noreferrer noopener\">https:\/\/www.dbi-services.com\/blog\/combine-oracle-seha-on-oda-with-dbvisit-standbymp\/<\/a>. But are really all those high availability and disaster recovering solutions working together? Do Oracle SEHA relocate and failover functionalities work in conjunction with dbvisit StandbyMP switchover? Let&#8217;s see and try it!<\/p>\n\n\n\n<!--more-->\n\n\n\n<h2 class=\"wp-block-heading\">Test environment<\/h2>\n\n\n\n<p>Just to recall my test environment<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>an ODA X5-2-HA with 2 nodes dbioda02 and dbioda03<\/li>\n\n\n\n<li>an ODA X8-2M with node named dbi-oda-x8<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\"><\/ul>\n\n\n\n<p>The ODA X5-2-HA will host an HA database with db_unique_name DBISEHA, which I could relocate to the other nodes or benefit of the automatic failover in case the privilege nodes is crashing.<\/p>\n\n\n\n<p>The ODA X8-2M will host a single instance database, with db_unique_name DBISEHA_STD, initially the standby one.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Perform a graceful swithover<\/h2>\n\n\n\n<p>Let&#8217;s run a switchover between primary node dbi0da02 and dbi-oda-x8 nodes.<\/p>\n\n\n\n<p>The primary database instance is hosted on node dbioda02:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,4]\">\noracle@dbioda02:\/home\/oracle\/ [DBISEHA] ps -ef | grep [p]mon | grep -i dbiseha\noracle   18471     1  0 Jan27 ?        00:01:09 ora_pmon_DBISEHA\n\noracle@dbioda03:\/home\/oracle\/ [DBISEHA] ps -ef | grep [p]mon | grep -i dbiseha\noracle@dbioda03:\/home\/oracle\/ [DBISEHA]\n<\/pre>\n<\/br>\n\n\n\n<p>The primary database :<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1]\">\noracle@dbioda02:\/home\/oracle\/ [DBISEHA] DBISEHA\n********* dbi services Ltd. *********\nSTATUS                 : OPEN\nDB_UNIQUE_NAME         : DBISEHA\nOPEN_MODE              : READ WRITE\nLOG_MODE               : ARCHIVELOG\nDATABASE_ROLE          : PRIMARY\nFLASHBACK_ON           : NO\nFORCE_LOGGING          : YES\nVERSION                : 19.15.0.0.0\nCDB Enabled            : NO\n*************************************\n<\/pre>\n<\/br>\n\n\n\n<p>The standby database:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1]\">\noracle@dbi-oda-x8:\/home\/oracle\/ [DBISEHA] DBISEHA\n********* dbi services Ltd. *********\nSTATUS                 : MOUNTED\nDB_UNIQUE_NAME         : DBISEHA_STD\nOPEN_MODE              : MOUNTED\nLOG_MODE               : ARCHIVELOG\nDATABASE_ROLE          : PHYSICAL STANDBY\nFLASHBACK_ON           : NO\nFORCE_LOGGING          : YES\nVERSION                : 19.15.0.0.0\nCDB Enabled            : NO\n*************************************\n<\/pre>\n<\/br>\n\n\n\n<p>Let&#8217;s ship all archive logs from primary to standby database:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1]\">\noracle@dbioda02:\/home\/oracle\/ [DBISEHA] \/u01\/app\/dbvisit\/standbymp\/oracle\/dbvctl -d DBISEHA\n=============================================================\nDbvisit Standby Database Technology (11.2.1_0_g8a57214c) (pid 30570)\ndbvctl started on dbvisitvippri: Fri Feb 17 10:00:14 2023\n=============================================================\n\n&gt;&gt;&gt; Obtaining information from standby database (RUN_INSPECT=Y)... done\n    Thread: 1 Archive log gap: 0. Transfer log gap: 0\n&gt;&gt;&gt; Sending heartbeat message... skipped\n&gt;&gt;&gt; Performing a log switch... done\n&gt;&gt;&gt; Transferring Log file(s) from DBISEHA on dbvisitvippri to dbi-oda-x8:\n\n    thread 1 sequence 7 (thread_1_seq_7.333.1129024819)... done\n\n=============================================================\ndbvctl ended on dbvisitvippri: Fri Feb 17 10:00:46 2023\n=============================================================\n<\/pre>\n<\/br>\n\n\n\n<p>Let&#8217;s apply them on the standby database:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1]\">\noracle@dbi-oda-x8:\/home\/oracle\/ [DBISEHA] \/u01\/app\/dbvisit\/standbymp\/oracle\/dbvctl -d DBISEHA\n=============================================================\nDbvisit Standby Database Technology (11.2.1_0_g8a57214c) (pid 2528)\ndbvctl started on dbi-oda-x8: Fri Feb 17 10:00:46 2023\n=============================================================\n\n&gt;&gt;&gt; Sending heartbeat message... skipped\n\n&gt;&gt;&gt; Applying Log file(s) from dbvisitvippri to DBISEHA on dbi-oda-x8:\n\n    thread 1 sequence 7 (1_7_1127209532.arc)... done\n    Last applied log(s):\n    thread 1 sequence 7\n\n    Next SCN required for recovery 3952980 generated at 2023-02-17:10:00:19 +01:00.\n    Next required log thread 1 sequence 8\n\n=============================================================\ndbvctl ended on dbi-oda-x8: Fri Feb 17 10:01:11 2023\n=============================================================\n<\/pre>\n<\/br>\n\n\n\n<p>Let&#8217;s confirm there is no gap between the primary and the standby databases:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,27,28]\">\noracle@dbioda02:\/home\/oracle\/ [DBISEHA] \/u01\/app\/dbvisit\/standbymp\/oracle\/dbvctl -d DBISEHA -i\n=============================================================\nDbvisit Standby Database Technology (11.2.1_0_g8a57214c) (pid 20814)\ndbvctl started on dbvisitvippri: Fri Feb 17 10:50:04 2023\n=============================================================\n\nDbvisit Standby log gap report for DBISEHA at 202302171050:\n-------------------------------------------------------------\nDescription       | SCN          | Timestamp\n-------------------------------------------------------------\nSource              3954545        2023-02-17:10:50:05 +01:00\nDestination         3952980        2023-02-17:10:00:19 +01:00\n\nStandby database time lag (DAYS-HH:MI:SS): +00:49:46\n\nReport for Thread 1\n-------------------\nSOURCE\nCurrent Sequence 8\nLast Archived Sequence 7\nLast Transferred Sequence 7\nLast Transferred Timestamp 2023-02-17 10:00:45\n\nDESTINATION\nNext Required Recovery Sequence 8\n\nTransfer Log Gap 0\nApply Log Gap 0\n\n=============================================================\ndbvctl ended on dbvisitvippri: Fri Feb 17 10:50:07 2023\n=============================================================\n<\/pre>\n<\/br>\n\n\n\n<p>Transfer and apply log gap output been 0, both primary and standby databases are in sync.<\/p>\n\n\n\n<p>Let&#8217;s switchover! <\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1]\">\noracle@dbioda02:\/home\/oracle\/ [DBISEHA] \/u01\/app\/dbvisit\/standbymp\/oracle\/dbvctl -d DBISEHA -o switchover\n=============================================================\nDbvisit Standby Database Technology (11.2.1_0_g8a57214c) (pid 23650)\ndbvctl started on dbvisitvippri: Fri Feb 17 10:52:07 2023\n=============================================================\n\n&gt;&gt;&gt; Starting Switchover between dbvisitvippri and dbi-oda-x8\n\nRunning pre-checks       ... done\n\n=&gt;Do you want to proceed with Graceful Switchover? [no]: yes\nYour input: 1\n\nIs this correct?  [Yes]:\nPre processing           ... done\nProcessing primary       ... done\nProcessing standby       ... done\nConverting standby       ... done\nConverting primary       ... done\nCompleting               ... done\nSynchronizing            ... done\nPost processing          ... done\n\n&gt;&gt;&gt; Graceful switchover completed.\n    Primary Database Server: dbi-oda-x8\n    Standby Database Server: dbvisitvippri\n\n&gt;&gt;&gt; Dbvisit Standby can be run as per normal:\n    dbvctl -d DBISEHA\n\nAs part of the Switchover process, the primary and standby controlfiles have been exchanged.Unless you are using RMAN catalog database, you may need to cross-check all backups and review RMAN settings using the SHOW ALL command on the new Primary\/Standby databases. Confirm the path set for the SNAPSHOT CONTROLFILE NAME TO setting is valid on both sides.\nPID:23650\nTRACE:23650_dbvctl_switchover_DBISEHA_202302171052.trc\n\n=============================================================\ndbvctl ended on dbvisitvippri: Fri Feb 17 10:59:28 2023\n=============================================================\n<\/pre>\n<\/br>\n\n\n\n<p>My new primary database is DBISEHA_STD hosted on dbi-oda-x8:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1]\">\noracle@dbi-oda-x8:\/home\/oracle\/ [DBISEHA] DBISEHA\n********* dbi services Ltd. *********\nSTATUS                 : OPEN\nDB_UNIQUE_NAME         : DBISEHA_STD\nOPEN_MODE              : READ WRITE\nLOG_MODE               : ARCHIVELOG\nDATABASE_ROLE          : PRIMARY\nFLASHBACK_ON           : NO\nFORCE_LOGGING          : YES\nVERSION                : 19.15.0.0.0\nCDB Enabled            : NO\n*************************************\n<\/pre>\n<\/br>\n\n\n\n<p>My new standby database is DBISEHA hosted on dbioda02:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1]\">\noracle@dbioda02:\/home\/oracle\/ [DBISEHA] DBISEHA\n********* dbi services Ltd. *********\nSTATUS                 : MOUNTED\nDB_UNIQUE_NAME         : DBISEHA\nOPEN_MODE              : MOUNTED\nLOG_MODE               : ARCHIVELOG\nDATABASE_ROLE          : PHYSICAL STANDBY\nFLASHBACK_ON           : NO\nFORCE_LOGGING          : YES\nVERSION                : 19.15.0.0.0\nCDB Enabled            : NO\n*************************************\n<\/pre>\n<\/br>\n\n\n\n<p>Let&#8217;s generate 3 archive logs on the primary database:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,13,17,21]\">\noracle@dbi-oda-x8:\/home\/oracle\/ [DBISEHA] sqh\n\nSQL*Plus: Release 19.0.0.0.0 - Production on Fri Feb 17 11:04:54 2023\nVersion 19.15.0.0.0\n\nCopyright (c) 1982, 2022, Oracle.  All rights reserved.\n\n\nConnected to:\nOracle Database 19c Standard Edition 2 Release 19.0.0.0.0 - Production\nVersion 19.15.0.0.0\n\nSQL&gt; alter system archive log current;\n\nSystem altered.\n\nSQL&gt; alter system archive log current;\n\nSystem altered.\n\nSQL&gt; alter system archive log current;\n\nSystem altered.\n<\/pre>\n<\/br>\n\n\n\n<p>Send those archive logs to the new standby database:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1]\">\noracle@dbi-oda-x8:\/home\/oracle\/ [DBISEHA] \/u01\/app\/dbvisit\/standbymp\/oracle\/dbvctl -d DBISEHA\n=============================================================\nDbvisit Standby Database Technology (11.2.1_0_g8a57214c) (pid 2981)\ndbvctl started on dbi-oda-x8: Fri Feb 17 11:06:12 2023\n=============================================================\n\n&gt;&gt;&gt; Obtaining information from standby database (RUN_INSPECT=Y)... done\n    Thread: 1 Archive log gap: 3. Transfer log gap: 3\n&gt;&gt;&gt; Transferring Log file(s) from DBISEHA on dbi-oda-x8 to dbvisitvippri:\n\n    thread 1 sequence 14 (thread_1_seq_14.360.1129028709)... done\n    thread 1 sequence 15 (thread_1_seq_15.361.1129028711)... done\n    thread 1 sequence 16 (thread_1_seq_16.362.1129028715)... done\n\n=============================================================\ndbvctl ended on dbi-oda-x8: Fri Feb 17 11:06:21 2023\n=============================================================\n<\/pre>\n<\/br>\n\n\n\n<p>Apply them on the new standby database:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1]\">\noracle@dbioda02:\/home\/oracle\/ [DBISEHA] \/u01\/app\/dbvisit\/standbymp\/oracle\/dbvctl -d DBISEHA\n=============================================================\nDbvisit Standby Database Technology (11.2.1_0_g8a57214c) (pid 57569)\ndbvctl started on dbvisitvippri: Fri Feb 17 11:07:18 2023\n=============================================================\n\n\n&gt;&gt;&gt; Applying Log file(s) from dbi-oda-x8 to DBISEHA on dbvisitvippri:\n\n    thread 1 sequence 14 (1_14_1127209532.arc)... done\n    thread 1 sequence 15 (1_15_1127209532.arc)... done\n    thread 1 sequence 16 (1_16_1127209532.arc)... done\n    Last applied log(s):\n    thread 1 sequence 16\n\n    Next SCN required for recovery 3958195 generated at 2023-02-17:11:05:13 +01:00.\n    Next required log thread 1 sequence 17\n\n=============================================================\ndbvctl ended on dbvisitvippri: Fri Feb 17 11:07:32 2023\n=============================================================\n<\/pre>\n<\/br>\n\n\n\n<p>Control transfer and apply gap to make sure both primary and standby databases are in sync:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,27,28]\">\noracle@dbi-oda-x8:\/home\/oracle\/ [DBISEHA] \/u01\/app\/dbvisit\/standbymp\/oracle\/dbvctl -d DBISEHA -i\n=============================================================\nDbvisit Standby Database Technology (11.2.1_0_g8a57214c) (pid 6687)\ndbvctl started on dbi-oda-x8: Fri Feb 17 11:08:22 2023\n=============================================================\n\nDbvisit Standby log gap report for DBISEHA_STD at 202302171108:\n-------------------------------------------------------------\nDescription       | SCN          | Timestamp\n-------------------------------------------------------------\nSource              3958348        2023-02-17:11:08:22 +01:00\nDestination         3958195        2023-02-17:11:05:13 +01:00\n\nStandby database time lag (DAYS-HH:MI:SS): +00:03:09\n\nReport for Thread 1\n-------------------\nSOURCE\nCurrent Sequence 17\nLast Archived Sequence 16\nLast Transferred Sequence 16\nLast Transferred Timestamp 2023-02-17 11:06:21\n\nDESTINATION\nNext Required Recovery Sequence 17\n\nTransfer Log Gap 0\nApply Log Gap 0\n\n=============================================================\ndbvctl ended on dbi-oda-x8: Fri Feb 17 11:08:27 2023\n=============================================================\n<\/pre>\n<\/br>\n\n\n\n<h2 class=\"wp-block-heading\">Relocate Oracle SEHA database<\/h2>\n\n\n\n<p>The Oracle SEHA database, DBISEHA, has currently the standby role. Of course I could test and relocate the standby database to the other node, dbioda03, or decide to test the relocation functionality having the database in the primary role. Let&#8217;s do that, and this will give me the opportunity as well to first test the switchover back.<\/p>\n\n\n\n<p>Switchover back to dbioda02, hosting the VIP dbvisitvippri.<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1]\">\noracle@dbi-oda-x8:\/home\/oracle\/ [DBISEHA] \/u01\/app\/dbvisit\/standbymp\/oracle\/dbvctl -d DBISEHA -o switchover\n=============================================================\nDbvisit Standby Database Technology (11.2.1_0_g8a57214c) (pid 8871)\ndbvctl started on dbi-oda-x8: Fri Feb 17 11:09:47 2023\n=============================================================\n\n&gt;&gt;&gt; Starting Switchover between dbi-oda-x8 and dbvisitvippri\n\nRunning pre-checks       ... done\n\n=&gt;Do you want to proceed with Graceful Switchover? [no]: yes\nYour input: 1\n\nIs this correct?  [Yes]:\nPre processing           ... done\nProcessing primary       ... done\nProcessing standby       ... done\nConverting standby       ... done\nConverting primary       ... done\nCompleting               ... done\nSynchronizing            ... done\nPost processing          ... done\n\n&gt;&gt;&gt; Graceful switchover completed.\n    Primary Database Server: dbvisitvippri\n    Standby Database Server: dbi-oda-x8\n\n&gt;&gt;&gt; Dbvisit Standby can be run as per normal:\n    dbvctl -d DBISEHA\n\nAs part of the Switchover process, the primary and standby controlfiles have been exchanged.Unless you are using RMAN catalog database, you may need to cross-check all backups and review RMAN settings using the SHOW ALL command on the new Primary\/Standby databases. Confirm the path set for the SNAPSHOT CONTROLFILE NAME TO setting is valid on both sides.\nPID:8871\nTRACE:8871_dbvctl_switchover_DBISEHA_202302171109.trc\n\n=============================================================\ndbvctl ended on dbi-oda-x8: Fri Feb 17 11:17:41 2023\n=============================================================\n<\/pre>\n<\/br>\n\n\n\n<p>So my primary database instance is really running on the node 0, dbioda02:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,4,7,20,23,26]\">\noracle@dbioda02:\/home\/oracle\/ [DBISEHA] ps -ef | grep [p]mon | grep -i dbiseha\noracle   77736     1  0 11:16 ?        00:00:00 ora_pmon_DBISEHA\n\noracle@dbioda02:\/home\/oracle\/ [DBISEHA] ip addr sh pubnet | grep 10.36.0.246\n    inet 10.36.0.246\/24 brd 10.36.0.255 scope global secondary pubnet:2\n\noracle@dbioda02:\/home\/oracle\/ [DBISEHA] DBISEHA\n********* dbi services Ltd. *********\nSTATUS                 : OPEN\nDB_UNIQUE_NAME         : DBISEHA\nOPEN_MODE              : READ WRITE\nLOG_MODE               : ARCHIVELOG\nDATABASE_ROLE          : PRIMARY\nFLASHBACK_ON           : NO\nFORCE_LOGGING          : YES\nVERSION                : 19.15.0.0.0\nCDB Enabled            : NO\n*************************************\n\noracle@dbioda03:\/home\/oracle\/ [DBISEHA] ps -ef | grep [p]mon | grep -i dbiseha\noracle@dbioda03:\/home\/oracle\/ [DBISEHA]\n\noracle@dbioda03:\/home\/oracle\/ [DBISEHA] ip addr sh pubnet | grep 10.36.0.246\noracle@dbioda03:\/home\/oracle\/ [DBISEHA]\n\noracle@dbioda03:\/home\/oracle\/ [DBISEHA] DBISEHA\n********* dbi services Ltd. *********\nSTATUS          : STOPPED\n*************************************\n<\/pre>\n<\/br>\n\n\n\n<p>And both primary and standby are in sync:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,27,28]\">\noracle@dbioda02:\/home\/oracle\/ [DBISEHA] \/u01\/app\/dbvisit\/standbymp\/oracle\/dbvctl -d DBISEHA -i\n=============================================================\nDbvisit Standby Database Technology (11.2.1_0_g8a57214c) (pid 97164)\ndbvctl started on dbvisitvippri: Fri Feb 17 11:27:16 2023\n=============================================================\n\nDbvisit Standby log gap report for DBISEHA at 202302171127:\n-------------------------------------------------------------\nDescription       | SCN          | Timestamp\n-------------------------------------------------------------\nSource              3962813        2023-02-17:11:27:16 +01:00\nDestination         3962604        2023-02-17:11:21:48 +01:00\n\nStandby database time lag (DAYS-HH:MI:SS): +00:05:28\n\nReport for Thread 1\n-------------------\nSOURCE\nCurrent Sequence 26\nLast Archived Sequence 25\nLast Transferred Sequence 25\nLast Transferred Timestamp 2023-02-17 11:22:32\n\nDESTINATION\nNext Required Recovery Sequence 26\n\nTransfer Log Gap 0\nApply Log Gap 0\n\n=============================================================\ndbvctl ended on dbvisitvippri: Fri Feb 17 11:27:19 2023\n=============================================================\n<\/pre>\n<\/br>\n\n\n\n<p>Doing a relocate from the instance database to the other nodes will not be a problem for dbvisit even if we were having some gap. Why? Because&#8230;<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The FRA is on the shared storage, mandatory for both instances to have access to the same FRA<\/li>\n\n\n\n<li>Dbvisit archive log file system is also an ACFS shared file system<\/li>\n\n\n\n<li>Dbvisit software directory is also running on an ACFS shared file system<\/li>\n<\/ul>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,8,12]\">\nSQL&gt; show parameter db_recovery_file_dest\n\nNAME\t\t\t\t                         TYPE\t       VALUE\n------------------------------------ ----------- ------------------------------\ndb_recovery_file_dest\t\t             string\t     +RECO\ndb_recovery_file_dest_size\t         big integer 200G\n\noracle@dbioda02:\/home\/oracle\/ [DBISEHA] df -h \/u90\/app\/oracle\/dbvisit_arch\nFilesystem              Size  Used Avail Use% Mounted on\n\/dev\/asm\/dbvarclog-269   60G  767M   60G   2% \/u90\/app\/oracle\/dbvisit_arch\n\noracle@dbioda02:\/home\/oracle\/ [DBISEHA] df -h \/u01\/app\/dbvisit\nFilesystem            Size  Used Avail Use% Mounted on\n\/dev\/asm\/dbvisit-269  100G  1.3G   99G   2% \/u01\/app\/dbvisit\n<\/pre>\n<\/br>\n\n\n\n<p>We will test having an archive log gap between the primary and the standby with the Oracle SEHA failover.<\/p>\n\n\n\n<p>Relocate Oracle SEHA primary database to node 1, dbioda03:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,20]\">\n[root@dbioda02 ~]# odacli modify-database -in DBISEHA -g 1\n{\n  \"jobId\" : \"c38c2457-5849-4623-9e16-b5e1c75b4de1\",\n  \"status\" : \"Created\",\n  \"message\" : \"Modify database\",\n  \"reports\" : [ ],\n  \"createTimestamp\" : \"February 17, 2023 11:36:58 AM CET\",\n  \"resourceList\" : [ {\n    \"resourceId\" : \"bed8b9fb-214a-423e-b0e8-d8c084b45dd1\",\n    \"resourceType\" : \"DB\",\n    \"resourceNewType\" : null,\n    \"jobId\" : \"c38c2457-5849-4623-9e16-b5e1c75b4de1\",\n    \"updatedTime\" : \"February 17, 2023 11:36:58 AM CET\"\n  } ],\n  \"description\" : \"Modify database : DBISEHA\",\n  \"updatedTime\" : \"February 17, 2023 11:36:58 AM CET\",\n  \"jobType\" : \"\"\n}\n\n[root@dbioda02 ~]# odacli describe-job -i c38c2457-5849-4623-9e16-b5e1c75b4de1\n\nJob details\n----------------------------------------------------------------\n                     ID:  c38c2457-5849-4623-9e16-b5e1c75b4de1\n            Description:  Modify database : DBISEHA\n                 Status:  Success\n                Created:  February 17, 2023 11:36:58 AM CET\n                Message:  Modify database\n\nTask Name                                Start Time                          End Time                            Status\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\nRelocate database {DBISEHA}              February 17, 2023 11:36:59 AM CET   February 17, 2023 11:37:54 AM CET   Success\n<\/pre>\n<\/br>\n\n\n\n<p>Relocate the VIP, dbvisitvippri, on the node 1:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1]\">\noracle@dbioda02:\/home\/oracle\/ [DBISEHA] crsctl relocate resource dbvisitvippri -f\nCRS-2673: Attempting to stop 'dbvagentmanager' on 'dbioda02'\nCRS-2677: Stop of 'dbvagentmanager' on 'dbioda02' succeeded\nCRS-2673: Attempting to stop 'dbvisitvippri' on 'dbioda02'\nCRS-2677: Stop of 'dbvisitvippri' on 'dbioda02' succeeded\nCRS-2672: Attempting to start 'dbvisitvippri' on 'dbioda03'\nCRS-2676: Start of 'dbvisitvippri' on 'dbioda03' succeeded\nCRS-2672: Attempting to start 'dbvagentmanager' on 'dbioda03'\n[dbvagentmanager] Starting Dbvisit dbvagentmanagerSubmitted check for dbvagentmanager with result not running correctly, return 1\nCRS-2676: Start of 'dbvagentmanager' on 'dbioda03' succeeded\n<\/pre>\n<br>\n\n\n\n<p>I can check and confirm that the oracle instance, the vip and the Dbvisit process has been relocated from dbioda02 to dbioda03:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,4,7,10,13,16]\">\noracle@dbioda02:\/home\/oracle\/ [DBISEHA] ps -ef | grep [p]mon | grep -i dbiseha\noracle@dbioda02:\/home\/oracle\/ [DBISEHA]\n\noracle@dbioda02:\/home\/oracle\/ [DBISEHA] ip addr sh pubnet | grep 10.36.0.246\noracle@dbioda02:\/home\/oracle\/ [DBISEHA]\n\noracle@dbioda02:\/home\/oracle\/ [DBISEHA] ps -ef | grep [d]bv\noracle@dbioda02:\/home\/oracle\/ [DBISEHA]\n\noracle@dbioda03:\/home\/oracle\/ [DBISEHA] ps -ef | grep [p]mon | grep -i dbiseha\noracle   93947     1  0 11:37 ?        00:00:00 ora_pmon_DBISEHA\n\noracle@dbioda03:\/home\/oracle\/ [DBISEHA] ip addr sh pubnet | grep 10.36.0.246\n    inet 10.36.0.246\/24 brd 10.36.0.255 scope global secondary pubnet:3\n    \noracle@dbioda03:\/home\/oracle\/ [DBISEHA] ps -ef | grep [d]bv\noracle   23378     1  0 11:53 ?        00:00:00 \/u01\/app\/dbvisit\/standbymp\/bin\/dbvagentmanager service run\noracle   23514 23378  0 11:53 ?        00:00:00 \/u01\/app\/dbvisit\/standbymp\/bin\/dbvhelper -agentManagerId 2v7stu05tncsp -directorId 3pheqx762v9xr -hostAddress dbvisitvippri -natsAddress dbi-oda-x8 -natsPort 5533 -configurationType Oracle -helperProcessKey oracle:2v7stu05tncsp\n<\/pre>\n<br>\n\n\n\n<p>Instance is running on node 1 now:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,6]\">\noracle@dbioda02:\/home\/oracle\/ [DBISEHA] DBISEHA\n********* dbi services Ltd. *********\nSTATUS          : STOPPED\n*************************************\n\noracle@dbioda03:\/home\/oracle\/ [DBISEHA] DBISEHA\n********* dbi services Ltd. *********\nSTATUS                 : OPEN\nDB_UNIQUE_NAME         : DBISEHA\nOPEN_MODE              : READ WRITE\nLOG_MODE               : ARCHIVELOG\nDATABASE_ROLE          : PRIMARY\nFLASHBACK_ON           : NO\nFORCE_LOGGING          : YES\nVERSION                : 19.15.0.0.0\nCDB Enabled            : NO\n*************************************\n<\/pre>\n<br>\n\n\n\n<p>Let&#8217;s create a few archive logs:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,13,17,21]\">\noracle@dbioda03:\/home\/oracle\/ [DBISEHA] sqh\n\nSQL*Plus: Release 19.0.0.0.0 - Production on Fri Feb 17 13:16:55 2023\nVersion 19.15.0.0.0\n\nCopyright (c) 1982, 2022, Oracle.  All rights reserved.\n\n\nConnected to:\nOracle Database 19c Standard Edition 2 Release 19.0.0.0.0 - Production\nVersion 19.15.0.0.0\n\nSQL&gt; alter system archive log current;\n\nSystem altered.\n\nSQL&gt; \/\n\nSystem altered.\n\nSQL&gt; \/\n\nSystem altered.\n<\/pre>\n<br>\n\n\n\n<p>Send the new archive logs to the standby database:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1]\">\noracle@dbioda03:\/home\/oracle\/ [DBISEHA] \/u01\/app\/dbvisit\/standbymp\/oracle\/dbvctl -d DBISEHA\n=============================================================\nDbvisit Standby Database Technology (11.2.1_0_g8a57214c) (pid 53287)\ndbvctl started on dbvisitvippri: Fri Feb 17 13:18:32 2023\n=============================================================\n\n&gt;&gt;&gt; Obtaining information from standby database (RUN_INSPECT=Y)... done\n    Thread: 1 Archive log gap: 3. Transfer log gap: 3\n&gt;&gt;&gt; Transferring Log file(s) from DBISEHA on dbvisitvippri to dbi-oda-x8:\n\n    thread 1 sequence 26 (thread_1_seq_26.345.1129036623)... done\n    thread 1 sequence 27 (thread_1_seq_27.346.1129036627)... done\n    thread 1 sequence 28 (thread_1_seq_28.347.1129036629)... done\n\n=============================================================\ndbvctl ended on dbvisitvippri: Fri Feb 17 13:18:42 2023\n=============================================================\n<\/pre>\n<br>\n\n\n\n<p>Apply them on the standby database:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1]\">\noracle@dbi-oda-x8:\/home\/oracle\/ [DBISEHA] \/u01\/app\/dbvisit\/standbymp\/oracle\/dbvctl -d DBISEHA\n=============================================================\nDbvisit Standby Database Technology (11.2.1_0_g8a57214c) (pid 89786)\ndbvctl started on dbi-oda-x8: Fri Feb 17 13:19:21 2023\n=============================================================\n\n\n&gt;&gt;&gt; Applying Log file(s) from dbvisitvippri to DBISEHA on dbi-oda-x8:\n\n    thread 1 sequence 26 (1_26_1127209532.arc)... done\n    thread 1 sequence 27 (1_27_1127209532.arc)... done\n    thread 1 sequence 28 (1_28_1127209532.arc)... done\n    Last applied log(s):\n    thread 1 sequence 28\n\n    Next SCN required for recovery 3967784 generated at 2023-02-17:13:17:08 +01:00.\n    Next required log thread 1 sequence 29\n\n=============================================================\ndbvctl ended on dbi-oda-x8: Fri Feb 17 13:19:27 2023\n=============================================================\n<\/pre>\n<br>\n\n\n\n<p>Check transfer and apply gap:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,27,28]\">\noracle@dbioda03:\/home\/oracle\/ [DBISEHA] \/u01\/app\/dbvisit\/standbymp\/oracle\/dbvctl -d DBISEHA -i\n=============================================================\nDbvisit Standby Database Technology (11.2.1_0_g8a57214c) (pid 55244)\ndbvctl started on dbvisitvippri: Fri Feb 17 13:20:01 2023\n=============================================================\n\nDbvisit Standby log gap report for DBISEHA at 202302171320:\n-------------------------------------------------------------\nDescription       | SCN          | Timestamp\n-------------------------------------------------------------\nSource              3967925        2023-02-17:13:20:02 +01:00\nDestination         3967784        2023-02-17:13:17:08 +01:00\n\nStandby database time lag (DAYS-HH:MI:SS): +00:02:54\n\nReport for Thread 1\n-------------------\nSOURCE\nCurrent Sequence 29\nLast Archived Sequence 28\nLast Transferred Sequence 28\nLast Transferred Timestamp 2023-02-17 13:18:42\n\nDESTINATION\nNext Required Recovery Sequence 29\n\nTransfer Log Gap 0\nApply Log Gap 0\n\n=============================================================\ndbvctl ended on dbvisitvippri: Fri Feb 17 13:20:04 2023\n=============================================================\n<\/pre>\n<br>\n\n\n\n<p>I tested a switchover to dbi-oda-x8:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1]\">\noracle@dbioda03:\/home\/oracle\/ [DBISEHA] \/u01\/app\/dbvisit\/standbymp\/oracle\/dbvctl -d DBISEHA -o switchover\n=============================================================\nDbvisit Standby Database Technology (11.2.1_0_g8a57214c) (pid 58371)\ndbvctl started on dbvisitvippri: Fri Feb 17 13:21:39 2023\n=============================================================\n\n&gt;&gt;&gt; Starting Switchover between dbvisitvippri and dbi-oda-x8\n\nRunning pre-checks       ... done\n\n=&gt;Do you want to proceed with Graceful Switchover? [no]: yes\nYour input: 1\n\nIs this correct?  [Yes]:\nPre processing           ... done\nProcessing primary       ... done\nProcessing standby       ... done\nConverting standby       ... done\nConverting primary       ... done\nCompleting               ... done\nSynchronizing            ... done\nPost processing          ... done\n\n&gt;&gt;&gt; Graceful switchover completed.\n    Primary Database Server: dbi-oda-x8\n    Standby Database Server: dbvisitvippri\n\n&gt;&gt;&gt; Dbvisit Standby can be run as per normal:\n    dbvctl -d DBISEHA\n\nAs part of the Switchover process, the primary and standby controlfiles have been exchanged.Unless you are using RMAN catalog database, you may need to cross-check all backups and review RMAN settings using the SHOW ALL command on the new Primary\/Standby databases. Confirm the path set for the SNAPSHOT CONTROLFILE NAME TO setting is valid on both sides.\nPID:58371\nTRACE:58371_dbvctl_switchover_DBISEHA_202302171321.trc\n\n=============================================================\ndbvctl ended on dbvisitvippri: Fri Feb 17 13:29:11 2023\n=============================================================\n<\/pre>\n<br>\n\n\n\n<p>And after sending\/applying a few archive logs, I switchovered back:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1]\">\noracle@dbi-oda-x8:\/home\/oracle\/ [DBISEHA] \/u01\/app\/dbvisit\/standbymp\/oracle\/dbvctl -d DBISEHA -o switchover\n=============================================================\nDbvisit Standby Database Technology (11.2.1_0_g8a57214c) (pid 14235)\ndbvctl started on dbi-oda-x8: Fri Feb 17 13:31:22 2023\n=============================================================\n\n&gt;&gt;&gt; Starting Switchover between dbi-oda-x8 and dbvisitvippri\n\nRunning pre-checks       ... done\n\n=&gt;Do you want to proceed with Graceful Switchover? [no]: yes\nYour input: 1\n\nIs this correct?  [Yes]:\nPre processing           ... done\nProcessing primary       ... done\nProcessing standby       ... done\nConverting standby       ... done\nConverting primary       ... done\nCompleting               ... done\nSynchronizing            ... done\nPost processing          ... done\n\n&gt;&gt;&gt; Graceful switchover completed.\n    Primary Database Server: dbvisitvippri\n    Standby Database Server: dbi-oda-x8\n\n&gt;&gt;&gt; Dbvisit Standby can be run as per normal:\n    dbvctl -d DBISEHA\n\nAs part of the Switchover process, the primary and standby controlfiles have been exchanged.Unless you are using RMAN catalog database, you may need to cross-check all backups and review RMAN settings using the SHOW ALL command on the new Primary\/Standby databases. Confirm the path set for the SNAPSHOT CONTROLFILE NAME TO setting is valid on both sides.\nPID:14235\nTRACE:14235_dbvctl_switchover_DBISEHA_202302171331.trc\n\n=============================================================\ndbvctl ended on dbi-oda-x8: Fri Feb 17 13:39:30 2023\n=============================================================\n<\/pre>\n<br>\n\n\n\n<h2 class=\"wp-block-heading\">Oracle SEHA failover with active Dbvisit StandbyMP configuration running<\/h2>\n\n\n\n<p>Let&#8217;s try the automatic failover functionality from Oracle SEHA. Purpose will be to crash the active node 1, dbioda03, where the primary database is running.<\/p>\n\n\n\n<p>To recall, the primary database instance, the VIP and dbvisit processes are currently running on node dbioda03.<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,4,7,11,24,25,26,27]\">\noracle@dbioda03:\/home\/oracle\/ [DBISEHA] ps -ef | grep [p]mon | grep -i dbiseha\noracle   92866     1  0 13:38 ?        00:00:00 ora_pmon_DBISEHA\n\noracle@dbioda03:\/home\/oracle\/ [DBISEHA] ip addr sh pubnet | grep 10.36.0.246\n    inet 10.36.0.246\/24 brd 10.36.0.255 scope global secondary pubnet:3\n\noracle@dbioda03:\/home\/oracle\/ [DBISEHA] ps -ef | grep [d]bv\noracle   23378     1  0 11:53 ?        00:00:06 \/u01\/app\/dbvisit\/standbymp\/bin\/dbvagentmanager service run\noracle   23514 23378  0 11:53 ?        00:00:00 \/u01\/app\/dbvisit\/standbymp\/bin\/dbvhelper -agentManagerId 2v7stu05tncsp -directorId 3pheqx762v9xr -hostAddress dbvisitvippri -natsAddress dbi-oda-x8 -natsPort 5533 -configurationType Oracle -helperProcessKey oracle:2v7stu05tncsp\n\noracle@dbioda03:\/home\/oracle\/ [DBISEHA] DBISEHA\n********* dbi services Ltd. *********\nSTATUS                 : OPEN\nDB_UNIQUE_NAME         : DBISEHA\nOPEN_MODE              : READ WRITE\nLOG_MODE               : ARCHIVELOG\nDATABASE_ROLE          : PRIMARY\nFLASHBACK_ON           : NO\nFORCE_LOGGING          : YES\nVERSION                : 19.15.0.0.0\nCDB Enabled            : NO\n*************************************\n\noracle@dbioda02:\/home\/oracle\/ [DBISEHA] ps -ef | grep [p]mon | grep -i dbiseha\noracle@dbioda02:\/home\/oracle\/ [DBISEHA] ip addr sh pubnet | grep 10.36.0.246\noracle@dbioda02:\/home\/oracle\/ [DBISEHA] ps -ef | grep [d]bv\noracle@dbioda02:\/home\/oracle\/ [DBISEHA] DBISEHA\n********* dbi services Ltd. *********\nSTATUS          : STOPPED\n*************************************\n<\/pre>\n<br>\n\n\n\n<p>Let&#8217;s create a gap between primary and standby database:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,13,17,21]\">\noracle@dbioda03:\/home\/oracle\/ [DBISEHA] sqh\n\nSQL*Plus: Release 19.0.0.0.0 - Production on Fri Feb 17 13:49:36 2023\nVersion 19.15.0.0.0\n\nCopyright (c) 1982, 2022, Oracle.  All rights reserved.\n\n\nConnected to:\nOracle Database 19c Standard Edition 2 Release 19.0.0.0.0 - Production\nVersion 19.15.0.0.0\n\nSQL&gt; alter system archive log current;\n\nSystem altered.\n\nSQL&gt; \/\n\nSystem altered.\n\nSQL&gt; \/\n\nSystem altered.\n<\/pre>\n<br>\n\n\n\n<p>We can see that the last created archive log file have neither been transferred nor applied on the standby database:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,27,28]\">\noracle@dbioda03:\/home\/oracle\/ [DBISEHA] \/u01\/app\/dbvisit\/standbymp\/oracle\/dbvctl -d DBISEHA -i\n=============================================================\nDbvisit Standby Database Technology (11.2.1_0_g8a57214c) (pid 16473)\ndbvctl started on dbvisitvippri: Fri Feb 17 13:50:02 2023\n=============================================================\n\nDbvisit Standby log gap report for DBISEHA at 202302171350:\n-------------------------------------------------------------\nDescription       | SCN          | Timestamp\n-------------------------------------------------------------\nSource              3975799        2023-02-17:13:50:02 +01:00\nDestination         3975504        2023-02-17:13:42:22 +01:00\n\nStandby database time lag (DAYS-HH:MI:SS): +00:07:40\n\nReport for Thread 1\n-------------------\nSOURCE\nCurrent Sequence 50\nLast Archived Sequence 49\nLast Transferred Sequence 46\nLast Transferred Timestamp 2023-02-17 13:42:37\n\nDESTINATION\nNext Required Recovery Sequence 47\n\nTransfer Log Gap 3\nApply Log Gap 3\n\n=============================================================\ndbvctl ended on dbvisitvippri: Fri Feb 17 13:50:05 2023\n=============================================================\n<\/pre>\n<br>\n\n\n\n<p>Let&#8217;s crash ODA X5-2-HA node 1, dbioda03, running the primary database instance:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,4]\">\n[root@dbioda03 ~]# date\nFri Feb 17 13:53:52 CET 2023\n\n[root@dbioda03 ~]# systemctl poweroff\nConnection to 10.36.0.233 closed by remote host.\nConnection to 10.36.0.233 closed.\n<\/pre>\n<br>\n\n\n\n<p>Very quickly, about one minute later, I can see that the instance of oracle SEHA database, DBISEHA, got automatically failovered on node 0, dbioda02. The VIP, dbvisitvippri, has been also automatically relocated on node 0. The implemented dbvagentmanager script has automatically started, with the VIP relocation, the needed dbvisit processes.<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,4,7,10,14]\">\noracle@dbioda02:\/home\/oracle\/ [DBISEHA] date\nFri Feb 17 13:55:07 CET 2023\n\noracle@dbioda02:\/home\/oracle\/ [DBISEHA] ps -ef | grep [p]mon | grep -i dbiseha\noracle   31132     1  0 13:54 ?        00:00:00 ora_pmon_DBISEHA\n\noracle@dbioda02:\/home\/oracle\/ [DBISEHA] ip addr sh pubnet | grep 10.36.0.246\n    inet 10.36.0.246\/24 brd 10.36.0.255 scope global secondary pubnet:2\n    \noracle@dbioda02:\/home\/oracle\/ [DBISEHA] ps -ef | grep [d]bv\noracle   30423     1  0 13:54 ?        00:00:00 \/u01\/app\/dbvisit\/standbymp\/bin\/dbvagentmanager service run\noracle   30496 30423  0 13:54 ?        00:00:00 \/u01\/app\/dbvisit\/standbymp\/bin\/dbvhelper -agentManagerId 2v7stu05tncsp -directorId 3pheqx762v9xr -hostAddress dbvisitvippri -natsAddress dbi-oda-x8 -natsPort 5533 -configurationType Oracle -helperProcessKey oracle:2v7stu05tncsp\n\noracle@dbioda02:\/home\/oracle\/ [DBISEHA] DBISEHA\n********* dbi services Ltd. *********\nSTATUS                 : OPEN\nDB_UNIQUE_NAME         : DBISEHA\nOPEN_MODE              : READ WRITE\nLOG_MODE               : ARCHIVELOG\nDATABASE_ROLE          : PRIMARY\nFLASHBACK_ON           : NO\nFORCE_LOGGING          : YES\nVERSION                : 19.15.0.0.0\nCDB Enabled            : NO\n*************************************\n<\/pre>\n<br>\n\n\n\n<p>All seems ok and our Dbvisit configuration should go on working.<\/p>\n\n\n\n<p>We still have our 3 archive log gap, plus one additional following the instance failover:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,27,28]\">\noracle@dbioda02:\/home\/oracle\/ [DBISEHA] \/u01\/app\/dbvisit\/standbymp\/oracle\/dbvctl -d DBISEHA -i\n=============================================================\nDbvisit Standby Database Technology (11.2.1_0_g8a57214c) (pid 51716)\ndbvctl started on dbvisitvippri: Fri Feb 17 14:04:16 2023\n=============================================================\n\nDbvisit Standby log gap report for DBISEHA at 202302171404:\n-------------------------------------------------------------\nDescription       | SCN          | Timestamp\n-------------------------------------------------------------\nSource              4077647        2023-02-17:14:04:18 +01:00\nDestination         3975504        2023-02-17:13:42:22 +01:00\n\nStandby database time lag (DAYS-HH:MI:SS): +00:21:56\n\nReport for Thread 1\n-------------------\nSOURCE\nCurrent Sequence 51\nLast Archived Sequence 50\nLast Transferred Sequence 46\nLast Transferred Timestamp 2023-02-17 13:42:37\n\nDESTINATION\nNext Required Recovery Sequence 47\n\nTransfer Log Gap 4\nApply Log Gap 4\n\n=============================================================\ndbvctl ended on dbvisitvippri: Fri Feb 17 14:04:20 2023\n=============================================================\n<\/pre>\n<br>\n\n\n\n<p>We can ship these 4 archive logs to the standby side:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1]\">\noracle@dbioda02:\/home\/oracle\/ [DBISEHA] \/u01\/app\/dbvisit\/standbymp\/oracle\/dbvctl -d DBISEHA\n=============================================================\nDbvisit Standby Database Technology (11.2.1_0_g8a57214c) (pid 56938)\ndbvctl started on dbvisitvippri: Fri Feb 17 14:05:32 2023\n=============================================================\n\n&gt;&gt;&gt; Obtaining information from standby database (RUN_INSPECT=Y)... done\n    Thread: 1 Archive log gap: 4. Transfer log gap: 4\n&gt;&gt;&gt; Transferring Log file(s) from DBISEHA on dbvisitvippri to dbi-oda-x8:\n\n    thread 1 sequence 47 (thread_1_seq_47.359.1129038579)... done\n    thread 1 sequence 48 (thread_1_seq_48.360.1129038581)... done\n    thread 1 sequence 49 (thread_1_seq_49.361.1129038583)... done\n    thread 1 sequence 50 (thread_1_seq_50.365.1129038891)... done\n\n=============================================================\ndbvctl ended on dbvisitvippri: Fri Feb 17 14:05:43 2023\n=============================================================\n<\/pre>\n<br>\n\n\n\n<p>Apply them on the standby side:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1]\">\noracle@dbi-oda-x8:\/home\/oracle\/ [DBISEHA] \/u01\/app\/dbvisit\/standbymp\/oracle\/dbvctl -d DBISEHA\n=============================================================\nDbvisit Standby Database Technology (11.2.1_0_g8a57214c) (pid 68994)\ndbvctl started on dbi-oda-x8: Fri Feb 17 14:06:18 2023\n=============================================================\n\n\n&gt;&gt;&gt; Applying Log file(s) from dbvisitvippri to DBISEHA on dbi-oda-x8:\n\n    thread 1 sequence 47 (1_47_1127209532.arc)... done\n    thread 1 sequence 48 (1_48_1127209532.arc)... done\n    thread 1 sequence 49 (1_49_1127209532.arc)... done\n    thread 1 sequence 50 (1_50_1127209532.arc)... done\n    Last applied log(s):\n    thread 1 sequence 50\n\n    Next SCN required for recovery 4076181 generated at 2023-02-17:13:54:50 +01:00.\n    Next required log thread 1 sequence 51\n\n=============================================================\ndbvctl ended on dbi-oda-x8: Fri Feb 17 14:06:24 2023\n=============================================================\n<\/pre>\n<br>\n\n\n\n<p>And confirm both primary and standby are in sync:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,27,28]\">\noracle@dbioda02:\/home\/oracle\/ [DBISEHA] \/u01\/app\/dbvisit\/standbymp\/oracle\/dbvctl -d DBISEHA -i\n=============================================================\nDbvisit Standby Database Technology (11.2.1_0_g8a57214c) (pid 59910)\ndbvctl started on dbvisitvippri: Fri Feb 17 14:07:06 2023\n=============================================================\n\nDbvisit Standby log gap report for DBISEHA at 202302171407:\n-------------------------------------------------------------\nDescription       | SCN          | Timestamp\n-------------------------------------------------------------\nSource              4077849        2023-02-17:14:07:06 +01:00\nDestination         4076181        2023-02-17:13:54:50 +01:00\n\nStandby database time lag (DAYS-HH:MI:SS): +00:12:16\n\nReport for Thread 1\n-------------------\nSOURCE\nCurrent Sequence 51\nLast Archived Sequence 50\nLast Transferred Sequence 50\nLast Transferred Timestamp 2023-02-17 14:05:43\n\nDESTINATION\nNext Required Recovery Sequence 51\n\nTransfer Log Gap 0\nApply Log Gap 0\n\n=============================================================\ndbvctl ended on dbvisitvippri: Fri Feb 17 14:07:09 2023\n=============================================================\n<\/pre>\n<br>\n\n\n\n<h2 class=\"wp-block-heading\">Summary<\/h2>\n\n\n\n<p>I could successfully test Dbvisit StandbyMP configured with Oracle SEHA database, running switchover, relocate and automatic failover. After a relocate of the Oracle SEHA instance and a relocate of the VIP used with Dbvisit, Dbvisit configuration could work properly, included switchover. Crashing the node running the Oracle SEHA instance, we could see that the oracle database instance has been automatically relocated to the other node as well as the VIP used for Dbvisit configuration. The system was immediately ready to move forward and sync with the other disaster recover cluster node.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I recently wrote an article about how to combine Oracle SEHA database running on ODA 2-HA and dbvisit StandbyMP solution. See my article here : https:\/\/www.dbi-services.com\/blog\/combine-oracle-seha-on-oda-with-dbvisit-standbymp\/. But are really all those high availability and disaster recovering solutions working together? Do Oracle SEHA relocate and failover functionalities work in conjunction with dbvisit StandbyMP switchover? Let&#8217;s see [&hellip;]<\/p>\n","protected":false},"author":48,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[59],"tags":[372,871,79,2848],"type_dbi":[],"class_list":["post-22654","post","type-post","status-publish","format-standard","hentry","category-oracle","tag-dbvisit","tag-ha","tag-oda","tag-oracle-seha"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.2 (Yoast SEO v27.2) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Can we benefit from Oracle SEHA relocate and failover with dbvisit StandbyMP switchover? - dbi Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/can-we-benefit-from-oracle-seha-relocate-and-failover-with-dbvisit-standbymp-switchover\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Can we benefit from Oracle SEHA relocate and failover with dbvisit StandbyMP switchover?\" \/>\n<meta property=\"og:description\" content=\"I recently wrote an article about how to combine Oracle SEHA database running on ODA 2-HA and dbvisit StandbyMP solution. See my article here : https:\/\/www.dbi-services.com\/blog\/combine-oracle-seha-on-oda-with-dbvisit-standbymp\/. But are really all those high availability and disaster recovering solutions working together? Do Oracle SEHA relocate and failover functionalities work in conjunction with dbvisit StandbyMP switchover? Let&#8217;s see [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/can-we-benefit-from-oracle-seha-relocate-and-failover-with-dbvisit-standbymp-switchover\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2023-02-17T13:25:08+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2023-02-17T13:27:47+00:00\" \/>\n<meta name=\"author\" content=\"Marc Wagner\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Marc Wagner\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"17 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/can-we-benefit-from-oracle-seha-relocate-and-failover-with-dbvisit-standbymp-switchover\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/can-we-benefit-from-oracle-seha-relocate-and-failover-with-dbvisit-standbymp-switchover\/\"},\"author\":{\"name\":\"Marc Wagner\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628\"},\"headline\":\"Can we benefit from Oracle SEHA relocate and failover with dbvisit StandbyMP switchover?\",\"datePublished\":\"2023-02-17T13:25:08+00:00\",\"dateModified\":\"2023-02-17T13:27:47+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/can-we-benefit-from-oracle-seha-relocate-and-failover-with-dbvisit-standbymp-switchover\/\"},\"wordCount\":853,\"commentCount\":0,\"keywords\":[\"dbvisit\",\"HA\",\"ODA\",\"Oracle SEHA\"],\"articleSection\":[\"Oracle\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/can-we-benefit-from-oracle-seha-relocate-and-failover-with-dbvisit-standbymp-switchover\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/can-we-benefit-from-oracle-seha-relocate-and-failover-with-dbvisit-standbymp-switchover\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/can-we-benefit-from-oracle-seha-relocate-and-failover-with-dbvisit-standbymp-switchover\/\",\"name\":\"Can we benefit from Oracle SEHA relocate and failover with dbvisit StandbyMP switchover? - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2023-02-17T13:25:08+00:00\",\"dateModified\":\"2023-02-17T13:27:47+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/can-we-benefit-from-oracle-seha-relocate-and-failover-with-dbvisit-standbymp-switchover\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/can-we-benefit-from-oracle-seha-relocate-and-failover-with-dbvisit-standbymp-switchover\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/can-we-benefit-from-oracle-seha-relocate-and-failover-with-dbvisit-standbymp-switchover\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Can we benefit from Oracle SEHA relocate and failover with dbvisit StandbyMP switchover?\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628\",\"name\":\"Marc Wagner\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/a873cc6e7fbdbbcbdbcaf5dbded14ad9a77b2ec2c3e03b4d724ed33d35d5f328?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/a873cc6e7fbdbbcbdbcaf5dbded14ad9a77b2ec2c3e03b4d724ed33d35d5f328?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/a873cc6e7fbdbbcbdbcaf5dbded14ad9a77b2ec2c3e03b4d724ed33d35d5f328?s=96&d=mm&r=g\",\"caption\":\"Marc Wagner\"},\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/marc-wagner\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Can we benefit from Oracle SEHA relocate and failover with dbvisit StandbyMP switchover? - dbi Blog","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:\/\/www.dbi-services.com\/blog\/can-we-benefit-from-oracle-seha-relocate-and-failover-with-dbvisit-standbymp-switchover\/","og_locale":"en_US","og_type":"article","og_title":"Can we benefit from Oracle SEHA relocate and failover with dbvisit StandbyMP switchover?","og_description":"I recently wrote an article about how to combine Oracle SEHA database running on ODA 2-HA and dbvisit StandbyMP solution. See my article here : https:\/\/www.dbi-services.com\/blog\/combine-oracle-seha-on-oda-with-dbvisit-standbymp\/. But are really all those high availability and disaster recovering solutions working together? Do Oracle SEHA relocate and failover functionalities work in conjunction with dbvisit StandbyMP switchover? Let&#8217;s see [&hellip;]","og_url":"https:\/\/www.dbi-services.com\/blog\/can-we-benefit-from-oracle-seha-relocate-and-failover-with-dbvisit-standbymp-switchover\/","og_site_name":"dbi Blog","article_published_time":"2023-02-17T13:25:08+00:00","article_modified_time":"2023-02-17T13:27:47+00:00","author":"Marc Wagner","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Marc Wagner","Est. reading time":"17 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/can-we-benefit-from-oracle-seha-relocate-and-failover-with-dbvisit-standbymp-switchover\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/can-we-benefit-from-oracle-seha-relocate-and-failover-with-dbvisit-standbymp-switchover\/"},"author":{"name":"Marc Wagner","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628"},"headline":"Can we benefit from Oracle SEHA relocate and failover with dbvisit StandbyMP switchover?","datePublished":"2023-02-17T13:25:08+00:00","dateModified":"2023-02-17T13:27:47+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/can-we-benefit-from-oracle-seha-relocate-and-failover-with-dbvisit-standbymp-switchover\/"},"wordCount":853,"commentCount":0,"keywords":["dbvisit","HA","ODA","Oracle SEHA"],"articleSection":["Oracle"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/can-we-benefit-from-oracle-seha-relocate-and-failover-with-dbvisit-standbymp-switchover\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/can-we-benefit-from-oracle-seha-relocate-and-failover-with-dbvisit-standbymp-switchover\/","url":"https:\/\/www.dbi-services.com\/blog\/can-we-benefit-from-oracle-seha-relocate-and-failover-with-dbvisit-standbymp-switchover\/","name":"Can we benefit from Oracle SEHA relocate and failover with dbvisit StandbyMP switchover? - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2023-02-17T13:25:08+00:00","dateModified":"2023-02-17T13:27:47+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/can-we-benefit-from-oracle-seha-relocate-and-failover-with-dbvisit-standbymp-switchover\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/can-we-benefit-from-oracle-seha-relocate-and-failover-with-dbvisit-standbymp-switchover\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/can-we-benefit-from-oracle-seha-relocate-and-failover-with-dbvisit-standbymp-switchover\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Can we benefit from Oracle SEHA relocate and failover with dbvisit StandbyMP switchover?"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628","name":"Marc Wagner","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/a873cc6e7fbdbbcbdbcaf5dbded14ad9a77b2ec2c3e03b4d724ed33d35d5f328?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/a873cc6e7fbdbbcbdbcaf5dbded14ad9a77b2ec2c3e03b4d724ed33d35d5f328?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/a873cc6e7fbdbbcbdbcaf5dbded14ad9a77b2ec2c3e03b4d724ed33d35d5f328?s=96&d=mm&r=g","caption":"Marc Wagner"},"url":"https:\/\/www.dbi-services.com\/blog\/author\/marc-wagner\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/22654","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/48"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=22654"}],"version-history":[{"count":27,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/22654\/revisions"}],"predecessor-version":[{"id":22713,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/22654\/revisions\/22713"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=22654"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=22654"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=22654"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=22654"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}