I’m currently working on a customer project, where we have 2 old Lenovo Servers, one ODA X7-2M and another ODA X8-2M. In the new project, we are replacing the 2 old Lenovo Servers by 2 new ODA X9-2L. The production database, let’s call it DB01, is a Standard Edition database with dbvisit Standby as Disaster Recovery solution. During each project, we take the opportunity to upgrade dbvisit Stanby software to last available version. In 2022, I then upgraded dbvisit from v8 to v10, and recently to v11.<\/p>\n\n\n\n
In 2022, when upgrading dbvisit Standby from v8 to v10, I faced a dbvnet port problem for the standby database running on the old Lenovo Server. For the standby databases running on the ODA there was absolutely no problem.<\/p>\n\n\n\n
The problem raised already when trying to upgrade the DDC configuration to the new v10 version:<\/p>\n\n\n\n
\noracle@srv01:\/u01\/app\/dbvisit\/standby\/ [LX] .\/dbvctl -d DB01STD2 -o upgrade\n=============================================================\nDbvisit Standby Database Technology (10.2.0_0_gd69c33d2) (pid 72540)\ndbvctl started on srv01: Tue Sep 13 20:29:20 2022\n=============================================================\n\n\n\n=========================================================\n\n Dbvisit Standby Database Technology (10.2.0_0_gd69c33d2)\n http:\/\/www.dbvisit.com\n\n=========================================================\n\n=>dbvctl only needs to be run on the primary server.\n\nIs this the primary server? [Yes]:\n\n>>> DDC file DB01STD2 version: 8.0.26\n\n>>> Failed to copy \/u01\/app\/dbvisit\/standby\/conf\/dbv_DB01STD2.env to standby: Problem with\n \/u01\/app\/dbvisit\/dbvnet\/dbvnet \/u01\/app\/dbvisit\/standby\/conf\/dbv_DB01STD2.env\n srv02:\/u01\/app\/dbvisit\/standby\/conf\/dbv_DB01STD2.env. Ensure\n \/u01\/app\/dbvisit\/dbvnet\/dbvnet is configured correctly without needing a password or\n passphrase, the file exists and the remote directory \/u01\/app\/dbvisit\/standby\/conf on\n srv02 exists. time=\"2022-09-13T20:29:33+02:00\" level=info msg=\"dbvnet: error:\n unable to connect: dial tcp X.X.X.43:7890: connect: connection refused\"\n\n>>> DDC file DB01STD2 upgraded to version 10.2.0.\n\n>>> Dbvisit Database repository (DDR) up to date, no upgrade required.\n\n=============================================================\ndbvctl ended on srv01: Tue Sep 13 20:29:33 2022\n=============================================================\n<\/pre>\n<\/br>\n\n\n\nAlbeit dbvnet process was up and running on 7890 port on the standby server:<\/p>\n\n\n\n
\n[root@srv02 ~]# ps -ef | grep -i dbv | grep -v grep\noracle 2049 1 0 20:57 ? 00:00:00 \/u01\/app\/dbvisit\/dbvagent\/dbvagent -d start\noracle 2077 1 0 20:57 ? 00:00:00 \/u01\/app\/dbvisit\/dbvnet\/dbvnet -d start\n<\/pre>\n<\/br>\n\n\n\nIt was impossible to reach the connection to the standby server on the standard port.<\/p>\n\n\n\n
\noracle@srv01:\/u01\/app\/dbvisit\/standby\/conf\/ [LX] nc -zv X.X.X.43 7890\nNcat: Version 7.50 ( https:\/\/nmap.org\/ncat )\nNcat: Connection refused.\n<\/pre>\n<\/br>\n\n\n\nAnd no firewall was in used.<\/p>\n\n\n\n
At that time, for the concerned configurations involving the Lenovo servers as standby, we decided to move the communication to use ssh connection instead of standard port for dbvnet. Port 22 instead of port 7890. This resolved at that time the problem.<\/p>\n\n\n\n
dbvisit Standby upgrade to v11<\/h2>\n\n\n\n
This year, upgrading dbvisit Standby v10 to last StandbyMP v11 version, implied to first solve the dbvnet problem with port 7890 related to the Lenovo servers. This is mandatory knowing last StandbyMP version does not support 22 port connection any more.<\/p>\n\n\n\n
When upgrading dbvisit, the primary database was running on srv02. srv01 was other old Lenovo servers running a standby database with configuration DB01STD2. Both other ODAs were running standby database with DDC configuration DB01STD1 and DB01STD3.<\/p>\n\n\n\n
As we can see, the DDC configuration in relation with standby databases running on the ODA were still using dbvnet port 7890:<\/p>\n\n\n\n
\noracle@srv02:\/u01\/app\/dbvisit\/standby\/conf\/ [DB01] grep -i '^RSH\\|^CP\\|NETPORT\\|NETPORT_DR' dbv_DB01STD3.env\n# NETPORT - Dbvnet port on primary server(default 7890)\nNETPORT = 7890\n# NETPORT_DR - Dbvnet port on standby server(default 7890)\nNETPORT_DR = 7890\nCP =\nRSH =\n\noracle@srv02:\/u01\/app\/dbvisit\/standby\/conf\/ [DB01] grep -i '^RSH\\|^CP\\|NETPORT\\|NETPORT_DR' dbv_DB01STD1.env\n# NETPORT - Dbvnet port on primary server(default 7890)\nNETPORT = 7890\n# NETPORT_DR - Dbvnet port on standby server(default 7890)\nNETPORT_DR = 7890\nCP =\nRSH =\n<\/pre>\n<\/br>\n\n\n\nWhen DDC configuration in relation with standby database running on other Lenovo Server srv01 was using dbvnet port 22:<\/p>\n\n\n\n
\noracle@srv02:\/u01\/app\/dbvisit\/standby\/conf\/ [DB01] grep -i '^RSH\\|^CP\\|NETPORT\\|NETPORT_DR' dbv_DB01STD2.env\n# NETPORT - Dbvnet port on primary server(default 7890)\nNETPORT = 22\n# NETPORT_DR - Dbvnet port on standby server(default 7890)\nNETPORT_DR = 22\nCP = \/usr\/bin\/scp\nRSH = \/usr\/bin\/ssh\n<\/pre>\n<\/br>\n\n\n\nI changed the DB01STD2 configuration to use again dbvnet on port 7890:<\/p>\n\n\n\n
\noracle@srv02:\/u01\/app\/dbvisit\/standby\/conf\/ [DB01] cp -p dbv_DB01STD2.env dbv_DB01STD2.env.202312291139\noracle@srv02:\/u01\/app\/dbvisit\/standby\/conf\/ [DB01] vi dbv_DB01STD2.env\noracle@srv02:\/u01\/app\/dbvisit\/standby\/conf\/ [DB01] diff dbv_DB01STD2.env dbv_DB01STD2.env.202312291139\n61c61\n NETPORT = 22\n103c103\n NETPORT_DR = 22\n419c419\n CP = \/usr\/bin\/scp\n432c432\n RSH = \/usr\/bin\/ssh\n<\/pre>\n<\/br>\n\n\n\nBut of course synchronising the configuration with srv01 standby server was failing with same error faced in 2022:<\/p>\n\n\n\n
\noracle@srv02:\/u01\/app\/dbvisit\/standby\/conf\/ [DB01] ..\/dbvctl -d DB01STD2 -C\n=============================================================\nDbvisit Standby Database Technology (10.2.0_0_gd69c33d2) (pid 224727)\ndbvctl started on srv02: Tue Dec 19 11:41:06 2023\n=============================================================\n\n\n<<<>>>\n\nPID:224727\nTRACEFILE:224727_dbvctl_DB01STD2_202312191141.trc\nSERVER:srv02\nERROR_CODE:1\nConnection to srv01 failed.\nNo initial contact can be made or remote command cannot be run\nPlease check network connection and review the settings:\n RSH=\n DEST_SERVER=srv01\n DEST_NETPORT=7890\n DBVISIT_BASE=\/u01\/app\/dbvisit\n\ntime=\"2023-12-19T11:41:16+01:00\" level=info msg=\"dbvnet: error: unable to connect: dial\ntcp X.X.X.42:7890: connect: connection refused\"\n\n\n>>>> Dbvisit Standby terminated <<<<\n<\/pre>\n<\/br>\n\n\n\nI confirmed I could not reach the standby server on the port 7890:<\/p>\n\n\n\n
\noracle@srv02:\/u01\/app\/dbvisit\/standby\/conf\/ [DB01] nc -zv X.X.X.42 7890\nNcat: Version 7.50 ( https:\/\/nmap.org\/ncat )\nNcat: Connection refused.\n\noracle@srv02:\/u01\/app\/dbvisit\/standby\/conf\/ [DB01] nc -zv srv01 7890\nNcat: Version 7.50 ( https:\/\/nmap.org\/ncat )\nNcat: Connection refused.\n<\/pre>\n<\/br>\n\n\n\nDoing some further troubleshooting I could realize that the server was listening on the port 7890 on the internal 127.0.0.1 IP address:<\/p>\n\n\n\n
\n[root@srv01 ~]# ss -tulpn | grep 7890\ntcp LISTEN 0 128 127.0.0.1:7890 *:* users:((\"dbvnet\",pid=1712,fd=0))\n[root@srv01 ~]#\n<\/pre>\n<\/br>\n\n\n\nWhich was definitively the problem. But why?<\/p>\n\n\n\n
The dbvnet process is using the hostname as listener address and listener port as 7890:<\/p>\n\n\n\n
\noracle@srv01:\/home\/oracle\/ [rdbms12201] cd \/u01\/app\/dbvisit\/dbvnet\/conf\/\noracle@srv01:\/u01\/app\/dbvisit\/dbvnet\/conf\/ [rdbms12201] cat dbvnetd.conf\n[general]\nlistener_address=srv01\nlistener_port=7890\npassphrase=encrypt\n\n\ncertkey=\n\ndebug=3\n\n<\/pre>\n<\/br>\n\n\n\nSolution<\/h2>\n\n\n\n
The problem was coming from a bad \/etc\/hosts configuration in the old Lenovo Servers.<\/p>\n\n\n\n
As we can see in the \/etc\/hosts:<\/p>\n\n\n\n
\n[root@srv01 ~]# cat \/etc\/hosts\n127.0.0.1 srv01 srv01.customer.local localhost localhost.localdomain localhost4 localhost4.localdomain4\n::1 localhost localhost.localdomain localhost6 localhost6.localdomain6\n\n# Productive DB Servers\nX.X.X.56 db01vip db01vip.customer.local\nX.X.X.77 dbvisitconsole01 dbvisitconsole01.customer.local\n\nX.X.X.43 srv02 srv02.customer.local\nY.Y.Y.43 srv02_arch\n\nX.X.X.42 srv01 srv01.customer.local\nY.Y.Y.42 srv01_arch\n\n10.50.7.11 srv03 srv03.customer.local\n# Y.Y.Y. srv03_arch\n<\/pre>\n<\/br>\n\n\n\nthe hostname is incorrectly set on the localhost line.<\/p>\n\n\n\n
I updated accordingly the \/etc\/hosts configuration file on both Lenovo servers srv01 and srv02 as following:<\/p>\n\n\n\n
\n[root@srv01 ~]# vi \/etc\/hosts\n[root@srv01 ~]# cat \/etc\/hosts\n#127.0.0.1 srv01 srv01.customer.local localhost localhost.localdomain localhost4 localhost4.localdomain4\n127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4\n::1 localhost localhost.localdomain localhost6 localhost6.localdomain6\n\n# Productive DB Servers\nX.X.X.56 db01vip db01vip.customer.local\nX.X.X.77 dbvisitconsole01 dbvisitconsole01.customer.local\n\nX.X.X.43 srv02 srv02.customer.local\nY.Y.Y.43 srv02_arch\n\nX.X.X.42 srv01 srv01.customer.local\nY.Y.Y.42 srv01_arch\n\n10.50.7.11 srv03 srv03.customer.local\n# Y.Y.Y. srv03_arch\n\n[root@srv01 ~]#\n<\/pre>\n<\/br>\n\n\n\nI restarted dbvnet service process on both Lenovo servers srv01 and srv02:<\/p>\n\n\n\n
\n[root@srv01 ~]# systemctl stop dbvnet\n[root@srv01 ~]# ps -ef | grep [d]bv\n[root@srv01 ~]# systemctl start dbvnet\n[root@srv01 ~]# ps -ef | grep [d]bv\noracle 57869 1 0 11:58 ? 00:00:00 \/u01\/app\/dbvisit\/dbvnet\/dbvnet -d start\n<\/pre>\n<\/br>\n\n\n\nAnd could confirm that now the server was listening on the right IP address interface (and not the local one anymore) for port 7890:<\/p>\n\n\n\n
\n[root@srv01 ~]# ss -tulpn | grep 7890\ntcp LISTEN 0 128 X.X.X.42:7890 *:* users:((\"dbvnet\",pid=57869,fd=0))\n[root@srv01 ~]#\n<\/pre>\n<\/br>\n\n\n\nAnd now the standby server was allowing connection on the appropriate port listening on the hostname:<\/p>\n\n\n\n
\noracle@srv02:\/u01\/app\/dbvisit\/standby\/conf\/ [DB01] nc -zv srv01 7890\nNcat: Version 7.50 ( https:\/\/nmap.org\/ncat )\nNcat: Connected to X.X.X.42:7890.\nNcat: 0 bytes sent, 0 bytes received in 0.01 seconds.\n<\/pre>\n<\/br>\n\n\n\nAnd I could synchronise the configuration on the standby server now:<\/p>\n\n\n\n
\noracle@srv02:\/u01\/app\/dbvisit\/standby\/conf\/ [DB01] ..\/dbvctl -d DB01STD2 -C\n=============================================================\nDbvisit Standby Database Technology (10.2.0_0_gd69c33d2) (pid 252908)\ndbvctl started on srv02: Tue Dec 19 11:59:00 2023\n=============================================================\n\n>>> Dbvisit Standby configurational differences found between srv02 and srv01.\n Synchronised.\n\n=============================================================\ndbvctl ended on srv02: Tue Dec 19 11:59:01 2023\n=============================================================\n<\/pre>\n<\/br>\n\n\n\nAnd all was ok then to successfully complete dbvisit StandbyMP upgrade to last v11 version.<\/p>\n","protected":false},"excerpt":{"rendered":"
I’m currently working on a customer project, where we have 2 old Lenovo Servers, one ODA X7-2M and another ODA X8-2M. In the new project, we are replacing the 2 old Lenovo Servers by 2 new ODA X9-2L. The production database, let’s call it DB01, is a Standard Edition database with dbvisit Standby as Disaster […]<\/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-30047","post","type-post","status-publish","format-standard","hentry","category-oracle"],"acf":[],"yoast_head":"\n
dbvisit StandbyMP with OracleSE2 - dbvnet port problem - 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-oraclese2-dbvnet-port-problem\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"dbvisit StandbyMP with OracleSE2 - dbvnet port problem\" \/>\n<meta property=\"og:description\" content=\"I’m currently working on a customer project, where we have 2 old Lenovo Servers, one ODA X7-2M and another ODA X8-2M. In the new project, we are replacing the 2 old Lenovo Servers by 2 new ODA X9-2L. The production database, let’s call it DB01, is a Standard Edition database with dbvisit Standby as Disaster […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/dbvisit-standbymp-with-oraclese2-dbvnet-port-problem\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2023-12-31T15:06:33+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2023-12-31T15:06:35+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=\"3 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-oraclese2-dbvnet-port-problem\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dbvisit-standbymp-with-oraclese2-dbvnet-port-problem\/\"},\"author\":{\"name\":\"Marc Wagner\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628\"},\"headline\":\"dbvisit StandbyMP with OracleSE2 – dbvnet port problem\",\"datePublished\":\"2023-12-31T15:06:33+00:00\",\"dateModified\":\"2023-12-31T15:06:35+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dbvisit-standbymp-with-oraclese2-dbvnet-port-problem\/\"},\"wordCount\":563,\"commentCount\":0,\"articleSection\":[\"Oracle\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/dbvisit-standbymp-with-oraclese2-dbvnet-port-problem\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dbvisit-standbymp-with-oraclese2-dbvnet-port-problem\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/dbvisit-standbymp-with-oraclese2-dbvnet-port-problem\/\",\"name\":\"dbvisit StandbyMP with OracleSE2 - dbvnet port problem - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2023-12-31T15:06:33+00:00\",\"dateModified\":\"2023-12-31T15:06:35+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dbvisit-standbymp-with-oraclese2-dbvnet-port-problem\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/dbvisit-standbymp-with-oraclese2-dbvnet-port-problem\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dbvisit-standbymp-with-oraclese2-dbvnet-port-problem\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"dbvisit StandbyMP with OracleSE2 – dbvnet port problem\"}]},{\"@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 OracleSE2 - dbvnet port problem - 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-oraclese2-dbvnet-port-problem\/","og_locale":"en_US","og_type":"article","og_title":"dbvisit StandbyMP with OracleSE2 - dbvnet port problem","og_description":"I’m currently working on a customer project, where we have 2 old Lenovo Servers, one ODA X7-2M and another ODA X8-2M. In the new project, we are replacing the 2 old Lenovo Servers by 2 new ODA X9-2L. The production database, let’s call it DB01, is a Standard Edition database with dbvisit Standby as Disaster […]","og_url":"https:\/\/www.dbi-services.com\/blog\/dbvisit-standbymp-with-oraclese2-dbvnet-port-problem\/","og_site_name":"dbi Blog","article_published_time":"2023-12-31T15:06:33+00:00","article_modified_time":"2023-12-31T15:06:35+00:00","author":"Marc Wagner","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Marc Wagner","Est. reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/dbvisit-standbymp-with-oraclese2-dbvnet-port-problem\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/dbvisit-standbymp-with-oraclese2-dbvnet-port-problem\/"},"author":{"name":"Marc Wagner","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628"},"headline":"dbvisit StandbyMP with OracleSE2 – dbvnet port problem","datePublished":"2023-12-31T15:06:33+00:00","dateModified":"2023-12-31T15:06:35+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/dbvisit-standbymp-with-oraclese2-dbvnet-port-problem\/"},"wordCount":563,"commentCount":0,"articleSection":["Oracle"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/dbvisit-standbymp-with-oraclese2-dbvnet-port-problem\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/dbvisit-standbymp-with-oraclese2-dbvnet-port-problem\/","url":"https:\/\/www.dbi-services.com\/blog\/dbvisit-standbymp-with-oraclese2-dbvnet-port-problem\/","name":"dbvisit StandbyMP with OracleSE2 - dbvnet port problem - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2023-12-31T15:06:33+00:00","dateModified":"2023-12-31T15:06:35+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/dbvisit-standbymp-with-oraclese2-dbvnet-port-problem\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/dbvisit-standbymp-with-oraclese2-dbvnet-port-problem\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/dbvisit-standbymp-with-oraclese2-dbvnet-port-problem\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"dbvisit StandbyMP with OracleSE2 – dbvnet port problem"}]},{"@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\/30047","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=30047"}],"version-history":[{"count":14,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/30047\/revisions"}],"predecessor-version":[{"id":30061,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/30047\/revisions\/30061"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=30047"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=30047"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=30047"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=30047"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}