{"id":5443,"date":"2015-09-03T08:50:11","date_gmt":"2015-09-03T06:50:11","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/oracle-12c-duplicate-in-cluster-fails-with-ora-65500\/"},"modified":"2015-09-03T08:50:11","modified_gmt":"2015-09-03T06:50:11","slug":"oracle-12c-duplicate-in-cluster-fails-with-ora-65500","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/oracle-12c-duplicate-in-cluster-fails-with-ora-65500\/","title":{"rendered":"Oracle 12c duplicate in cluster fails with ORA-65500"},"content":{"rendered":"

I had to perform a duplicate database between 2 ODAs and was always facing an ORA-65500 at the begin of the RMAN operation. Looking a bit deeper in the log outputs pointed me out that it was due to some changes in the way RMAN makes the duplicate in 12c and cluster resources management.<\/p>\n

<\/p>\n

Basically up to 12c when RMAN was doing a duplicate, it was changing the auxiliary spfile to set the DB_NAME at the value of the target database. This is required as after restoring a copy of the control file, RMAN needs to MOUNT the database. If the DB_NAME does not match between the spfile and the control files it won’t be possible to MOUNT the database. At the end of the duplicate RMAN changes the DB_NAME back in the spfile and uses NID principle to change it in the control files.<\/p>\n

In version 12c now RMAN doesn’t change only the DB_NAME, but also the DB_UNIQUE_NAME and here is the trick!<\/p>\n

While working in a cluster environment (Oracle Restart, RAC One Node, RAC, ODA…) the database is defined as a cluster resource based on its DB_UNIQUE_NAME<\/p>\n

[root@dbioda1 bin]# .\/crsctl stat res ora.dbtest_site1.db -t\n--------------------------------------------------------------------------------\nName           Target  State        Server                   State details\n--------------------------------------------------------------------------------\nCluster Resources\n--------------------------------------------------------------------------------\nora.dbtest_site1.db\n      1        ONLINE  ONLINE       dbioda1              Open,STABLE\n--------------------------------------------------------------------------------<\/pre>\n
 <\/p>\n
At the beginning of the duplicate process RMAN runs following SQL:<\/p>\n
sql statement: alter system set  db_name =  ''DBPROD'' comment= ''Modified by RMAN duplicate'' scope=spfile\n\nsql statement: alter system set  db_unique_name =  ''DBTEST_SITE1'' comment= ''Modified by RMAN duplicate'' scope=spfile<\/pre>\n
 <\/p>\n
Unfortunately changing the DB_UNIQUE_NAME is NOT allowed on a database defined as a cluster resource and that’s why we get the following error:<\/p>\n
RMAN-00571: ===========================================================\nRMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============\nRMAN-00571: ===========================================================\nRMAN-03002: failure of Duplicate Db command at 09\/03\/2015 10:11:00\nRMAN-04014: startup failed: ORA-00304: requested INSTANCE_NUMBER is busy\nRMAN-03015: error occurred in stored script Memory Script\nRMAN-03009: failure of sql command on clone_default channel at 09\/03\/2015 10:10:36\nRMAN-11003: failure during parse\/execution of SQL statement: alter system set  db_unique_name =  'DBTEST_SITE1' comment= 'Modified by RMAN duplicate' scope=spfile\nORA-32017: failure in updating SPFILE\nORA-65500: could not modify DB_UNIQUE_NAME, resource exists<\/pre>\n
 <\/p>\n
The most frustrating is that after this failure, you won’t be able to start anymore your auxiliary database using your spfile. The only solution is to generate it again from a pfile<\/p>\n
Connected to an idle instance.\n\nSQL> startup nomount\nORA-00304: requested INSTANCE_NUMBER is busy\n\nSQL> create spfile='\/u02\/app\/oracle\/oradata\/datastore\/.ACFS\/snaps\/DBTEST\/DBTEST_SITE1\/spfileDBTEST.ora' from pfile='\/home\/oracle\/initDBTEST.ora';\n\nFile created.\n\nSQL> startup nomount\nORACLE instance started.\n\nTotal System Global Area 1.7180E+10 bytes\nFixed Size\t\t    3731384 bytes\nVariable Size\t\t 2550136904 bytes\nDatabase Buffers\t 1.4563E+10 bytes\nRedo Buffers\t\t   63377408 bytes<\/pre>\n
 <\/p>\n
Indeed you can even validate this behaviour after setting your database in NOMOUNT and trying manually to change the DB_UNIQUE_NAME.<\/p>\n
Therefore I tried some workarounds:<\/p>\n
    \n
  1. Stopping the database using srvctl before setting it in NOMOUNT and changing the DB_UNIQUE_NAME<\/li>\n
  2. Disabling the database in the cluster before setting it in NOMOUNT and changing the DB_UNIQUE_NAME<\/li>\n<\/ol>\n
    Of course the solution 1 doesn’t work as after starting the database in NOMOUNT, cluster resource is up again<\/p>\n
    oracle@dbioda1:\/home\/oracle\/ [DBTEST] srvctl status database -db DBTEST_SITE1\nInstance DBTEST is running on node dbioda1\noracle@dbioda1:\/home\/oracle\/ [DBTEST] srvctl stop database -db DBTEST_SITE1\noracle@dbioda1:\/home\/oracle\/ [DBTEST] sqh\nSQL*Plus: Release 12.1.0.2.0 Production on Thu Sep 3 10:25:46 2015\n\nCopyright (c) 1982, 2014, Oracle.  All rights reserved.\nConnected to an idle instance.\n\nSQL> startup nomount\nORACLE instance started.\n\nTotal System Global Area 1.7180E+10 bytes\n...\n\nSQL> alter system set db_unique_name='TOTO' scope=spfile;\nalter system set db_unique_name='TOTO' scope=spfile\n*\nERROR at line 1:\nORA-32017: failure in updating SPFILE\nORA-65500: could not modify DB_UNIQUE_NAME, resource exists<\/strong>\n\nSQL> exit\n\noracle@dbioda1:\/home\/oracle\/ [DBTEST] srvctl status database -db DBTEST_SITE1\nInstance DBTEST is running on node dbioda1<\/pre>\n
     <\/p>\n
    I was a bit more confident in the workaround 2 by disabling the resource in the cluster before doing the changes. Unfortunately we still face the same issue:<\/p>\n
    oracle@dbioda1:\/home\/oracle\/ [DBTEST] srvctl status database -db DBTEST_SITE1\nInstance DBTEST is running on node dbioda1\noracle@dbioda1:\/home\/oracle\/ [DBTEST] srvctl stop database -db DBTEST_SITE1\noracle@dbioda1:\/home\/oracle\/ [DBTEST] srvctl disable database -db DBTEST_SITE1\noracle@dbioda1:\/home\/oracle\/ [DBTEST] sqh\nSQL*Plus: Release 12.1.0.2.0 Production on Thu Sep 3 10:32:50 2015\nCopyright (c) 1982, 2014, Oracle.  All rights reserved.\n\nConnected to an idle instance.\n\nSQL> startup nomount\nORACLE instance started.\n\nTotal System Global Area 1.7180E+10 bytes\n...\nSQL> alter system set db_unique_name='TOTO' scope=spfile;\nalter system set db_unique_name='TOTO' scope=spfile\n*\nERROR at line 1:\nORA-32017: failure in updating SPFILE\nORA-65500: could not modify DB_UNIQUE_NAME, resource exists<\/strong>\n\nSQL> exit\n\noracle@dbioda1:\/home\/oracle\/ [DBTEST] srvctl status database -db DBTEST_SITE1\nInstance DBTEST is not running on node dbioda1<\/strong><\/pre>\n
    As we can see\u00a0 after setting the database in NOMOUNT, the cluster resource remains stopped as it is disabled. But even so we are not allowed to change the DB_UNIQUE_NAME<\/p>\n
    Thefore the only solution I could found so far is first to remove the resource from the cluster, run the duplicate and then add the resource back in the cluster with a command like:<\/p>\n
    srvctl add database -db DBTEST_SITE1 -oraclehome $ORACLE_HOME -dbtype SINGLE -role PRIMARY -spfile \/u02\/app\/oracle\/oradata\/datastore\/.ACFS\/snaps\/DBTEST\/DBTEST_SITE1\/spfileDBTEST.ora -pwfile \/u01\/app\/oracle\/product\/12.1.0.2\/dbhome_1\/dbs\/orapwDBTEST -dbname DBTEST -startoption mount -stopoption immediate -instance DBTEST -node dbioda1 -acfspath \"\/u01\/app\/oracle\/oradata\/datastore,\/u02\/app\/oracle\/oradata\/datastore,\/u01\/app\/oracle\/fast_recovery_area\/datastore\"<\/pre>\n
     <\/p>\n
    As a conclusion, we can say the following:<\/p>\n
      \n
    • \u00a0Oracle 11g database duplicate in cluster or ODA environments works straight forward<\/li>\n
    • Oracle 12c database duplicate in cluster or ODA environmentsrequries first to remove the database resource from the cluster and to add it back afterwards.<\/li>\n<\/ul>\n
       <\/p>\n
      Hope it helps! \ud83d\ude00<\/p>\n
       <\/p>\n
       <\/p>\n","protected":false},"excerpt":{"rendered":"
      I had to perform a duplicate database between 2 ODAs and was always facing an ORA-65500 at the begin of the RMAN operation. Looking a bit deeper in the log outputs pointed me out that it was due to some changes in the way RMAN makes the duplicate in 12c and cluster resources management.<\/p>\n","protected":false},"author":7,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229,198],"tags":[38,280,23,311,258,209,270],"type_dbi":[],"class_list":["post-5443","post","type-post","status-publish","format-standard","hentry","category-database-administration-monitoring","category-database-management","tag-cluster","tag-database","tag-dba","tag-duplicate","tag-grid","tag-oracle-12c","tag-rman"],"acf":[],"yoast_head":"\nOracle 12c duplicate in cluster fails with ORA-65500 - dbi Blog<\/title>\n<meta name=\"description\" content=\"Blog about Oracle 12c duplicate issue in cluster and ODA environments while facing ORA-65500 error. Unfortunately cluster resource needs to be remove before duplicating the database.\" \/>\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\/oracle-12c-duplicate-in-cluster-fails-with-ora-65500\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Oracle 12c duplicate in cluster fails with ORA-65500\" \/>\n<meta property=\"og:description\" content=\"Blog about Oracle 12c duplicate issue in cluster and ODA environments while facing ORA-65500 error. Unfortunately cluster resource needs to be remove before duplicating the database.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/oracle-12c-duplicate-in-cluster-fails-with-ora-65500\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2015-09-03T06:50:11+00:00\" \/>\n<meta name=\"author\" content=\"David Hueber\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"David Hueber\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 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\/oracle-12c-duplicate-in-cluster-fails-with-ora-65500\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/oracle-12c-duplicate-in-cluster-fails-with-ora-65500\/\"},\"author\":{\"name\":\"David Hueber\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8873e20a98a02305870909f4e3d0088f\"},\"headline\":\"Oracle 12c duplicate in cluster fails with ORA-65500\",\"datePublished\":\"2015-09-03T06:50:11+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/oracle-12c-duplicate-in-cluster-fails-with-ora-65500\/\"},\"wordCount\":505,\"commentCount\":0,\"keywords\":[\"Cluster\",\"database\",\"DBA\",\"duplicate\",\"Grid\",\"Oracle 12c\",\"RMAN\"],\"articleSection\":[\"Database Administration & Monitoring\",\"Database management\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/oracle-12c-duplicate-in-cluster-fails-with-ora-65500\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/oracle-12c-duplicate-in-cluster-fails-with-ora-65500\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/oracle-12c-duplicate-in-cluster-fails-with-ora-65500\/\",\"name\":\"Oracle 12c duplicate in cluster fails with ORA-65500 - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2015-09-03T06:50:11+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8873e20a98a02305870909f4e3d0088f\"},\"description\":\"Blog about Oracle 12c duplicate issue in cluster and ODA environments while facing ORA-65500 error. Unfortunately cluster resource needs to be remove before duplicating the database.\",\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/oracle-12c-duplicate-in-cluster-fails-with-ora-65500\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/oracle-12c-duplicate-in-cluster-fails-with-ora-65500\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/oracle-12c-duplicate-in-cluster-fails-with-ora-65500\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Oracle 12c duplicate in cluster fails with ORA-65500\"}]},{\"@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\/8873e20a98a02305870909f4e3d0088f\",\"name\":\"David Hueber\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/fc07284dbd5667f0bed32b0d8d64076ab885746973ea1b5c4e69c6fa7074cf59?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/fc07284dbd5667f0bed32b0d8d64076ab885746973ea1b5c4e69c6fa7074cf59?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/fc07284dbd5667f0bed32b0d8d64076ab885746973ea1b5c4e69c6fa7074cf59?s=96&d=mm&r=g\",\"caption\":\"David Hueber\"},\"description\":\"David Hueber has ten years of experience in infrastructure operation & management, engineering, and optimization. He is specialized in Oracle technologies (engineering, backup and recovery, high availability, etc.), Service Management standards and Oracle infrastructure operation processes (Service Desk, Change Management, Capacity Planning, etc.). David Hueber is ITILv3 Service Operation Lifecycle certified and Linux LPIC-1 certified. He received a university degree in Informatics and Networks at the IUT Mulhouse, France. He also studied Information Systems at the Conservatoire National des Arts et M\u00e9tiers in Mulhouse, France. His branch-related experience covers Financial Services \/ Banking, Chemicals & Pharmaceuticals, Transport & Logistics, Retail, Food, etc.\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/david-hueber\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Oracle 12c duplicate in cluster fails with ORA-65500 - dbi Blog","description":"Blog about Oracle 12c duplicate issue in cluster and ODA environments while facing ORA-65500 error. Unfortunately cluster resource needs to be remove before duplicating the database.","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\/oracle-12c-duplicate-in-cluster-fails-with-ora-65500\/","og_locale":"en_US","og_type":"article","og_title":"Oracle 12c duplicate in cluster fails with ORA-65500","og_description":"Blog about Oracle 12c duplicate issue in cluster and ODA environments while facing ORA-65500 error. Unfortunately cluster resource needs to be remove before duplicating the database.","og_url":"https:\/\/www.dbi-services.com\/blog\/oracle-12c-duplicate-in-cluster-fails-with-ora-65500\/","og_site_name":"dbi Blog","article_published_time":"2015-09-03T06:50:11+00:00","author":"David Hueber","twitter_card":"summary_large_image","twitter_misc":{"Written by":"David Hueber","Est. reading time":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/oracle-12c-duplicate-in-cluster-fails-with-ora-65500\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/oracle-12c-duplicate-in-cluster-fails-with-ora-65500\/"},"author":{"name":"David Hueber","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8873e20a98a02305870909f4e3d0088f"},"headline":"Oracle 12c duplicate in cluster fails with ORA-65500","datePublished":"2015-09-03T06:50:11+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/oracle-12c-duplicate-in-cluster-fails-with-ora-65500\/"},"wordCount":505,"commentCount":0,"keywords":["Cluster","database","DBA","duplicate","Grid","Oracle 12c","RMAN"],"articleSection":["Database Administration & Monitoring","Database management"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/oracle-12c-duplicate-in-cluster-fails-with-ora-65500\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/oracle-12c-duplicate-in-cluster-fails-with-ora-65500\/","url":"https:\/\/www.dbi-services.com\/blog\/oracle-12c-duplicate-in-cluster-fails-with-ora-65500\/","name":"Oracle 12c duplicate in cluster fails with ORA-65500 - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2015-09-03T06:50:11+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8873e20a98a02305870909f4e3d0088f"},"description":"Blog about Oracle 12c duplicate issue in cluster and ODA environments while facing ORA-65500 error. Unfortunately cluster resource needs to be remove before duplicating the database.","breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/oracle-12c-duplicate-in-cluster-fails-with-ora-65500\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/oracle-12c-duplicate-in-cluster-fails-with-ora-65500\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/oracle-12c-duplicate-in-cluster-fails-with-ora-65500\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Oracle 12c duplicate in cluster fails with ORA-65500"}]},{"@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\/8873e20a98a02305870909f4e3d0088f","name":"David Hueber","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/fc07284dbd5667f0bed32b0d8d64076ab885746973ea1b5c4e69c6fa7074cf59?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/fc07284dbd5667f0bed32b0d8d64076ab885746973ea1b5c4e69c6fa7074cf59?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/fc07284dbd5667f0bed32b0d8d64076ab885746973ea1b5c4e69c6fa7074cf59?s=96&d=mm&r=g","caption":"David Hueber"},"description":"David Hueber has ten years of experience in infrastructure operation & management, engineering, and optimization. He is specialized in Oracle technologies (engineering, backup and recovery, high availability, etc.), Service Management standards and Oracle infrastructure operation processes (Service Desk, Change Management, Capacity Planning, etc.). David Hueber is ITILv3 Service Operation Lifecycle certified and Linux LPIC-1 certified. He received a university degree in Informatics and Networks at the IUT Mulhouse, France. He also studied Information Systems at the Conservatoire National des Arts et M\u00e9tiers in Mulhouse, France. His branch-related experience covers Financial Services \/ Banking, Chemicals & Pharmaceuticals, Transport & Logistics, Retail, Food, etc.","url":"https:\/\/www.dbi-services.com\/blog\/author\/david-hueber\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/5443","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\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=5443"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/5443\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=5443"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=5443"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=5443"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=5443"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}