I do have a Data Guard environment, where I have configured the RMAN DB_UNIQUE_NAME persistent setting for my primary and the standby. With the RMAN DB_UNIQUE_NAME settings I am able to run reports my Oracle Data Guard environment from any database. I could e.g. list all archivelogs for SITE1 from SITE2 or the other ways around.
\nOr I could show all persistent settings for SITE1 from SITE2 and of course the other way around. The only prerequisite for this feature is the RMAN catalog. In case you are not connected to the RMAN catalog you end up with the following error:<\/p>\n
RMAN> SHOW ARCHIVELOG DELETION POLICY FOR DB_UNIQUE_NAME 'DBIT121_SITE2';\n\nusing target database control file instead of recovery catalog\nRMAN-00571: ===========================================================\nRMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============\nRMAN-00571: ===========================================================\nRMAN-03002: failure of show command at 02\/21\/2017 13:58:53\nRMAN-05037: FOR DB_UNIQUE_NAME option cannot be used in nocatalog mode<\/pre>\nAfter connecting to the catalog, you can use this feature, e.g. to show the archive deletion policy.<\/p>\n
$ rman target sys\/welcome1 catalog \/@rcat\n\nRecovery Manager: Release 12.1.0.2.0 - Production on Tue Feb 21 14:25:10 2017\n\nCopyright (c) 1982, 2014, Oracle and\/or its affiliates. All rights reserved.\n\nconnected to target database: DBIT121 (DBID=644484523)\nconnected to recovery catalog database\n\nRMAN> SHOW ARCHIVELOG DELETION POLICY FOR DB_UNIQUE_NAME 'DBIT121_SITE1';\nRMAN configuration parameters for database with db_unique_name DBIT121_SITE1 are:\nCONFIGURE ARCHIVELOG DELETION POLICY TO SHIPPED TO ALL STANDBY BACKED UP 1 TIMES TO DISK;\n\nRMAN> SHOW ARCHIVELOG DELETION POLICY FOR DB_UNIQUE_NAME 'DBIT121_SITE2';\nRMAN configuration parameters for database with db_unique_name DBIT121_SITE2 are:\nCONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;<\/pre>\nThere are quite a lot options which can be combined with the DB_UNIQUE_NAME feature like the following.<\/p>\n
LIST ARCHIVELOG ALL FOR DB_UNIQUE_NAME 'DBIT121_SITE2';\nREPORT SCHEMA FOR DB_UNIQUE_NAME 'DBIT121_SITE2';\nSHOW ALL FOR DB_UNIQUE_NAME 'DBIT121_SITE2';<\/pre>\nBut getting back to my issue. I was running a resync catalog from my Standby database and ended up with the following error:<\/p>\n
RMAN> RESYNC CATALOG FROM DB_UNIQUE_NAME 'DBIT121_SITE1';\n\nresyncing from database with DB_UNIQUE_NAME DBIT121_SITE1\nRMAN-00571: ===========================================================\nRMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============\nRMAN-00571: ===========================================================\nRMAN-03009: failure of resync from db_unique_name command on default channel at 02\/21\/2017 13:08:42\nRMAN-20005: target database name is ambiguous<\/pre>\nRMAN says that the target database name is ambiguous. But what does this mean. Let’s take a look a the RMAN error with the oerr utility. The oerr utility\u00a0can not only be used with “ORA” error codes like “oerr ora 01555”, but also with “RMAN” error codes.<\/p>\n
$ oerr rman 20005\n20005, 1, \"target database name is ambiguous\"\n\/\/ *Cause: two or more databases in the recovery catalog match this name\n\/\/ *Action:\n\/\/<\/pre>\nOk. This error is much more precise. Looks like that RMAN found more the one database called DBIT121 in the catalog, and so RMAN does not know, on which DBID to perform the requested command. Ok. So let’s connect to the RMAN catalog and check if this is really the case.<\/p>\n
SQL> SELECT DB.DB_KEY,DB.DB_ID, DB.CURR_DBINC_KEY, DBINC.DB_NAME\n FROM DB, DBINC\n WHERE DB.CURR_DBINC_KEY = DBINC.DBINC_KEY\n AND DBINC.DB_NAME = 'DBIT121' ; 2 3 4\n\n DB_KEY DB_ID CURR_DBINC_KEY DB_NAME\n---------- ---------- -------------- --------\n 1 642589239 2 DBIT121\n 546780 644484523 546781 DBIT121<\/pre>\nIndeed. I do have two different DBID’s pointing to the same DB_NAME. Kinda confusing for RMAN. But which one is the one that have been backed up. We could query the RC_BACKUP_SET and RC_BACKUP_PIECE views to find that out.<\/p>\n
SQL> SELECT RBS.DB_KEY\n , RD.NAME\n , RBS.DB_ID\n 2 3 4 , RBS.BS_KEY\n , RBS.RECID\n , RBS.STAMP\n , RBS.BACKUP_TYPE\n , RBS.START_TIME, STATUS\n 5 6 7 8 9 FROM RC_BACKUP_SET RBS, RC_DATABASE RD\n WHERE RBS.DB_KEY=RD.DB_KEY\n AND RBS.DB_ID=RD.DBID\n AND RD.NAME='DBIT121' ; 10 11 12\n...\n...\n\n DB_KEY NAME DB_ID BS_KEY RECID STAMP B START_TIM S\n---------- -------- ---------- ---------- ---------- ---------- - --------- -\n 546780 DBIT121 644484523 555608 3070 936496831 I 21-FEB-17 A\n 546780 DBIT121 644484523 555609 3071 936496832 I 21-FEB-17 A\n 546780 DBIT121 644484523 555610 3072 936496836 D 21-FEB-17 A\n 546780 DBIT121 644484523 555611 3073 936496860 D 21-FEB-17 A\n 546780 DBIT121 644484523 555612 3074 936496875 D 21-FEB-17 A\n 546780 DBIT121 644484523 555613 3075 936496884 D 21-FEB-17 A\n 546780 DBIT121 644484523 555614 3076 936496890 D 21-FEB-17 A\n 546780 DBIT121 644484523 555615 3077 936496895 L 21-FEB-17 A\n 546780 DBIT121 644484523 555616 3078 936496897 L 21-FEB-17 A\n 546780 DBIT121 644484523 555617 3079 936496897 L 21-FEB-17 A\n 546780 DBIT121 644484523 555618 3080 936496898 D 21-FEB-17 A\n\n DB_KEY NAME DB_ID BS_KEY RECID STAMP B START_TIM S\n---------- -------- ---------- ---------- ---------- ---------- - --------- -\n 546780 DBIT121 644484523 555619 3081 936496900 D 21-FEB-17 A\n 546780 DBIT121 644484523 555620 3082 936498788 D 21-FEB-17 A\n 546780 DBIT121 644484523 555621 3083 936502389 D 21-FEB-17 A\n 546780 DBIT121 644484523 555622 3084 936505991 D 21-FEB-17 A\n 546780 DBIT121 644484523 555623 3085 936509589 D 21-FEB-17 A\n 546780 DBIT121 644484523 555624 3086 936513189 D 21-FEB-17 A\n 546780 DBIT121 644484523 555625 3087 936516788 D 21-FEB-17 A\n 546780 DBIT121 644484523 555626 3088 936520387 D 21-FEB-17 A\n 546780 DBIT121 644484523 555627 3089 936523988 D 21-FEB-17 A\n 546780 DBIT121 644484523 555628 3090 936527608 D 21-FEB-17 A\n 546780 DBIT121 644484523 555629 3091 936531188 D 21-FEB-17 A\n...\n...<\/pre>\nAfter checking the output, I see that DBID 644484523 is the correct one, and DBID 642589239 is the one I want to get rid of.<\/p>\n
To do so, we can shutdown the Standby database and start it up with nomount. The reason for that, is that you can’t issue the SET DBID command against a database which is mounted or open.<\/p>\n
RMAN> SET DBID=642589239;\n\nexecuting command: SET DBID\nRMAN-00571: ===========================================================\nRMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============\nRMAN-00571: ===========================================================\nRMAN-03002: failure of set command at 02\/21\/2017 13:15:26\nRMAN-06188: cannot use command when connected to a mounted target database<\/pre>\nOk. Let’s go the nomount and execute the “unregister database;” command after the correct DBID is set.<\/p>\n
$ rman target sys\/welcome1 catalog \/@rcat\n\nRecovery Manager: Release 12.1.0.2.0 - Production on Tue Feb 21 14:25:10 2017\nCopyright (c) 1982, 2014, Oracle and\/or its affiliates. All rights reserved.\n\nconnected to target database: DBIT121 (not mounted)\nconnected to recovery catalog database\n\nRMAN> SET DBID=642589239;\n\nexecuting command: SET DBID\ndatabase name is \"DBIT121\" and DBID is 642589239\n\nRMAN> unregister database;\n\ndatabase name is \"DBIT121\" and DBID is 642589239\n\nDo you really want to unregister the database (enter YES or NO)? YES\ndatabase unregistered from the recovery catalog\n\nRMAN><\/pre>\nLet’s check the RMAN catalog again.<\/p>\n
SQL> SELECT DB.DB_KEY, DB.DB_ID, DB.CURR_DBINC_KEY, DBINC.DB_NAME\n FROM DB, DBINC\n WHERE DB.CURR_DBINC_KEY = DBINC.DBINC_KEY\n AND DBINC.DB_NAME = 'DBIT121' ; 2 3 4\n\n DB_KEY DB_ID CURR_DBINC_KEY DB_NAME\n---------- ---------- -------------- --------\n 556718 644484523 556719 DBIT121<\/pre>\nCool. Looks much better. \ud83d\ude42 Now my resync catalog from SITE1 issued from SITE2 works again.<\/p>\n
RMAN> LIST DB_UNIQUE_NAME OF DATABASE;\n\nList of Databases\nDB Key DB Name DB ID Database Role Db_unique_name\n------- ------- ----------------- --------------- ------------------\n556718 DBIT121 644484523 PRIMARY DBIT121_SITE1\n556718 DBIT121 644484523 STANDBY DBIT121_SITE2\n\nRMAN> RESYNC CATALOG FROM DB_UNIQUE_NAME 'DBIT121_SITE1';\n\nresyncing from database with DB_UNIQUE_NAME DBIT121_SITE1\nstarting full resync of recovery catalog\nfull resync complete<\/pre>\nConclusion<\/h3>\n
The RMAN DB_UNIQUE_NAME persistent setting is a quite cool feature. This is something I would really recommend when working with RMAN and Data Guard. It allows you to do actions on primary from the standby or the standby from the primary. It doesn’t matter. But take care that you don’t have multiple DBID’s pointing to the same DB in your RMAN catalog.<\/p>\n","protected":false},"excerpt":{"rendered":"
By William Sescu I do have a Data Guard environment, where I have configured the RMAN DB_UNIQUE_NAME persistent setting for my primary and the standby. With the RMAN DB_UNIQUE_NAME settings I am able to run reports my Oracle Data Guard environment from any database. I could e.g. list all archivelogs for SITE1 from SITE2 or […]<\/p>\n","protected":false},"author":27,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229,198],"tags":[209,270],"type_dbi":[],"class_list":["post-9799","post","type-post","status-publish","format-standard","hentry","category-database-administration-monitoring","category-database-management","tag-oracle-12c","tag-rman"],"acf":[],"yoast_head":"\n
Oracle 12c - How to correct the error: "RMAN-20005: target database name is ambiguous" - 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\/oracle-12c-how-to-correct-the-error-rman-20005-target-database-name-is-ambiguous\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Oracle 12c - How to correct the error: "RMAN-20005: target database name is ambiguous"\" \/>\n<meta property=\"og:description\" content=\"By William Sescu I do have a Data Guard environment, where I have configured the RMAN DB_UNIQUE_NAME persistent setting for my primary and the standby. With the RMAN DB_UNIQUE_NAME settings I am able to run reports my Oracle Data Guard environment from any database. I could e.g. list all archivelogs for SITE1 from SITE2 or […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/oracle-12c-how-to-correct-the-error-rman-20005-target-database-name-is-ambiguous\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2017-02-21T13:09:37+00:00\" \/>\n<meta name=\"author\" content=\"Oracle Team\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Oracle Team\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 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-how-to-correct-the-error-rman-20005-target-database-name-is-ambiguous\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/oracle-12c-how-to-correct-the-error-rman-20005-target-database-name-is-ambiguous\\\/\"},\"author\":{\"name\":\"Oracle Team\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/66ab87129f2d357f09971bc7936a77ee\"},\"headline\":\"Oracle 12c – How to correct the error: “RMAN-20005: target database name is ambiguous”\",\"datePublished\":\"2017-02-21T13:09:37+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/oracle-12c-how-to-correct-the-error-rman-20005-target-database-name-is-ambiguous\\\/\"},\"wordCount\":497,\"commentCount\":0,\"keywords\":[\"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-how-to-correct-the-error-rman-20005-target-database-name-is-ambiguous\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/oracle-12c-how-to-correct-the-error-rman-20005-target-database-name-is-ambiguous\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/oracle-12c-how-to-correct-the-error-rman-20005-target-database-name-is-ambiguous\\\/\",\"name\":\"Oracle 12c - How to correct the error: \\\"RMAN-20005: target database name is ambiguous\\\" - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\"},\"datePublished\":\"2017-02-21T13:09:37+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/66ab87129f2d357f09971bc7936a77ee\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/oracle-12c-how-to-correct-the-error-rman-20005-target-database-name-is-ambiguous\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/oracle-12c-how-to-correct-the-error-rman-20005-target-database-name-is-ambiguous\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/oracle-12c-how-to-correct-the-error-rman-20005-target-database-name-is-ambiguous\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Oracle 12c – How to correct the error: “RMAN-20005: target database name is ambiguous”\"}]},{\"@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\\\/66ab87129f2d357f09971bc7936a77ee\",\"name\":\"Oracle Team\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g\",\"caption\":\"Oracle Team\"},\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/author\\\/oracle-team\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Oracle 12c - How to correct the error: \"RMAN-20005: target database name is ambiguous\" - 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\/oracle-12c-how-to-correct-the-error-rman-20005-target-database-name-is-ambiguous\/","og_locale":"en_US","og_type":"article","og_title":"Oracle 12c - How to correct the error: \"RMAN-20005: target database name is ambiguous\"","og_description":"By William Sescu I do have a Data Guard environment, where I have configured the RMAN DB_UNIQUE_NAME persistent setting for my primary and the standby. With the RMAN DB_UNIQUE_NAME settings I am able to run reports my Oracle Data Guard environment from any database. I could e.g. list all archivelogs for SITE1 from SITE2 or […]","og_url":"https:\/\/www.dbi-services.com\/blog\/oracle-12c-how-to-correct-the-error-rman-20005-target-database-name-is-ambiguous\/","og_site_name":"dbi Blog","article_published_time":"2017-02-21T13:09:37+00:00","author":"Oracle Team","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Oracle Team","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/oracle-12c-how-to-correct-the-error-rman-20005-target-database-name-is-ambiguous\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/oracle-12c-how-to-correct-the-error-rman-20005-target-database-name-is-ambiguous\/"},"author":{"name":"Oracle Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee"},"headline":"Oracle 12c – How to correct the error: “RMAN-20005: target database name is ambiguous”","datePublished":"2017-02-21T13:09:37+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/oracle-12c-how-to-correct-the-error-rman-20005-target-database-name-is-ambiguous\/"},"wordCount":497,"commentCount":0,"keywords":["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-how-to-correct-the-error-rman-20005-target-database-name-is-ambiguous\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/oracle-12c-how-to-correct-the-error-rman-20005-target-database-name-is-ambiguous\/","url":"https:\/\/www.dbi-services.com\/blog\/oracle-12c-how-to-correct-the-error-rman-20005-target-database-name-is-ambiguous\/","name":"Oracle 12c - How to correct the error: \"RMAN-20005: target database name is ambiguous\" - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2017-02-21T13:09:37+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/oracle-12c-how-to-correct-the-error-rman-20005-target-database-name-is-ambiguous\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/oracle-12c-how-to-correct-the-error-rman-20005-target-database-name-is-ambiguous\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/oracle-12c-how-to-correct-the-error-rman-20005-target-database-name-is-ambiguous\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Oracle 12c – How to correct the error: “RMAN-20005: target database name is ambiguous”"}]},{"@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\/66ab87129f2d357f09971bc7936a77ee","name":"Oracle Team","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g","caption":"Oracle Team"},"url":"https:\/\/www.dbi-services.com\/blog\/author\/oracle-team\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/9799","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\/27"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=9799"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/9799\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=9799"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=9799"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=9799"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=9799"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}