{"id":10787,"date":"2018-01-24T16:57:07","date_gmt":"2018-01-24T15:57:07","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/explain-plan-format\/"},"modified":"2018-01-24T16:57:07","modified_gmt":"2018-01-24T15:57:07","slug":"explain-plan-format","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/explain-plan-format\/","title":{"rendered":"Explain Plan format"},"content":{"rendered":"

By Franck Pachot<\/h2>\n

.
\nThe DBMS_XPLAN format accepts a lot of options, which are not all documented. Here is a small recap of available information.<\/p>\n

The minimum that is displayed is the Plan Line Id, the Operation, and the Object Name. You can add columns and\/or sections with options, such as ‘rows’, optionally starting with a ‘+’ like ‘+rows’. Some options group several additional information, such ‘typical’, which is also the default, or ‘basic’, ‘all’, ‘advanced’. You can choose one of them and remove some columns, with ‘-‘, such as ‘typical -rows -bytes -cost -plan_hash -predicate -remote -parallel -partition -note’. Finally, from an cursor executed with plan statistics, you can show all execution statistics with ‘allstats’, and the last execution statistics with ‘allstats last’. Subsets of ‘allstats’ are ‘rowstats’, ‘memstats’, ‘iostats’, buffstats’.<\/p>\n

Of course, the column\/section is displayed only if the information is present.<\/p>\n

This blog post shows what is display by which option, as of 12c<\/i>R2, and probably with some missing combinations.
\n<\/p>\n

+plan_hash, or BASIC<\/h3>\n
\nPLAN_TABLE_OUTPUT\n-----------------\nPlan hash value: 1338588353\n<\/code><\/pre>\n
Plan hash value: is displayed by ‘basic +plan_hash’ or ‘typical’ or ‘all’ or ‘advanced’<\/p>\n
+rows +bytes +cost +partition +parallel, or TYPICAL<\/h3>\n
\n-----------------------------------------------------------------------------------------------------------------------------------\n| Id  | Operation                 | Name     | Rows  | Bytes | Cost (%CPU)| Time     | Pstart| Pstop | TQ\/Ins |IN-OUT| PQ Distrib |\n-----------------------------------------------------------------------------------------------------------------------------------\n|   0 | SELECT STATEMENT          |          |   287 | 19516 |     5  (20)| 00:00:01 |       |       |        |      |            |\n|   1 |  PX COORDINATOR           |          |       |       |            |          |       |       |        |      |            |\n|   2 |   PX SEND QC (ORDER)      | :TQ10002 |   287 | 19516 |     5  (20)| 00:00:01 |       |       |  Q1,02 | P->S | QC (ORDER) |\n|   3 |    SORT ORDER BY          |          |   287 | 19516 |     5  (20)| 00:00:01 |       |       |  Q1,02 | PCWP |            |\n|   4 |     PX RECEIVE            |          |   287 | 19516 |     4   (0)| 00:00:01 |       |       |  Q1,02 | PCWP |            |\n|   5 |      PX SEND RANGE        | :TQ10001 |   287 | 19516 |     4   (0)| 00:00:01 |       |       |  Q1,01 | P->P | RANGE      |\n|*  6 |       HASH JOIN           |          |   287 | 19516 |     4   (0)| 00:00:01 |       |       |  Q1,01 | PCWP |            |\n|   7 |        PX BLOCK ITERATOR  |          |    14 |   532 |     2   (0)| 00:00:01 |     1 |     1 |  Q1,01 | PCWC |            |\n|   8 |         TABLE ACCESS FULL | EMP      |    14 |   532 |     2   (0)| 00:00:01 |     1 |     1 |  Q1,01 | PCWP |            |\n|   9 |        BUFFER SORT        |          |       |       |            |          |       |       |  Q1,01 | PCWC |            |\n|  10 |         PX RECEIVE        |          |    82 |  2460 |     2   (0)| 00:00:01 |       |       |  Q1,01 | PCWP |            |\n|  11 |          PX SEND BROADCAST| :TQ10000 |    82 |  2460 |     2   (0)| 00:00:01 |       |       |        | S->P | BROADCAST  |\n|  12 |           REMOTE          | DEPT     |    82 |  2460 |     2   (0)| 00:00:01 |       |       | LOOPB~ | R->S |            |\n-----------------------------------------------------------------------------------------------------------------------------------\n<\/code><\/pre>\n
Rows or E-Rows: is displayed by ‘basic +rows’ or ‘typical’ or ‘all’ or ‘advanced’
\nBytes or E-Bytes: is displayed by ‘basic +bytes’ or ‘typical’ or ‘all’ or ‘advanced’
\nCost: is displayed by ‘basic +cost’ or ‘typical’ or ‘all’ or ‘advanced’
\nTmpSpc or E-Temp: is displayed by ‘basic +bytes’ or ‘typical’ or ‘all’ or ‘advanced’
\nTime or E-Time: is displayed by ‘typical’ or ‘all’ or ‘advanced’
\nPstart\/Pstop: is displayed by ‘basic +partition’ or ‘typical’ or ‘all’ or ‘advanced’
\nTQ\/Ins, IN-OUT, PQ Distrib: is displayed by ‘basic +parallel’ or ‘typical’ or ‘all’ or ‘advanced’<\/p>\n
The ‘A-‘ and ‘E-‘ prefixes are used when displaying execution statistics, to differentiate estimations with actual numbers<\/p>\n
+alias<\/h3>\n
\nQuery Block Name \/ Object Alias (identified by operation id):\n-------------------------------------------------------------\n \n   1 - SEL$58A6D7F6\n   8 - SEL$58A6D7F6 \/ EMP@SEL$1\n  12 - SEL$58A6D7F6 \/ DEPT@SEL$1\n<\/code><\/pre>\n
Query Block Name \/ Object Alias: is displayed by ‘basic +alias’ or ‘typical +alias’ or ‘all’ or ‘advanced’<\/p>\n
+outline<\/h3>\n
\nOutline Data\n-------------\n \n  \/*+\n      BEGIN_OUTLINE_DATA\n      PQ_DISTRIBUTE(@\"SEL$58A6D7F6\" \"DEPT\"@\"SEL$1\" NONE BROADCAST)\n      USE_HASH(@\"SEL$58A6D7F6\" \"DEPT\"@\"SEL$1\")\n      LEADING(@\"SEL$58A6D7F6\" \"EMP\"@\"SEL$1\" \"DEPT\"@\"SEL$1\")\n      FULL(@\"SEL$58A6D7F6\" \"DEPT\"@\"SEL$1\")\n      FULL(@\"SEL$58A6D7F6\" \"EMP\"@\"SEL$1\")\n      OUTLINE(@\"SEL$1\")\n      OUTLINE(@\"SEL$2\")\n      MERGE(@\"SEL$1\" >\"SEL$2\")\n      OUTLINE_LEAF(@\"SEL$58A6D7F6\")\n      ALL_ROWS\n      DB_VERSION('12.2.0.1')\n      OPTIMIZER_FEATURES_ENABLE('12.2.0.1')\n      IGNORE_OPTIM_EMBEDDED_HINTS\n      END_OUTLINE_DATA\n  *\/\n<\/code><\/pre>\n
Outline Data: is displayed by ‘basic +outline’ or ‘typical +outline’ or ‘all +outline’ or ‘advanced’<\/p>\n
+peeked_binds<\/h3>\n
\nPeeked Binds (identified by position):\n--------------------------------------\n \n   1 - :X (VARCHAR2(30), CSID=873): 'x'\n<\/code><\/pre>\n
Peeked Binds: is displayed by ‘basic +peeked_binds’ or ‘typical +peeked_binds’ or ‘all +outline’ or ‘advanced’<\/p>\n
+predicate<\/h3>\n
\nPredicate Information (identified by operation id):\n---------------------------------------------------\n \n   6 - access(\"EMP\".\"DEPTNO\"=\"DEPT\".\"DEPTNO\")\n<\/code><\/pre>\n
Predicate Information: is displayed by ‘basic +predicate’ or ‘typical’ or ‘all’ or ‘advanced’<\/p>\n
+column<\/h3>\n
\nColumn Projection Information (identified by operation id):\n-----------------------------------------------------------\n \n   1 - INTERNAL_FUNCTION(\"DEPT\".\"DEPTNO\")[22], \"EMP\".\"EMPNO\"[NUMBER,22], \"EMP\".\"ENAME\"[VARCHAR2,10],\n       \"EMP\".\"JOB\"[VARCHAR2,9], \"EMP\".\"MGR\"[NUMBER,22], \"EMP\".\"HIREDATE\"[DATE,7], \"EMP\".\"SAL\"[NUMBER,22],\n       \"EMP\".\"COMM\"[NUMBER,22], \"DEPT\".\"DNAME\"[VARCHAR2,14], \"DEPT\".\"LOC\"[VARCHAR2,13]\n   2 - (#keys=0) INTERNAL_FUNCTION(\"DEPT\".\"DEPTNO\")[22], \"EMP\".\"EMPNO\"[NUMBER,22], \"EMP\".\"ENAME\"[VARCHAR2,10],\n       \"EMP\".\"JOB\"[VARCHAR2,9], \"EMP\".\"MGR\"[NUMBER,22], \"EMP\".\"HIREDATE\"[DATE,7], \"EMP\".\"SAL\"[NUMBER,22],\n       \"EMP\".\"COMM\"[NUMBER,22], \"DEPT\".\"DNAME\"[VARCHAR2,14], \"DEPT\".\"LOC\"[VARCHAR2,13]\n   3 - (#keys=1) INTERNAL_FUNCTION(\"DEPT\".\"DEPTNO\")[22], \"EMP\".\"EMPNO\"[NUMBER,22], \"EMP\".\"ENAME\"[VARCHAR2,10],\n       \"EMP\".\"JOB\"[VARCHAR2,9], \"EMP\".\"MGR\"[NUMBER,22], \"EMP\".\"HIREDATE\"[DATE,7], \"EMP\".\"SAL\"[NUMBER,22],\n       \"EMP\".\"COMM\"[NUMBER,22], \"DEPT\".\"DNAME\"[VARCHAR2,14], \"DEPT\".\"LOC\"[VARCHAR2,13]\n   4 - INTERNAL_FUNCTION(\"DEPT\".\"DEPTNO\")[22], \"EMP\".\"EMPNO\"[NUMBER,22], \"EMP\".\"ENAME\"[VARCHAR2,10],\n       \"EMP\".\"JOB\"[VARCHAR2,9], \"EMP\".\"MGR\"[NUMBER,22], \"EMP\".\"HIREDATE\"[DATE,7], \"EMP\".\"SAL\"[NUMBER,22],\n       \"EMP\".\"COMM\"[NUMBER,22], \"DEPT\".\"DNAME\"[VARCHAR2,14], \"DEPT\".\"LOC\"[VARCHAR2,13]\n<\/code><\/pre>\n
Column Projection Information: is displayed by ‘basic +projection’ or ‘typical +projection’ or ‘all’ or ‘advanced’<\/p>\n
+remote<\/h3>\n
\nRemote SQL Information (identified by operation id):\n----------------------------------------------------\n \n  12 - SELECT \"DEPTNO\",\"DNAME\",\"LOC\" FROM \"DEPT\" \"DEPT\" (accessing 'LOOPBACK' )\n<\/code><\/pre>\n
Remote SQL Information: is displayed by ‘basic +remote’ or ‘typical’ or ‘all’ or ‘advanced’<\/p>\n
+metrics<\/h3>\n
\nSql Plan Directive information:\n-------------------------------\n \n  Used directive ids:\n    9695481911885124390\n<\/code><\/pre>\n
Sql Plan Directive information: is displayed by ‘+metrics’<\/p>\n
+note<\/h3>\n
The Note section can show information about SQL Profiles, SQL Patch, SQL Plan Baseline, Outlines, Dynamic Sampling, Degree of Parallelism, Parallel Query, Parallel DML, Create Index Size, Cardinality Feedback, Rely Constraints used for transformation, Sub-Optimal XML, Adaptive Plan, GTT private statistics,…<\/p>\n
\nNote\n-----\n   - Degree of Parallelism is 2 because of table property\n   - dynamic statistics used: dynamic sampling (level=2)\n   - 1 Sql Plan Directive used for this statement\n   - this is an adaptive plan (rows marked '-' are inactive)\n<\/code><\/pre>\n
Note: is displayed by ‘basic +note’ or ‘typical’ or ‘all’ or ‘advanced’<\/p>\n
+adaptive<\/h3>\n
\n---------------------------------------------------------------------------------------\n|   Id  | Operation                              | Name         |Starts|E-Rows| A-Rows|\n---------------------------------------------------------------------------------------\n|     0 | SELECT STATEMENT                       |              |    1 |      |     0 |\n|     1 |  HASH UNIQUE                           |              |    1 |    1 |     0 |\n|  *  2 |   HASH JOIN SEMI                       |              |    1 |    1 |     0 |\n|-    3 |    NESTED LOOPS SEMI                   |              |    1 |    1 |     7 |\n|-    4 |     STATISTICS COLLECTOR               |              |    1 |      |     7 |\n|  *  5 |      TABLE ACCESS FULL                 | DEPARTMENTS  |    1 |    1 |     7 |\n|- *  6 |     TABLE ACCESS BY INDEX ROWID BATCHED| EMPLOYEES    |    0 |    1 |     0 |\n|- *  7 |      INDEX RANGE SCAN                  | EMP_DEP_IX   |    0 |   10 |     0 |\n|  *  8 |    TABLE ACCESS FULL                   | EMPLOYEES    |    1 |    1 |     1 |\n---------------------------------------------------------------------------------------\n<\/code><\/pre>\n
Inactive branches of adaptive plan: is displayed by ‘+adaptive’<\/p>\n
+report<\/h3>\n
\nReoptimized plan:\n-----------------\nThis cursor is marked for automatic reoptimization.  The plan that is\nexpected to be chosen on the next execution is displayed below.\n<\/code><\/pre>\n
Reoptimized plan: is displayed by ‘+report’<\/p>\n
ALLSTATS<\/h3>\n
\n---------------------------------------------------------------------------------------------------------------------------\n| Id  | Operation                 | Name     | Starts | E-Rows | A-Rows |   A-Time   | Buffers |  OMem |  1Mem |  O\/1\/M   |\n---------------------------------------------------------------------------------------------------------------------------\n<\/code><\/pre>\n
Starts: is displayed by ‘basic +rowstats’, ‘basic +allstats’
\nA-Rows: is displayed by ‘basic +rowstats’, ‘basic +allstats’
\nA-Time: is displayed by ‘typical +rowstats’, ‘basic +allstats’
\nBuffers, Reads, Writes: is displayed by ‘basic +buffstats’, ‘basic +iostats’, ‘basic +allstats’
\nOMem, 1Mem, Used-Mem, O\/1\/M, Used-Mem: is displayed by ‘basic +memstats’, ‘basic +allstats’
\nMax-Tmp,Used-Tmp is displayed by ‘basic +memstats’, ‘typical +allstats’<\/p>\n
With summed stats, O\/1\/M and Max-Tmp are used for the headers. With last stats, Used-Mem and Used-Tmp.<\/p>\n","protected":false},"excerpt":{"rendered":"
By Franck Pachot . The DBMS_XPLAN format accepts a lot of options, which are not all documented. Here is a small recap of available information. The minimum that is displayed is the Plan Line Id, the Operation, and the Object Name. You can add columns and\/or sections with options, such as ‘rows’, optionally starting with […]<\/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":[59],"tags":[451,96],"type_dbi":[],"class_list":["post-10787","post","type-post","status-publish","format-standard","hentry","category-oracle","tag-dbms_xplan","tag-oracle"],"acf":[],"yoast_head":"\nExplain Plan format - 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\/explain-plan-format\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Explain Plan format\" \/>\n<meta property=\"og:description\" content=\"By Franck Pachot . The DBMS_XPLAN format accepts a lot of options, which are not all documented. Here is a small recap of available information. The minimum that is displayed is the Plan Line Id, the Operation, and the Object Name. You can add columns and\/or sections with options, such as ‘rows’, optionally starting with […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/explain-plan-format\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2018-01-24T15:57:07+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=\"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\/explain-plan-format\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/explain-plan-format\/\"},\"author\":{\"name\":\"Oracle Team\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee\"},\"headline\":\"Explain Plan format\",\"datePublished\":\"2018-01-24T15:57:07+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/explain-plan-format\/\"},\"wordCount\":560,\"commentCount\":0,\"keywords\":[\"dbms_xplan\",\"Oracle\"],\"articleSection\":[\"Oracle\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/explain-plan-format\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/explain-plan-format\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/explain-plan-format\/\",\"name\":\"Explain Plan format - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2018-01-24T15:57:07+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/explain-plan-format\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/explain-plan-format\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/explain-plan-format\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Explain Plan format\"}]},{\"@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":"Explain Plan format - 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\/explain-plan-format\/","og_locale":"en_US","og_type":"article","og_title":"Explain Plan format","og_description":"By Franck Pachot . The DBMS_XPLAN format accepts a lot of options, which are not all documented. Here is a small recap of available information. The minimum that is displayed is the Plan Line Id, the Operation, and the Object Name. You can add columns and\/or sections with options, such as ‘rows’, optionally starting with […]","og_url":"https:\/\/www.dbi-services.com\/blog\/explain-plan-format\/","og_site_name":"dbi Blog","article_published_time":"2018-01-24T15:57:07+00:00","author":"Oracle Team","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Oracle Team","Est. reading time":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/explain-plan-format\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/explain-plan-format\/"},"author":{"name":"Oracle Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee"},"headline":"Explain Plan format","datePublished":"2018-01-24T15:57:07+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/explain-plan-format\/"},"wordCount":560,"commentCount":0,"keywords":["dbms_xplan","Oracle"],"articleSection":["Oracle"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/explain-plan-format\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/explain-plan-format\/","url":"https:\/\/www.dbi-services.com\/blog\/explain-plan-format\/","name":"Explain Plan format - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2018-01-24T15:57:07+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/explain-plan-format\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/explain-plan-format\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/explain-plan-format\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Explain Plan format"}]},{"@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\/10787","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=10787"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/10787\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=10787"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=10787"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=10787"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=10787"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}