{"id":30032,"date":"2023-12-31T14:26:26","date_gmt":"2023-12-31T13:26:26","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=30032"},"modified":"2023-12-31T14:26:28","modified_gmt":"2023-12-31T13:26:28","slug":"dbvisit-standbymp-with-oracle-se2-switchover-error-with-ora-27125","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/dbvisit-standbymp-with-oracle-se2-switchover-error-with-ora-27125\/","title":{"rendered":"dbvisit StandbyMP with Oracle SE2 \u2013 switchover error with ORA-27125"},"content":{"rendered":"\n<p>After having recently deployed a new customer system running Oracle SE2 databases in Disaster Recovery environment using dbvisit StandbyMP v11.4.1 on Oracle Linux 8.8, I did some final test running a switchover. The switchover failed with following error:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>ORA-27125: unable to create shared memory segment<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-problem-description\">Problem description<\/h2>\n\n\n\n<p>Running switchover command was failing:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,12,15,17,20]\">\noracle@srv01:~\/ [MYDB] \/u01\/app\/dbvisit\/standbymp\/oracle\/dbvctl -d MYDB -o switchover\n=============================================================\nDbvisit Standby Database Technology (11.4.1) (pid 9997)\ndbvctl started on srv01: Thu Dec 14 11:48:41 2023\n=============================================================\n\n&gt;&gt;&gt; Starting Switchover between srv01 and srv02\n\nRunning pre-checks       ... done\n\n=&gt;Enter Custom User Script to run after Switchover is complete on srv01\n(leave blank for no script): []:\n\n=&gt;Enter Custom User Script to run after Switchover is complete on srv02\n(leave blank for no script): []:\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       ... failed\nRolling back Primary     ... done\nRolling back Standby     ... failed\n\n&gt;&gt;&gt; Database on server srv01 is still a Primary Database\n&gt;&gt;&gt; Database on server srv02 is in unknown state\n\n\n&lt;&lt;&lt;&gt;&gt;&gt;\n\nPID:9997\nTRACEFILE:9997_dbvctl_switchover_MYDB_202312141148.trc\n&gt;&gt;&gt;&gt; Dbvisit Standby terminated &lt;&lt;&lt;&lt;\n<\/pre>\n<\/br>\n\n\n\n<p>Looking in the appropriate log, I could find Oracle error:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,23,24]\">\noracle@srv01:\/u01\/app\/dbvisit\/standbymp\/oracle\/trace\/ [MYDB] cat 9997_dbvctl_switchover_MYDB_202312141148.trc\n...\n...\n...\n117978 20231214 11:50:39 main::UTIL_rsh_cmd: command:\"\/u01\/app\/dbvisit\/standbymp\/oracle\/dbvctl\" -d MYDB -f gs_process_standby   --show_trace\n117979 20231214 11:50:39 main::UTIL_rsh_cmd: noerror=\n117979 20231214 11:50:39 main::UTIL_run_command: ORACLE_HOME:     \/u01\/app\/oracle\/product\/19_20_0_0_RU230718_v0\n117979 20231214 11:50:39 main::UTIL_run_command: PATH:            \/usr\/local\/bin:\/bin:\/usr\/bin:\/usr\/X11R6\/bin:\/usr\/sbin:\/sbin:\/u01\/app\/oracle\/product\/19_20_0_0_RU230718_v0\/bin\n117979 20231214 11:50:39 main::UTIL_run_command: LD_LIBRARY_PATH: \/u01\/app\/dbvisit\/standbymp\/oracle\/lib:\/u01\/app\/oracle\/product\/19_20_0_0_RU230718_v0\/lib\n117979 20231214 11:50:39 main::UTIL_run_command: \"\/u01\/app\/dbvisit\/standbymp\/dbvnet\/dbvnet\" -c \"\/u01\/app\/dbvisit\/standbymp\/dbvnet\/conf\/dbvnetd.conf\" -a srv02 -p 7890 -e \"\\\"\/u01\/app\/dbvisit\/standbymp\/oracle\/dbvctl\\\" -d MYDB -f gs_process_standby   --show_trace \" 2&gt;&amp;1\n117979 20231214 11:50:39 main::UTIL_run_command: noerror=1\n123500 20231214 11:50:45 main::UTIL_run_command: return_code=256\n123500 20231214 11:50:45 main::UTIL_run_command: ===&gt;command output start\n123500 20231214 11:50:45 main::UTIL_run_command: DBVISIT_TRACEFILE=\/u01\/app\/dbvisit\/standbymp\/oracle\/trace\/235662_18_dbvctl_f_gs_process_standby_MYDB_202312141150.trc\n123500 20231214 11:50:45 main::UTIL_run_command:\n123500 20231214 11:50:45 main::UTIL_run_command: &lt;&lt;&lt;&gt;&gt;&gt;\n123500 20231214 11:50:45 main::UTIL_run_command:\n123500 20231214 11:50:45 main::UTIL_run_command: PID:235662\n123500 20231214 11:50:45 main::UTIL_run_command: TRACEFILE:235662_18_dbvctl_f_gs_process_standby_MYDB_202312141150.trc\n123500 20231214 11:50:45 main::UTIL_run_command: SERVER:srv02\n123501 20231214 11:50:45 main::UTIL_run_command: ERROR_CODE:8002\n123501 20231214 11:50:45 main::UTIL_run_command: Error executing RMAN command.\n123501 20231214 11:50:45 main::UTIL_run_command: RMAN-03002: failure of startup command at 12\/14\/2023 11:50:45\n123501 20231214 11:50:45 main::UTIL_run_command: RMAN-04014: startup failed: ORA-27125: unable to create shared memory segment\n123501 20231214 11:50:45 main::UTIL_run_command: Linux-x86_64 Error: 1: Operation not permitted\n123501 20231214 11:50:45 main::UTIL_run_command: See tracefile for details\n123501 20231214 11:50:45 main::UTIL_run_command: &gt;&gt;&gt;&gt; Dbvisit Standby terminated &lt;&lt;&lt;command output end\n123501 20231214 11:50:45 main::cmn_extract_trace_name: tracefile=\/u01\/app\/dbvisit\/standbymp\/oracle\/trace\/235662_18_dbvctl_f_gs_process_standby_MYDB_202312141150.trc\n(remote)\n123501 20231214 11:50:45 main::UTIL_rsh_cmd: ===&gt;source_output start\n123501 20231214 11:50:45 main::UTIL_rsh_cmd:\n123501 20231214 11:50:45 main::UTIL_rsh_cmd: &lt;&lt;&lt;&gt;&gt;&gt;\n...\n...\n...\n<\/pre>\n<\/br>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-troubleshooting\">Troubleshooting<\/h2>\n\n\n\n<p>It seems that when dbvisit wanted to start the standby database it could not get enough available shared memory from the hugepages, albeit everything is ok on the OS configuration side. Stopping and starting both primary and standby databases manually with sqlplus tool works perfectly. <\/p>\n\n\n\n<p>Oracle Linux limits are configured for Oracle user when running Oracle Preinstallation RPM. Resource Limits can also be checked in following oracle documentation : <a href=\"https:\/\/docs.oracle.com\/en\/database\/oracle\/oracle-database\/19\/ladbi\/checking-resource-limits-for-oracle-software-installation-users.html#GUID-293874BD-8069-470F-BEBF-A77C06618D5A\">https:\/\/docs.oracle.com\/en\/database\/oracle\/oracle-database\/19\/ladbi<\/a><a href=\"https:\/\/docs.oracle.com\/en\/database\/oracle\/oracle-database\/19\/ladbi\/checking-resource-limits-for-oracle-software-installation-users.html#GUID-293874BD-8069-470F-BEBF-A77C06618D5A\" target=\"_blank\" rel=\"noreferrer noopener\">\/<\/a><a href=\"https:\/\/docs.oracle.com\/en\/database\/oracle\/oracle-database\/19\/ladbi\/checking-resource-limits-for-oracle-software-installation-users.html#GUID-293874BD-8069-470F-BEBF-A77C06618D5A\">checking-resource-limits-for-oracle-software-installation-users.html#GUID-293874BD-8069-470F-BEBF-A77C06618D5A<\/a><\/p>\n\n\n\n<p>Checking system limits for Oracle user as per the soft and hard limits for the open file descriptors (resource nofile) seemed ok :<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,4]\">\noracle@srv01:~\/ [rdbms1900] ulimit -Sn\n1024\n\noracle@srv01:~\/ [rdbms1900] ulimit -Hn\n65536\n<\/pre>\n<\/br>\n\n\n\n<p>Checking system limits for Oracle user as per the soft and hard limits for the number of processes available to a single user (resource nproc) seemed ok:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,4]\">\noracle@srv01:~\/ [rdbms1900] ulimit -Su\n16384\n\noracle@srv01:~\/ [rdbms1900] ulimit -Hu\n16384\n<\/pre>\n<\/br>\n\n\n\n<p>Checking system limits for Oracle user as per the soft limit for the size of the stack segment of the process (resource stack) seemed ok:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,4]\">\noracle@srv01:~\/ [rdbms1900] ulimit -Ss\n10240\n\noracle@srv01:~\/ [rdbms1900] ulimit -Hs\n32768\n<\/pre>\n<\/br>\n\n\n\n<p>Checking system limits for Oracle user as per the soft and hard limit for maximum locked memory limit (resource memlock) seemed ok:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,4,7]\">\noracle@srv01:~\/ [rdbms1900] ulimit -Sl\n134217728\n\noracle@srv01:~\/ [rdbms1900] ulimit -Hl\n134217728\n\noracle@srv01:~\/ [rdbms1900] grep memlock \/etc\/security\/limits.conf\n#        - memlock - max locked-in-memory address space (KB)\noracle          soft     memlock         38797312\noracle          hard     memlock         38797312\n<\/pre>\n<\/br>\n\n\n\n<p>The memlock limit for Oracle user configured in limits.conf file is 38797312 KB which makes 37 GB.<\/p>\n\n\n\n<p>The memlock limit we can see for Oracle user with ulimit command is 134217728 KB which makes 128 GB. This might be an unlimited configuration.<\/p>\n\n\n\n<p>In any case we are all good with all those limits. By the way, we could have seen all those limits with one command:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1]\">\noracle@bvboracle01:~\/ [rdbms1900] ulimit -a\ncore file size          (blocks, -c) 0\ndata seg size           (kbytes, -d) unlimited\nscheduling priority             (-e) 0\nfile size               (blocks, -f) unlimited\npending signals                 (-i) 255582\nmax locked memory       (kbytes, -l) 134217728\nmax memory size         (kbytes, -m) unlimited\nopen files                      (-n) 1024\npipe size            (512 bytes, -p) 8\nPOSIX message queues     (bytes, -q) 819200\nreal-time priority              (-r) 0\nstack size              (kbytes, -s) 10240\ncpu time               (seconds, -t) unlimited\nmax user processes              (-u) 16384\nvirtual memory          (kbytes, -v) unlimited\nfile locks                      (-x) unlimited\n<\/pre>\n<\/br>\n\n\n\n<p>So the problem might more come from dbvagentmanager which could not get the system limits configured in \/etc\/security\/limits.conf when starting.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-solution\">Solution<\/h2>\n\n\n\n<p>dbvagentmanager systemctl service has been created as per the installation guide as following:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,3,5,8,10]\">\n[root@srv01 ~]# systemctl list-units --type=service | grep -i dbv\n\n[root@srv01 ~]# \/u01\/app\/dbvisit\/standbymp\/bin\/dbvagentmanager service install --user oracle\n\n[root@srv01 ~]# systemctl list-units --type=service | grep -i dbv\ndbvagentmanager.service                               loaded activating auto-restart The Dbvisit StandbyMP Agent provides connectivity to databases on this computer. This Agent is used &amp; managed by the Dbvisit StandbyMP Control Center.\n\n[root@srv01 ~]# \/u01\/app\/dbvisit\/standbymp\/bin\/dbvagentmanager service start\n\n[root@srv01 ~]# ps -ef | grep [d]bv\noracle      4000       1  0 15:38 ?        00:00:00 \/u01\/app\/dbvisit\/standbymp\/bin\/dbvagentmanager service run\n<\/pre>\n<\/br>\n\n\n\n<p>I then decided to add following limits in the dbvagentmanager service itself:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>LimitNOFILE=65536<\/li>\n\n\n\n<li>LimitNPROC=16384<\/li>\n\n\n\n<li>LimitMEMLOCK=infinity<\/li>\n<\/ul>\n\n\n\n<p>On both primary and standby servers, I updated accordingly systemctl dbvagentmanager service:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,2,5,31,33,54,55,56]\">\n[root@srv01 ~]# sudo systemctl stop dbvagentmanager\n[root@srv01 ~]# sudo systemctl disable dbvagentmanager\nRemoved \/etc\/systemd\/system\/multi-user.target.wants\/dbvagentmanager.service.\n\n[root@srv01 ~]# cat \/etc\/systemd\/system\/dbvagentmanager.service\n[Unit]\nDescription=The Dbvisit StandbyMP Agent provides connectivity to databases on this computer. This Agent is used &amp; managed by the Dbvisit StandbyMP Control Center.\nConditionFileIsExecutable=\/u01\/app\/dbvisit\/standbymp\/bin\/dbvagentmanager\n\n\n[Service]\nStartLimitInterval=5\nStartLimitBurst=10\nExecStart=\/u01\/app\/dbvisit\/standbymp\/bin\/dbvagentmanager \"service\" \"run\"\n\n\nUser=oracle\n\n\n\n\nRestart=always\n\nKillMode=process\nRestartSec=120\nEnvironmentFile=-\/etc\/sysconfig\/dbvagentmanager\n\n[Install]\nWantedBy=multi-user.target\n\n[root@srv01 ~]# vi \/etc\/systemd\/system\/dbvagentmanager.serviceagentmanager.service\n\n[root@srv01 ~]# cat \/etc\/systemd\/system\/dbvagentmanager.service\n[Unit]\nDescription=The Dbvisit StandbyMP Agent provides connectivity to databases on this computer. This Agent is used &amp; managed by the Dbvisit StandbyMP Control Center.\nConditionFileIsExecutable=\/u01\/app\/dbvisit\/standbymp\/bin\/dbvagentmanager\n\n[Service]\nStartLimitInterval=5\nStartLimitBurst=10\nExecStart=\/u01\/app\/dbvisit\/standbymp\/bin\/dbvagentmanager \"service\" \"run\"\nUser=oracle\nRestart=always\nKillMode=process\nRestartSec=120\nEnvironmentFile=-\/etc\/sysconfig\/dbvagentmanager\nLimitNOFILE=65536\nLimitNPROC=16384\nLimitMEMLOCK=infinity\n\n[Install]\nWantedBy=multi-user.target\n\n[root@srv01 ~]# sudo systemctl daemon-reload\n[root@srv01 ~]# sudo systemctl start dbvagentmanager\n[root@srv01 ~]# sudo systemctl enable dbvagentmanager\nCreated symlink \/etc\/systemd\/system\/multi-user.target.wants\/dbvagentmanager.service \u2192 \/etc\/systemd\/system\/dbvagentmanager.service.\n<\/pre>\n<\/br>\n\n\n\n<p>I could find the same explanation on a dbvisit support article for similar problem when creating the Oracle standby database with dbvisit : <a href=\"https:\/\/support.dbvisit.com\/hc\/en-us\/articles\/6488001083023-CSD-fails-with-RMAN-04014-startup-failed-ORA-27125-unable-to-create-shared-memory-segment-\">https:\/\/support.dbvisit.com\/hc\/en-us\/articles\/6488001083023-CSD-<\/a><a href=\"https:\/\/support.dbvisit.com\/hc\/en-us\/articles\/6488001083023-CSD-fails-with-RMAN-04014-startup-failed-ORA-27125-unable-to-create-shared-memory-segment-\" target=\"_blank\" rel=\"noreferrer noopener\">fails<\/a><a href=\"https:\/\/support.dbvisit.com\/hc\/en-us\/articles\/6488001083023-CSD-fails-with-RMAN-04014-startup-failed-ORA-27125-unable-to-create-shared-memory-segment-\">-with-RMAN-04014-startup-failed-ORA-<\/a><a href=\"https:\/\/support.dbvisit.com\/hc\/en-us\/articles\/6488001083023-CSD-fails-with-RMAN-04014-startup-failed-ORA-27125-unable-to-create-shared-memory-segment-\" target=\"_blank\" rel=\"noreferrer noopener\">27125<\/a><a href=\"https:\/\/support.dbvisit.com\/hc\/en-us\/articles\/6488001083023-CSD-fails-with-RMAN-04014-startup-failed-ORA-27125-unable-to-create-shared-memory-segment-\">-unable-to-create-shared-memory-segment-<\/a><\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-final-switchover-test\">Final switchover test<\/h2>\n\n\n\n<p>And I could finally run successfully the switchover:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,12,16,17]\">\noracle@srv01:~\/ [MYDB] \/u01\/app\/dbvisit\/standbymp\/oracle\/dbvctl -d MYDB -o switchover\n=============================================================\nDbvisit Standby Database Technology (11.4.1) (pid 12677)\ndbvctl started on srv01: Thu Dec 14 12:12:09 2023\n=============================================================\n\n&gt;&gt;&gt; Starting Switchover between srv01 and srv02\n\nRunning pre-checks       ... done\n\n=&gt;Enter Custom User Script to run after Switchover is complete on srv01\n(leave blank for no script): []:\n\n=&gt;Enter Custom User Script to run after Switchover is complete on srv02\n(leave blank for no script): []:\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: srv02\n    Standby Database Server: srv01\n\n&gt;&gt;&gt; Dbvisit Standby can be run as per normal:\n    dbvctl -d MYDB\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:12677\nTRACE:12677_dbvctl_switchover_MYDB_202312141212.trc\n\n=============================================================\ndbvctl ended on srv01: Thu Dec 14 12:15:13 2023\n=============================================================\n<\/pre>\n<\/br>\n","protected":false},"excerpt":{"rendered":"<p>After having recently deployed a new customer system running Oracle SE2 databases in Disaster Recovery environment using dbvisit StandbyMP v11.4.1 on Oracle Linux 8.8, I did some final test running a switchover. The switchover failed with following error: Problem description Running switchover command was failing: oracle@srv01:~\/ [MYDB] \/u01\/app\/dbvisit\/standbymp\/oracle\/dbvctl -d MYDB -o switchover ============================================================= Dbvisit Standby [&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":[],"type_dbi":[],"class_list":["post-30032","post","type-post","status-publish","format-standard","hentry","category-oracle"],"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>dbvisit StandbyMP with Oracle SE2 \u2013 switchover error with ORA-27125 - 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\/dbvisit-standbymp-with-oracle-se2-switchover-error-with-ora-27125\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"dbvisit StandbyMP with Oracle SE2 \u2013 switchover error with ORA-27125\" \/>\n<meta property=\"og:description\" content=\"After having recently deployed a new customer system running Oracle SE2 databases in Disaster Recovery environment using dbvisit StandbyMP v11.4.1 on Oracle Linux 8.8, I did some final test running a switchover. The switchover failed with following error: Problem description Running switchover command was failing: oracle@srv01:~\/ [MYDB] \/u01\/app\/dbvisit\/standbymp\/oracle\/dbvctl -d MYDB -o switchover ============================================================= Dbvisit Standby [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/dbvisit-standbymp-with-oracle-se2-switchover-error-with-ora-27125\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2023-12-31T13:26:26+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2023-12-31T13:26:28+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=\"2 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\/dbvisit-standbymp-with-oracle-se2-switchover-error-with-ora-27125\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dbvisit-standbymp-with-oracle-se2-switchover-error-with-ora-27125\/\"},\"author\":{\"name\":\"Marc Wagner\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628\"},\"headline\":\"dbvisit StandbyMP with Oracle SE2 \u2013 switchover error with ORA-27125\",\"datePublished\":\"2023-12-31T13:26:26+00:00\",\"dateModified\":\"2023-12-31T13:26:28+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dbvisit-standbymp-with-oracle-se2-switchover-error-with-ora-27125\/\"},\"wordCount\":419,\"commentCount\":0,\"articleSection\":[\"Oracle\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/dbvisit-standbymp-with-oracle-se2-switchover-error-with-ora-27125\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dbvisit-standbymp-with-oracle-se2-switchover-error-with-ora-27125\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/dbvisit-standbymp-with-oracle-se2-switchover-error-with-ora-27125\/\",\"name\":\"dbvisit StandbyMP with Oracle SE2 \u2013 switchover error with ORA-27125 - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2023-12-31T13:26:26+00:00\",\"dateModified\":\"2023-12-31T13:26:28+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dbvisit-standbymp-with-oracle-se2-switchover-error-with-ora-27125\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/dbvisit-standbymp-with-oracle-se2-switchover-error-with-ora-27125\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dbvisit-standbymp-with-oracle-se2-switchover-error-with-ora-27125\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"dbvisit StandbyMP with Oracle SE2 \u2013 switchover error with ORA-27125\"}]},{\"@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":"dbvisit StandbyMP with Oracle SE2 \u2013 switchover error with ORA-27125 - 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\/dbvisit-standbymp-with-oracle-se2-switchover-error-with-ora-27125\/","og_locale":"en_US","og_type":"article","og_title":"dbvisit StandbyMP with Oracle SE2 \u2013 switchover error with ORA-27125","og_description":"After having recently deployed a new customer system running Oracle SE2 databases in Disaster Recovery environment using dbvisit StandbyMP v11.4.1 on Oracle Linux 8.8, I did some final test running a switchover. The switchover failed with following error: Problem description Running switchover command was failing: oracle@srv01:~\/ [MYDB] \/u01\/app\/dbvisit\/standbymp\/oracle\/dbvctl -d MYDB -o switchover ============================================================= Dbvisit Standby [&hellip;]","og_url":"https:\/\/www.dbi-services.com\/blog\/dbvisit-standbymp-with-oracle-se2-switchover-error-with-ora-27125\/","og_site_name":"dbi Blog","article_published_time":"2023-12-31T13:26:26+00:00","article_modified_time":"2023-12-31T13:26:28+00:00","author":"Marc Wagner","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Marc Wagner","Est. reading time":"2 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/dbvisit-standbymp-with-oracle-se2-switchover-error-with-ora-27125\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/dbvisit-standbymp-with-oracle-se2-switchover-error-with-ora-27125\/"},"author":{"name":"Marc Wagner","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628"},"headline":"dbvisit StandbyMP with Oracle SE2 \u2013 switchover error with ORA-27125","datePublished":"2023-12-31T13:26:26+00:00","dateModified":"2023-12-31T13:26:28+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/dbvisit-standbymp-with-oracle-se2-switchover-error-with-ora-27125\/"},"wordCount":419,"commentCount":0,"articleSection":["Oracle"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/dbvisit-standbymp-with-oracle-se2-switchover-error-with-ora-27125\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/dbvisit-standbymp-with-oracle-se2-switchover-error-with-ora-27125\/","url":"https:\/\/www.dbi-services.com\/blog\/dbvisit-standbymp-with-oracle-se2-switchover-error-with-ora-27125\/","name":"dbvisit StandbyMP with Oracle SE2 \u2013 switchover error with ORA-27125 - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2023-12-31T13:26:26+00:00","dateModified":"2023-12-31T13:26:28+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/dbvisit-standbymp-with-oracle-se2-switchover-error-with-ora-27125\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/dbvisit-standbymp-with-oracle-se2-switchover-error-with-ora-27125\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/dbvisit-standbymp-with-oracle-se2-switchover-error-with-ora-27125\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"dbvisit StandbyMP with Oracle SE2 \u2013 switchover error with ORA-27125"}]},{"@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\/30032","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=30032"}],"version-history":[{"count":14,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/30032\/revisions"}],"predecessor-version":[{"id":30046,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/30032\/revisions\/30046"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=30032"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=30032"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=30032"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=30032"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}