In this post, I will continue my experiments with Oracle policy managed databases with Grid Infrastructure, and present one of the new features introduced with Grid Infrastructure 12c last June: the cluster configuration policies and policy sets. It allows the administrator to dynamically reconfigure all server pools at a time, with a single command, according to the business workload.<\/p>\n
To take a simple example, imagine you have two servers allocated for your production instances, and two servers allocated for you development instances. This repartition is conform to your daily workload. But you have very intensive batches running every night on your production databases. The production servers are strongly used, and you have two development servers, up and running, but not used at all. What a great resources wasting!<\/p>\n
In this case you have several solutions:<\/p>\n
1) Shut down development servers during the night because they are not used. It will at least allow energy saving \ud83d\ude42
\n2) Review your needs and allocate more server(s) to the production system
\n3) Create a crazy script to reconfigure each server pool, one by one, to accomodate the configuration to the real needs, with srvctl commands run in serial.
\n4) Use policies and policy sets<\/p>\n
As you may expect, I will develop the last solution!<\/p>\n
A policy set is a “document” (Oracle definition) which contains one or more policies. Each policy contains the configuration of all server-pools in the cluster: MIN_SIZE and MAX_SIZE, IMPORTANCE, server list, etc.<\/p>\n
It will make the administrator able to activate a policy or another, according to the workload or business needs, to dynamically and immediately change all the configuration of the cluster server-pools. For instance: use two servers for production and two servers for development during working days, and use three servers for production and one server for development during nights and week ends.<\/p>\n
First of all, there is my current configuration:<\/p>\n
[oracle@node01 ~]$ srvctl config srvpool<\/span>\nServer pool name: Free\nImportance: 0, Min: 0, Max: -1\nCategory:\nCandidate server names:\nServer pool name: Generic\nImportance: 0, Min: 0, Max: -1\nCategory:\nCandidate server names:\nServer pool name: srvprod\nImportance: 0, Min: 2, Max: 2<\/span>\nCategory: hub\nCandidate server names:\nServer pool name: srvtest\nImportance: 0, Min: 2, Max: 2<\/span>\nCategory: hub\nCandidate server names:<\/pre>\nI have two nodes running in my srvprod pool and two nodes running in the srvtest pool.<\/p>\n
An instance DB1 (prod) is running on nodes 1 and 4:<\/p>\n
[oracle@node01 ~]$ srvctl status database -d DB1\nInstance DB1_1 is running on node node01\nInstance DB1_2 is running on node node04<\/pre>\nAnd an instance DB2 (dev) is running on nodes 2 and 3:<\/p>\n
[oracle@node01 ~]$ srvctl status database -d DB2\nInstance DB2_1 is running on node node02\nInstance DB2_2 is running on node node03<\/pre>\nThe simplest way to benefit of policies and policy sets is to create a text file with the wanted configuration. Following steps explain how to proceed.<\/p>\n
Step 1: Create a new policy set<\/h3>\n
The crsctl tool offers an option to generate a new policy set file, based on the current active configuration. We must connect as grid:<\/p>\n
[grid@node01 ~]$ mkdir -p \/u00\/app\/oracle\/admin\/policies\n[grid@node01 ~]$ crsctl create policyset -file \/u00\/app\/oracle\/admin\/policies\/new_policy<\/pre>\nThe file has been generated:<\/p>\n
[grid@node01 ~]$ ll \/u00\/app\/oracle\/admin\/policies\ntotal 4\n-rw-r--r-- 1 grid oinstall 305 Apr 29 16:21 new_policy<\/span><\/pre>\n <\/p>\n
There is the file content:<\/p>\n
[grid@node01 ~]$ cat \/u00\/app\/oracle\/admin\/policies\/new_policy\nSERVER_POOL_NAMES=Free ora.srvprod ora.srvtest\nPOLICY\n\u00a0 NAME=Default<\/span>\n\u00a0 SERVERPOOL\n\u00a0\u00a0\u00a0 NAME=ora.srvprod\n\u00a0\u00a0\u00a0 IMPORTANCE=0\n\u00a0\u00a0\u00a0 MAX_SIZE=2\n\u00a0\u00a0\u00a0 MIN_SIZE=2\n\u00a0\u00a0\u00a0 SERVER_CATEGORY=ora.hub.category\n\u00a0 SERVERPOOL\n\u00a0\u00a0\u00a0 NAME=ora.srvtest\n\u00a0\u00a0\u00a0 IMPORTANCE=0\n\u00a0\u00a0\u00a0 MAX_SIZE=2\n\u00a0\u00a0\u00a0 MIN_SIZE=2\n\u00a0\u00a0\u00a0 SERVER_CATEGORY=ora.hub.category<\/pre>\nThe line “NAME=Default” corresponds to the name of the policy in the policy set. The policy set itself is represented by the file “new_policy” created above.<\/p>\n
Step 2: Update the current policy set<\/h3>\n
To update the current policy set, we just have to edit our policy set file “new_policy” and to add new policies above the Default one.<\/p>\n
As an example, imagine we want to allocate one server more for production during the nights, and to allocate all servers to the production during week ends, to disable the development instances. We append the following policies:<\/p>\n
POLICY
\n NAME=Nights<\/span>
\nSERVERPOOL
\nNAME=ora.srvprod
\nIMPORTANCE=0
\n\u00a0 MAX_SIZE=3<\/span>
\n\u00a0\u00a0\u00a0 MIN_SIZE=3<\/span>
\nSERVER_CATEGORY=ora.hub.category
\nSERVERPOOL
\nNAME=ora.srvtest
\nIMPORTANCE=0
\n MAX_SIZE=1<\/span>
\n\u00a0\u00a0\u00a0 MIN_SIZE=1<\/span>
\nSERVER_CATEGORY=ora.hub.category
\nPOLICY
\n\u00a0 NAME=WeekEnds<\/span>
\nSERVERPOOL
\nNAME=ora.srvprod
\nIMPORTANCE=0
\n\u00a0 MAX_SIZE=4<\/span>
\n\u00a0\u00a0\u00a0 MIN_SIZE=4<\/span>
\nSERVER_CATEGORY=ora.hub.category
\nSERVERPOOL
\nNAME=ora.srvtest
\nIMPORTANCE=0
\nMAX_SIZE=0<\/span>
\n\u00a0\u00a0\u00a0 MIN_SIZE=0<\/span>
\nSERVER_CATEGORY=ora.hub.category<\/p>\nOnce the file is edited, it must be loaded into the policy set configuration using crsctl:<\/p>\n
[grid@node01 ~]$ crsctl modify policyset<\/span> -file \/u00\/app\/oracle\/admin\/policies\/new_policy<\/pre>\n <\/p>\n
Step 3: Enable a new policy<\/h3>\n
Our policy set now contains three policies (Default, Nights and WeekEnds). The currently enabled policy is “Default”:<\/p>\n
[grid@node01 ~]$ crsctl status policyset<\/span> | grep -i last\nLAST_ACTIVATED_POLICY=Default<\/pre>\nWe are going to enable the “Nights” policy and wee what happens. To enable a policy, use the following crsctl command as grid:<\/p>\n
[grid@node01 ~]$ crsctl modify policyset<\/span> -attr \"LAST_ACTIVATED_POLICY=Nights\"\nCRS-2673: Attempting to stop 'ora.db2.db' on 'node02'\nCRS-2677: Stop of 'ora.db2.db' on 'node02' succeeded\nCRS-2672: Attempting to start 'ora.db1.db' on 'node02'\nCRS-2676: Start of 'ora.db1.db' on 'node02' succeeded<\/pre>\nIn the previous output, we can see on node02 that Oracle has stopped DB2 and started DB1 instead. We can confirm with srvctl:<\/p>\n
[grid@node01 ~]$ srvctl status srvpool\nServer pool name: Free\nActive servers count: 0\nServer pool name: Generic\nActive servers count: 0\nServer pool name: srvprod<\/span>\nActive servers count: 3<\/span>\nServer pool name: srvtest<\/span>\nActive servers count: 1<\/span>\n[grid@node01 ~]$ srvctl status database -d DB1\nInstance DB1_1 is running on node node01\nInstance DB1_2 is running on node node04\nInstance DB1_3 is running on node node02\n[grid@node01 ~]$ srvctl status database -d DB2\nInstance DB2_2 is running on node node03<\/pre>\nNow I enable the “WeekEnds” policy. The remaing development server will be allocated to the production server pool, and 4 production instances will be running:<\/p>\n
[grid@node01 ~]$ crsctl modify policyset -attr \"LAST_ACTIVATED_POLICY=WeekEnds\"\nCRS-2673: Attempting to stop 'ora.db2.db' on 'node03'\nCRS-2677: Stop of 'ora.db2.db' on 'node03' succeeded\nCRS-2672: Attempting to start 'ora.DB1.db' on 'node03'\nCRS-2676: Start of 'ora.DB1.db' on 'node03' succeeded<\/pre>\nAll nodes are now part of the production pool:<\/p>\n
[grid@node01 ~]$ srvctl status srvpool\nServer pool name: Free\nActive servers count: 0\nServer pool name: Generic\nActive servers count: 0\nServer pool name: srvprod<\/span>\nActive servers count: 4<\/span>\nServer pool name: srvtest\nActive servers count: 0<\/pre>\nFour production instances are opened:<\/p>\n
[grid@node01 ~]$ srvctl status database -d DB1\nInstance DB1_1 is running on node node01\nInstance DB1_2 is running on node node04\nInstance DB1_3 is running on node node02\nInstance DB1_4 is running on node node03<\/pre>\nAnd the service for development is completely down:<\/p>\n
[grid@node01 ~]$ srvctl status database -d DB2\nDatabase is not running.<\/pre>\nTo reset to the initial policy, just use the same command with the “Default” policy attribute:<\/p>\n
[grid@node01 ~]$ crsctl modify policyset -attr “LAST_ACTIVATED_POLICY=Default”<\/p>\n
Conclusion<\/h3>\n
This feature represents an easy way to configure a whole policy managed cluster at will. I have demonstrated how to edit a policy set using a text file generated using crsctl, but Oracle also documented how to manually definea policy set with command line. In my opinion, this is most fastidious and the text file is a better choice.<\/p>\n
I only regret that Oracle has not created a way to enable policies according to the database workload, or to schedule policies over the time. Here, we must manually enable the policy or use the crontab…<\/p>\n","protected":false},"excerpt":{"rendered":"
In this post, I will continue my experiments with Oracle policy managed databases with Grid Infrastructure, and present one of the new features introduced with Grid Infrastructure 12c last June: the cluster configuration policies and policy sets. It allows the administrator to dynamically reconfigure all server pools at a time, with a single command, according […]<\/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":[198],"tags":[456,17,209,216,446],"type_dbi":[],"class_list":["post-3724","post","type-post","status-publish","format-standard","hentry","category-database-management","tag-grid-infrastructure","tag-oracle-11g","tag-oracle-12c","tag-oracle-rac","tag-policy-managed-databases"],"acf":[],"yoast_head":"\n
Oracle policy managed databases: Policies and policy sets - 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-policy-managed-databases-policies-and-policy-sets\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Oracle policy managed databases: Policies and policy sets\" \/>\n<meta property=\"og:description\" content=\"In this post, I will continue my experiments with Oracle policy managed databases with Grid Infrastructure, and present one of the new features introduced with Grid Infrastructure 12c last June: the cluster configuration policies and policy sets. It allows the administrator to dynamically reconfigure all server pools at a time, with a single command, according […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/oracle-policy-managed-databases-policies-and-policy-sets\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2014-05-20T19:32:00+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-policy-managed-databases-policies-and-policy-sets\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/oracle-policy-managed-databases-policies-and-policy-sets\\\/\"},\"author\":{\"name\":\"Oracle Team\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/66ab87129f2d357f09971bc7936a77ee\"},\"headline\":\"Oracle policy managed databases: Policies and policy sets\",\"datePublished\":\"2014-05-20T19:32:00+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/oracle-policy-managed-databases-policies-and-policy-sets\\\/\"},\"wordCount\":835,\"commentCount\":0,\"keywords\":[\"Grid Infrastructure\",\"Oracle 11g\",\"Oracle 12c\",\"Oracle RAC\",\"Policy-managed databases\"],\"articleSection\":[\"Database management\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/oracle-policy-managed-databases-policies-and-policy-sets\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/oracle-policy-managed-databases-policies-and-policy-sets\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/oracle-policy-managed-databases-policies-and-policy-sets\\\/\",\"name\":\"Oracle policy managed databases: Policies and policy sets - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\"},\"datePublished\":\"2014-05-20T19:32:00+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/66ab87129f2d357f09971bc7936a77ee\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/oracle-policy-managed-databases-policies-and-policy-sets\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/oracle-policy-managed-databases-policies-and-policy-sets\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/oracle-policy-managed-databases-policies-and-policy-sets\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Oracle policy managed databases: Policies and policy sets\"}]},{\"@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 policy managed databases: Policies and policy sets - 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-policy-managed-databases-policies-and-policy-sets\/","og_locale":"en_US","og_type":"article","og_title":"Oracle policy managed databases: Policies and policy sets","og_description":"In this post, I will continue my experiments with Oracle policy managed databases with Grid Infrastructure, and present one of the new features introduced with Grid Infrastructure 12c last June: the cluster configuration policies and policy sets. It allows the administrator to dynamically reconfigure all server pools at a time, with a single command, according […]","og_url":"https:\/\/www.dbi-services.com\/blog\/oracle-policy-managed-databases-policies-and-policy-sets\/","og_site_name":"dbi Blog","article_published_time":"2014-05-20T19:32:00+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-policy-managed-databases-policies-and-policy-sets\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/oracle-policy-managed-databases-policies-and-policy-sets\/"},"author":{"name":"Oracle Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee"},"headline":"Oracle policy managed databases: Policies and policy sets","datePublished":"2014-05-20T19:32:00+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/oracle-policy-managed-databases-policies-and-policy-sets\/"},"wordCount":835,"commentCount":0,"keywords":["Grid Infrastructure","Oracle 11g","Oracle 12c","Oracle RAC","Policy-managed databases"],"articleSection":["Database management"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/oracle-policy-managed-databases-policies-and-policy-sets\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/oracle-policy-managed-databases-policies-and-policy-sets\/","url":"https:\/\/www.dbi-services.com\/blog\/oracle-policy-managed-databases-policies-and-policy-sets\/","name":"Oracle policy managed databases: Policies and policy sets - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2014-05-20T19:32:00+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/oracle-policy-managed-databases-policies-and-policy-sets\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/oracle-policy-managed-databases-policies-and-policy-sets\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/oracle-policy-managed-databases-policies-and-policy-sets\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Oracle policy managed databases: Policies and policy sets"}]},{"@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\/3724","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=3724"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/3724\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=3724"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=3724"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=3724"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=3724"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}