{"id":37011,"date":"2025-02-11T17:55:59","date_gmt":"2025-02-11T16:55:59","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=37011"},"modified":"2025-03-11T10:24:56","modified_gmt":"2025-03-11T09:24:56","slug":"cleanup-after-patching","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/cleanup-after-patching\/","title":{"rendered":"Cleanup Oracle After Patching"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\" id=\"h-cleanup-oracle-home-s-after-applying-the-quarterly-release-updates\">cleanup Oracle-Home(s) <br>after applying the quarterly Release Updates<\/h2>\n\n\n\n<p>Do you suffer from the fact that release updates take longer each time?<br>Are you afraid that your hard disk will fill up because the Oracle-Home is getting bigger and bigger?<br>Here is the how-to for cleaning up your environment.  <\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-a-cleanup-option-1-for-out-of-place-patching\"><strong>A) cleanup &#8211; option 1 for Out-Of-Place patching<\/strong><\/h3>\n\n\n\n<p class=\"has-medium-font-size\">According to Oracle&#8217;s recommendations, you did &#8220;out of place patching&#8221; and have now several Oracle-Home directories.<br>All your databases are using the new ORACLE_HOME (OH) and the old OHs are now obsolete.<br>Cleaning up is not only a matter of disk space. The old Software releases contain security issues &#8211; of course. This is the very reason for patching.<\/p>\n\n\n\n<h6 class=\"wp-block-heading\" id=\"h-set-the-environment-for-the-oh-you-want-to-delete\">Set the environment for the OH you want to delete<\/h6>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: bash; title: ; notranslate\" title=\"\">\nexport ORACLE_HOME=\/u01\/app\/oracle\/product\/19.25.0\/dbhome_1\nPATH=$ORACLE_HOME\/bin:$ORACLE_HOME\/OPatch:$ORACLE_HOME\/perl\/bin:$ORACLE_HOME\/ctx\/bin\nPATH=$PATH:\/home\/oracle\/.local\/bin:\/home\/oracle\/bin:\/usr\/local\/bin:\/usr\/bin:\/usr\/ccs\/bin:\/usr\/local\/sbin:\/usr\/sbin:\/sbin\nexport PATH\nexport CV_ASSUME_DISTID=OEL8.1\n\ncd $ORACLE_HOME\/deinstall\n.\/deinstall\n   -&gt; enter required answers \u2026\n       Enter     (confirm &#x5B;LISTENER] )\n       Enter     (confirm databases &#x5B;] )\n        Y        (to confirm to delete the listed OH)\n<\/pre><\/div>\n\n\n<h6 class=\"wp-block-heading\" id=\"h-you-can-delete-the-empty-directory-now\">you can delete the empty directory, now<\/h6>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\ncd \/u01\/app\/oracle\/product\/\ndu -sh *\nrmdir 19.25.0\n<\/pre><\/div>\n\n\n<h3 class=\"wp-block-heading\" id=\"h-b-cleanup-option-2-for-out-of-place-patching\"><strong>B) cleanup &#8211; option 2 for Out-Of-Place patching<\/strong><\/h3>\n\n\n\n<p>In some cases, the deinstall does not work and gives you some error messages.<br>Now we have the option to detach AND remove the old ORACLE_HOME.<br>In this example our OH-path is:   \/u01\/app\/oracle\/product\/19.15.0.0.220419.EE<\/p>\n\n\n\n<h6 class=\"wp-block-heading\" id=\"h-first-you-need-to-find-the-home-name-for-the-oh-to-deinstall-you-might-have-to-look-into-several-subfolders-for-it\">first you need to find the &#8220;Home-Name&#8221; for the OH to deinstall &#8211; you might have to look into several subfolders for it<\/h6>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: bash; title: ; notranslate\" title=\"\">\ncd \/u01\/app\/oraInventory\/logs\nls -l\ncd InstallActions&lt;timestamp&gt;\ngrep -i ORACLE_HOME_NAME *.log\n--&gt;&gt; responds for example with:   OraDB19Home1\n<\/pre><\/div>\n\n\n<h6 class=\"wp-block-heading\" id=\"h-set-the-environment-for-the-oracle-home-to-remove-and-detach-it\">set the environment for the ORACLE_HOME to remove and DETACH it<\/h6>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: bash; title: ; notranslate\" title=\"\">\nexport ORACLE_HOME=\/u01\/app\/oracle\/product\/19.15.0.0.220419.EE\nPATH=$ORACLE_HOME\/bin:$ORACLE_HOME\/OPatch:$ORACLE_HOME\/perl\/bin:$ORACLE_HOME\/ctx\/bin\nPATH=$PATH:\/home\/oracle\/.local\/bin:\/home\/oracle\/bin:\/usr\/local\/bin:\/usr\/bin:\/usr\/ccs\/bin:\/usr\/local\/sbin:\/usr\/sbin:\/sbin\nexport PATH\nexport CV_ASSUME_DISTID=OEL8.1\n\ncd $ORACLE_HOME\/oui\/bin\n.\/runInstaller -silent -detachHome ORACLE_HOME=&quot;\/u01\/app\/oracle\/product\/19.15.0.0.220419.EE&quot; ORACLE_HOME_NAME=&quot;OraDB19Home1&quot;\n\ncd \/u01\/app\/oracle\/product\nrm -rf 19.15.0.0.220419.EE\n\n<\/pre><\/div>\n\n\n<h6 class=\"wp-block-heading\" id=\"h-and-don-t-forget-to-remove-the-obsolete-oh-from-the-oratab-file\">and don&#8217;t forget to remove the obsolete OH from the oratab file<\/h6>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: bash; title: ; notranslate\" title=\"\">\nvi \/etc\/oratab\n<\/pre><\/div>\n\n\n<h3 class=\"wp-block-heading\" id=\"h-c-cleanup-option-for-in-place-patching\"><br><strong>C) cleanup &#8211; option for IN-Place patching<\/strong><\/h3>\n\n\n\n<p>For reasons, you could not do &#8220;out of place&#8221; patching. When you have an OH which was already patched several times, the OH increased in size over time. The old patches got stored in a subdirectory for rollback reasons.<\/p>\n\n\n\n<h6 class=\"wp-block-heading\" id=\"h-simply-check-the-size-of-the-subdirectory\">Simply check the size of the subdirectory<\/h6>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: bash; title: ; notranslate\" title=\"\">\ndu -sh $ORACLE_HOME\/.patch_storage\/\n--&gt;&gt; 6.6G  .patch_storage\/\n<\/pre><\/div>\n\n\n<h5 class=\"wp-block-heading\" id=\"h-i-checked-this-for-an-oracle-home-with-up-to-7-rus-installed\"><strong>I checked this for an ORACLE_HOME with up to 7 RUs installed:<\/strong><\/h5>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: bash; title: ; notranslate\" title=\"\">\n.patch_storage with   2 RUs     3 RUs     4 RUs     5 RUs     6 RUs     7 RUs\n          Size GB      5.6       6.6        9.1       12        14        18\n<\/pre><\/div>\n\n\n<p>you can imagine that each run of opatch needs more and more time for a larger repository in directory &#8216;.patch_storage&#8217;.<br>For the first patch it goes &#8216;on the fly&#8217;. The second needs a coffee break, the third needs a lunch break \u2026<\/p>\n\n\n\n<h6 class=\"wp-block-heading\" id=\"h-with-this-command-you-can-list-your-obsolete-patches\">with this command you can list your obsolete patches<\/h6>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: bash; title: ; notranslate\" title=\"\">\nopatch util listorderedinactivepatches\n<\/pre><\/div>\n\n\n<h6 class=\"wp-block-heading\" id=\"h-now-delete-them-this-will-take-a-while-and-it-leaves-intentionally-the-last-ru-in-the-repository\">now  delete them (this will take a while) and it leaves intentionally the last RU in the repository<\/h6>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: bash; title: ; notranslate\" title=\"\">\nopatch util deleteinactivepatches\n<\/pre><\/div>\n\n\n<h6 class=\"wp-block-heading\" id=\"h-the-disk-usage-is-now-reduced-and-the-next-patch-will-run-definitively-faster\">the disk usage is now reduced, and the next patch will run definitively faster<\/h6>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: bash; title: ; notranslate\" title=\"\">\ndu -sh $ORACLE_HOME\/.patch_storage\/\n--&gt;&gt; 6.0G .patch_storage\/\n<\/pre><\/div>\n\n\n<p>I am an impatient DBA and I don&#8217;t like drinking lots of coffee while waiting for opatch to finish. This is why I love to keep my Oracle-Home directories small and smart.<br><\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-d-add-on-patch-the-opatch\">D) add on &#8211; patch the OPatch<\/h3>\n\n\n\n<p>regardless of you do in-place or out-of-place patching, you need to update your opatch with the most recent release. The very most DBAs follow the advice in p6880880_opatch_README_12.2.0.1.xy.txt<br>&#8220;Please take a backup of ORACLE_HOME\/OPatch into a dedicated backup location&#8221; and rename the folder OPatch to OPatch_<strong>old<\/strong>.<br>With the next RU, they move the current to OPatch_<strong>even_older<\/strong> or some other funny name.<br>Just to remember: the purpose of patching is to REPLACE older Software, which contains security issues, by newer releases, containing fixes.<br>Did you know that opatch contains its own <strong>Java<\/strong>? So why should we leave an outaged Java on the system as a gate for hackers?<\/p>\n\n\n\n<p>Remove it immediately after you have verified, the new release is working.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><strong>---&gt;&gt;&gt; rm -rf ORACLE_HOME\/OPatch_old<\/strong><\/pre>\n\n\n\n<p>I hope, this helps you to keep your environment clean and tidy.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>cleanup Oracle-Home(s) after applying the quarterly Release Updates Do you suffer from the fact that release updates take longer each time?Are you afraid that your hard disk will fill up because the Oracle-Home is getting bigger and bigger?Here is the how-to for cleaning up your environment. A) cleanup &#8211; option 1 for Out-Of-Place patching According [&hellip;]<\/p>\n","protected":false},"author":27,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229,198,59],"tags":[1894,808,3528,3526,3525,3527,3522,96,572,3521,3519,3520,1923],"type_dbi":[],"class_list":["post-37011","post","type-post","status-publish","format-standard","hentry","category-database-administration-monitoring","category-database-management","category-oracle","tag-cleanup","tag-delete","tag-guideline","tag-how-to","tag-inactive","tag-know-how","tag-obsolete","tag-oracle","tag-patch","tag-patches","tag-release-update","tag-remove","tag-update"],"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>Cleanup Oracle After Patching - 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\/cleanup-after-patching\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Cleanup Oracle After Patching\" \/>\n<meta property=\"og:description\" content=\"cleanup Oracle-Home(s) after applying the quarterly Release Updates Do you suffer from the fact that release updates take longer each time?Are you afraid that your hard disk will fill up because the Oracle-Home is getting bigger and bigger?Here is the how-to for cleaning up your environment. A) cleanup &#8211; option 1 for Out-Of-Place patching According [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/cleanup-after-patching\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2025-02-11T16:55:59+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-03-11T09:24:56+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=\"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\/cleanup-after-patching\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/cleanup-after-patching\/\"},\"author\":{\"name\":\"Oracle Team\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee\"},\"headline\":\"Cleanup Oracle After Patching\",\"datePublished\":\"2025-02-11T16:55:59+00:00\",\"dateModified\":\"2025-03-11T09:24:56+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/cleanup-after-patching\/\"},\"wordCount\":559,\"commentCount\":9,\"keywords\":[\"cleanup\",\"delete\",\"guideline\",\"how to\",\"inactive\",\"know how\",\"obsolete\",\"Oracle\",\"patch\",\"patches\",\"release update\",\"remove\",\"update\"],\"articleSection\":[\"Database Administration &amp; Monitoring\",\"Database management\",\"Oracle\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/cleanup-after-patching\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/cleanup-after-patching\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/cleanup-after-patching\/\",\"name\":\"Cleanup Oracle After Patching - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2025-02-11T16:55:59+00:00\",\"dateModified\":\"2025-03-11T09:24:56+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/cleanup-after-patching\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/cleanup-after-patching\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/cleanup-after-patching\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Cleanup Oracle After Patching\"}]},{\"@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":"Cleanup Oracle After Patching - 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\/cleanup-after-patching\/","og_locale":"en_US","og_type":"article","og_title":"Cleanup Oracle After Patching","og_description":"cleanup Oracle-Home(s) after applying the quarterly Release Updates Do you suffer from the fact that release updates take longer each time?Are you afraid that your hard disk will fill up because the Oracle-Home is getting bigger and bigger?Here is the how-to for cleaning up your environment. A) cleanup &#8211; option 1 for Out-Of-Place patching According [&hellip;]","og_url":"https:\/\/www.dbi-services.com\/blog\/cleanup-after-patching\/","og_site_name":"dbi Blog","article_published_time":"2025-02-11T16:55:59+00:00","article_modified_time":"2025-03-11T09:24:56+00:00","author":"Oracle Team","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Oracle Team","Est. reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/cleanup-after-patching\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/cleanup-after-patching\/"},"author":{"name":"Oracle Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee"},"headline":"Cleanup Oracle After Patching","datePublished":"2025-02-11T16:55:59+00:00","dateModified":"2025-03-11T09:24:56+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/cleanup-after-patching\/"},"wordCount":559,"commentCount":9,"keywords":["cleanup","delete","guideline","how to","inactive","know how","obsolete","Oracle","patch","patches","release update","remove","update"],"articleSection":["Database Administration &amp; Monitoring","Database management","Oracle"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/cleanup-after-patching\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/cleanup-after-patching\/","url":"https:\/\/www.dbi-services.com\/blog\/cleanup-after-patching\/","name":"Cleanup Oracle After Patching - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2025-02-11T16:55:59+00:00","dateModified":"2025-03-11T09:24:56+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/cleanup-after-patching\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/cleanup-after-patching\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/cleanup-after-patching\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Cleanup Oracle After Patching"}]},{"@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\/37011","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=37011"}],"version-history":[{"count":30,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/37011\/revisions"}],"predecessor-version":[{"id":37628,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/37011\/revisions\/37628"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=37011"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=37011"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=37011"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=37011"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}