.
\nSQL Plan Baselines is a great feature for plan stability: you capture the plans that you accept. However, if the data model changes and the accepted plans cannot reproduce, the optimizer will come with a new plan. In 18c we have a note from DBMS_XPLAN when the optimization ‘failed to use SQL plan baseline for this statement’.
\n
\nI create a table, with an index, and run a query on it using this index:<\/p>\n
\nSQL> create table DEMO as select rownum n from xmltable('1 to 1000');\nTable DEMO created.\n \nSQL> create index DEMO_N on DEMO(n);\nIndex DEMO_N created.\n \nSQL> select * from DEMO where n=1;\n \n N\n -\n 1\n<\/code><\/pre>\nThe execution plan is correct, using the index:<\/p>\n
\nSQL> select * from dbms_xplan.display_cursor();\n \nPLAN_TABLE_OUTPUT\n-----------------\nSQL_ID 4mcr18aqntpkq, child number 0\n-------------------------------------\nselect * from DEMO where n=1\n \nPlan hash value: 217077817\n \n---------------------------------------------------------------------------\n| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |\n---------------------------------------------------------------------------\n| 0 | SELECT STATEMENT | | | | 1 (100)| |\n|* 1 | INDEX RANGE SCAN| DEMO_N | 1 | 4 | 1 (0)| 00:00:01 |\n---------------------------------------------------------------------------\n \nPredicate Information (identified by operation id):\n---------------------------------------------------\n \n 1 - access(\"N\"=1)\n<\/code><\/pre>\nI’m happy with this plan, and I capture it as an accepted SQL Plan Baseline for this statemement:<\/p>\n
\nSQL> exec dbms_output.put_line( dbms_spm.load_plans_from_cursor_cache('4mcr18aqntpkq') )\nPL\/SQL procedure successfully completed.\n \nSQL> select * from dba_sql_plan_baselines;\n \n SIGNATURE SQL_HANDLE SQL_TEXT PLAN_NAME CREATOR ORIGIN PARSING_SCHEMA_NAME DESCRIPTION VERSION CREATED LAST_MODIFIED LAST_EXECUTED LAST_VERIFIED ENABLED ACCEPTED FIXED REPRODUCED AUTOPURGE ADAPTIVE OPTIMIZER_COST MODULE ACTION EXECUTIONS ELAPSED_TIME CPU_TIME BUFFER_GETS DISK_READS DIRECT_WRITES ROWS_PROCESSED FETCHES END_OF_FETCH_COUNT\n --------- ---------- -------- --------- ------- ------ ------------------- ----------- ------- ------- ------------- ------------- ------------- ------- -------- ----- ---------- --------- -------- -------------- ------ ------ ---------- ------------ -------- ----------- ---------- ------------- -------------- ------- ------------------\n 5689790730784434204 SQL_4ef632861ab7681c select * from DEMO where n=1 SQL_PLAN_4xxjkhsdbfu0wd5d62705 DEMO MANUAL-LOAD-FROM-CURSOR-CACHE DEMO 18.0.0.0.0 27-FEB-18 09.37.55.000000000 PM 27-FEB-18 09.37.55.000000000 PM YES YES NO YES YES NO 1 java@VM181 (TNS V1-V3) 3 5771 4824 82 1 0 3 6\n<\/code><\/pre>\nWhen I run the sattement again, this plan is used and DBMS_XPLAN mentions the SQL Plan BAseline that was used:<\/p>\n
\nSQL> select * from DEMO where n=1;\n \n N\n -\n 1\n \nSQL> select * from dbms_xplan.display_cursor();\n \nPLAN_TABLE_OUTPUT\n-----------------\nSQL_ID 4mcr18aqntpkq, child number 0\n-------------------------------------\nselect * from DEMO where n=1\n \nPlan hash value: 217077817\n \n---------------------------------------------------------------------------\n| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |\n---------------------------------------------------------------------------\n| 0 | SELECT STATEMENT | | | | 1 (100)| |\n|* 1 | INDEX RANGE SCAN| DEMO_N | 1 | 4 | 1 (0)| 00:00:01 |\n---------------------------------------------------------------------------\n \nPredicate Information (identified by operation id):\n---------------------------------------------------\n \n 1 - access(\"N\"=1)\n \nNote\n-----\n - SQL plan baseline SQL_PLAN_4xxjkhsdbfu0wd5d62705 used for this statement\n<\/code><\/pre>\nNow, if I drop the index, the accepted plan cannot be used:<\/p>\n
\nSQL> drop index DEMO_N;\nIndex DEMO_N dropped.\n \nSQL> select * from DEMO where n=1;\n \n N\n -\n 1\n \nSQL> select * from dbms_xplan.display_cursor();\n \nPLAN_TABLE_OUTPUT\n-----------------\nSQL_ID 4mcr18aqntpkq, child number 0\n-------------------------------------\nselect * from DEMO where n=1\n \nPlan hash value: 4000794843\n \n--------------------------------------------------------------------------\n| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |\n--------------------------------------------------------------------------\n| 0 | SELECT STATEMENT | | | | 2 (100)| |\n|* 1 | TABLE ACCESS FULL| DEMO | 1 | 4 | 2 (0)| 00:00:01 |\n--------------------------------------------------------------------------\n \nPredicate Information (identified by operation id):\n---------------------------------------------------\n \n 1 - filter(\"N\"=1)\n \nNote\n-----\n - Failed to use SQL plan baseline for this statement\n<\/code><\/pre>\nSo the new note in 18c explains that there is an SQL Plan Baseline that cannot be used. Unfortunately, there is no identification of the SQL Plan baselines.<\/p>\n
\nSQL> select * from dba_sql_plan_baselines;\n \n SIGNATURE SQL_HANDLE SQL_TEXT PLAN_NAME CREATOR ORIGIN PARSING_SCHEMA_NAME DESCRIPTION VERSION CREATED LAST_MODIFIED LAST_EXECUTED LAST_VERIFIED ENABLED ACCEPTED FIXED REPRODUCED AUTOPURGE ADAPTIVE OPTIMIZER_COST MODULE ACTION EXECUTIONS ELAPSED_TIME CPU_TIME BUFFER_GETS DISK_READS DIRECT_WRITES ROWS_PROCESSED FETCHES END_OF_FETCH_COUNT\n --------- ---------- -------- --------- ------- ------ ------------------- ----------- ------- ------- ------------- ------------- ------------- ------- -------- ----- ---------- --------- -------- -------------- ------ ------ ---------- ------------ -------- ----------- ---------- ------------- -------------- ------- ------------------\n 5689790730784434204 SQL_4ef632861ab7681c select * from DEMO where n=1 SQL_PLAN_4xxjkhsdbfu0w838f84a8 DEMO AUTO-CAPTURE DEMO 18.0.0.0.0 27-FEB-18 09.37.56.000000000 PM 27-FEB-18 09.37.56.000000000 PM YES NO NO YES YES NO 2 java@VM181 (TNS V1-V3) 0 0 0 0 0 0 0 0\n 5689790730784434204 SQL_4ef632861ab7681c select * from DEMO where n=1 SQL_PLAN_4xxjkhsdbfu0wd5d62705 DEMO MANUAL-LOAD-FROM-CURSOR-CACHE DEMO 18.0.0.0.0 27-FEB-18 09.37.55.000000000 PM 27-FEB-18 09.37.55.000000000 PM 27-FEB-18 09.37.55.000000000 PM YES YES NO YES YES NO 1 java@VM181 (TNS V1-V3) 3 5771 4824 82 1 0 3 6\n<\/code><\/pre>\nSo, because the accepted plan was not able to reproduce, because the index has been dropped, the new plan was captured but not accepted.<\/p>\n
Note that if I re-create the index but with a different name, then the accepted SQL Plan cannot be used either:<\/p>\n
\nSQL> create index DEMO_XXX on DEMO(n);\nIndex DEMO_XXX created.\n \nSQL> select * from DEMO where n=1;\n \n N\n -\n 1\n \nSQL> select * from dbms_xplan.display_cursor();\n \nPLAN_TABLE_OUTPUT\n-----------------\nSQL_ID 4mcr18aqntpkq, child number 0\n-------------------------------------\nselect * from DEMO where n=1\n \nPlan hash value: 1306684165\n \n-----------------------------------------------------------------------------\n| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |\n-----------------------------------------------------------------------------\n| 0 | SELECT STATEMENT | | | | 1 (100)| |\n|* 1 | INDEX RANGE SCAN| DEMO_XXX | 1 | 4 | 1 (0)| 00:00:01 |\n-----------------------------------------------------------------------------\n \nPredicate Information (identified by operation id):\n---------------------------------------------------\n \n 1 - access(\"N\"=1)\n \nNote\n-----\n - Failed to use SQL plan baseline for this statement\n<\/code><\/pre>\nSo, it is not a bad idea to monitor the SQL PLan Baseline which did not reproduce. We can get them from the ‘baseline_repro_fail’ mention in OTHER_XML:<\/p>\n
\nSQL> select sql_id,other_xml from v$sql_plan where other_xml like '%baseline_repro_fail%';\n \nSQL_ID OTHER_XML \n------ --------- \n4mcr18aqntpkq <other_xml><info type=\"db_version\">18.0.0.0<\/info><info type=\"parse_schema\"><![CDATA[\"DEMO\"]]><\/info><info type=\"plan_hash_full\">211349514<\/info><info type=\"plan_hash\">1306684165<\/info><info type=\"plan_hash_2\">211349514<\/info><info type=\"baseline_repro_fail\" note=\"y\">yes<\/info><outline_data><hint><![CDATA[IGNORE_OPTIM_EMBEDDED_HINTS]]><\/hint><hint><![CDATA[OPTIMIZER_FEATURES_ENABLE('18.1.0')]]><\/hint><hint><![CDATA[DB_VERSION('18.1.0')]]><\/hint><hint><![CDATA[ALL_ROWS]]><\/hint><hint><![CDATA[OUTLINE_LEAF(@\"SEL$1\")]]><\/hint><hint><![CDATA[INDEX(@\"SEL$1\" \"DEMO\"@\"SEL$1\" (\"DEMO\".\"N\"))]]><\/hint><\/outline_data><\/other_xml>\n<\/code><\/pre>\nFrom the SQL_ID I can get the SIGNATURE used by SQL Plan Management:<\/p>\n
\nSQL> select sql_id,exact_matching_signature from v$sql where sql_id='4mcr18aqntpkq';\n \nSQL_ID EXACT_MATCHING_SIGNATURE\n------ ------------------------\n4mcr18aqntpkq 5689790730784434204\n<\/code><\/pre>\nAnd then the SQL Plan Baselines:<\/p>\n
\nSQL> select * from dba_sql_plan_baselines where signature=5689790730784434204;\n \n SIGNATURE SQL_HANDLE SQL_TEXT PLAN_NAME CREATOR ORIGIN PARSING_SCHEMA_NAME DESCRIPTION VERSION CREATED LAST_MODIFIED LAST_EXECUTED LAST_VERIFIED ENABLED ACCEPTED FIXED REPRODUCED AUTOPURGE ADAPTIVE OPTIMIZER_COST MODULE ACTION EXECUTIONS ELAPSED_TIME CPU_TIME BUFFER_GETS DISK_READS DIRECT_WRITES ROWS_PROCESSED FETCHES END_OF_FETCH_COUNT\n --------- ---------- -------- --------- ------- ------ ------------------- ----------- ------- ------- ------------- ------------- ------------- ------- -------- ----- ---------- --------- -------- -------------- ------ ------ ---------- ------------ -------- ----------- ---------- ------------- -------------- ------- ------------------\n 5689790730784434204 SQL_4ef632861ab7681c select * from DEMO where n=1 SQL_PLAN_4xxjkhsdbfu0w0c98f00a DEMO AUTO-CAPTURE DEMO 18.0.0.0.0 27-FEB-18 10.02.07.000000000 PM 27-FEB-18 10.02.07.000000000 PM YES NO NO YES YES NO 1 java@VM181 (TNS V1-V3) 0 0 0 0 0 0 0 0\n 5689790730784434204 SQL_4ef632861ab7681c select * from DEMO where n=1 SQL_PLAN_4xxjkhsdbfu0w838f84a8 DEMO AUTO-CAPTURE DEMO 18.0.0.0.0 27-FEB-18 10.02.07.000000000 PM 27-FEB-18 10.02.07.000000000 PM YES NO NO YES YES NO 2 java@VM181 (TNS V1-V3) 0 0 0 0 0 0 0 0\n 5689790730784434204 SQL_4ef632861ab7681c select * from DEMO where n=1 SQL_PLAN_4xxjkhsdbfu0wd5d62705 DEMO MANUAL-LOAD-FROM-CURSOR-CACHE DEMO 18.0.0.0.0 27-FEB-18 10.02.06.000000000 PM 27-FEB-18 10.02.06.000000000 PM 27-FEB-18 10.02.06.000000000 PM YES YES NO YES YES NO 1 java@VM181 (TNS V1-V3) 3 4634 4210 75 1 0 3 6\n<\/code><\/pre>\nNow it is easy to look at the SPM baselines to understand why it did not reproduce:<\/p>\n
\nSQL> select * from dbms_xplan.display_sql_plan_baseline('SQL_4ef632861ab7681c',format=>'basic');\n \nPLAN_TABLE_OUTPUT\n-----------------\n \n--------------------------------------------------------------------------------\nSQL handle: SQL_4ef632861ab7681c\nSQL text: select * from DEMO where n=1\n--------------------------------------------------------------------------------\n \n--------------------------------------------------------------------------------\nPlan name: SQL_PLAN_4xxjkhsdbfu0w0c98f00a Plan id: 211349514\nEnabled: YES Fixed: NO Accepted: NO Origin: AUTO-CAPTURE\nPlan rows: From dictionary\n--------------------------------------------------------------------------------\n \nPlan hash value: 1306684165\n \n-------------------------------------\n| Id | Operation | Name |\n-------------------------------------\n| 0 | SELECT STATEMENT | |\n| 1 | INDEX RANGE SCAN| DEMO_XXX |\n-------------------------------------\n \n--------------------------------------------------------------------------------\nPlan name: SQL_PLAN_4xxjkhsdbfu0w838f84a8 Plan id: 2207220904\nEnabled: YES Fixed: NO Accepted: NO Origin: AUTO-CAPTURE\nPlan rows: From dictionary\n--------------------------------------------------------------------------------\n \nPlan hash value: 4000794843\n \n----------------------------------\n| Id | Operation | Name |\n----------------------------------\n| 0 | SELECT STATEMENT | |\n| 1 | TABLE ACCESS FULL| DEMO |\n----------------------------------\n \n--------------------------------------------------------------------------------\nPlan name: SQL_PLAN_4xxjkhsdbfu0wd5d62705 Plan id: 3587581701\nEnabled: YES Fixed: NO Accepted: YES Origin: MANUAL-LOAD-FROM-CURSOR-CACHE\nPlan rows: From dictionary\n--------------------------------------------------------------------------------\n \nPlan hash value: 217077817\n \n-----------------------------------\n| Id | Operation | Name |\n-----------------------------------\n| 0 | SELECT STATEMENT | |\n| 1 | INDEX RANGE SCAN| DEMO_N |\n-----------------------------------\n \n<\/code><\/pre>\nNow we can see the unaccepted plan using index DEMO_XXX and the accepted one using index DEMO_N. If we add format=>’+outline’ we can even see that they index the same column. REady to accept the new plan and remove the old one.<\/p>\n
In conclusion: check you V$SQL_PLAN.OTHER_XML for info type=”baseline_repro_fail” in 18c and you can do some housekeeping on SQL Plan baselines which do not reproduce. Because if you accepted a plan which cannot reproduce, you may have a problem, and better address this pro-actively.<\/p>\n","protected":false},"excerpt":{"rendered":"
By Franck Pachot . SQL Plan Baselines is a great feature for plan stability: you capture the plans that you accept. However, if the data model changes and the accepted plans cannot reproduce, the optimizer will come with a new plan. In 18c we have a note from DBMS_XPLAN when the optimization ‘failed to use […]<\/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":[1184,664],"type_dbi":[],"class_list":["post-10999","post","type-post","status-publish","format-standard","hentry","category-oracle","tag-oracle-18c","tag-spm"],"acf":[],"yoast_head":"\n
18c dbms_xplan note about failed SQL Plan Baseline - 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\/18c-dbms_xplan-note-about-failed-sql-plan-baseline\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"18c dbms_xplan note about failed SQL Plan Baseline\" \/>\n<meta property=\"og:description\" content=\"By Franck Pachot . SQL Plan Baselines is a great feature for plan stability: you capture the plans that you accept. However, if the data model changes and the accepted plans cannot reproduce, the optimizer will come with a new plan. In 18c we have a note from DBMS_XPLAN when the optimization ‘failed to use […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/18c-dbms_xplan-note-about-failed-sql-plan-baseline\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2018-02-27T20:17:53+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=\"8 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\/18c-dbms_xplan-note-about-failed-sql-plan-baseline\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/18c-dbms_xplan-note-about-failed-sql-plan-baseline\/\"},\"author\":{\"name\":\"Oracle Team\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee\"},\"headline\":\"18c dbms_xplan note about failed SQL Plan Baseline\",\"datePublished\":\"2018-02-27T20:17:53+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/18c-dbms_xplan-note-about-failed-sql-plan-baseline\/\"},\"wordCount\":382,\"commentCount\":0,\"keywords\":[\"Oracle 18c\",\"SPM\"],\"articleSection\":[\"Oracle\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/18c-dbms_xplan-note-about-failed-sql-plan-baseline\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/18c-dbms_xplan-note-about-failed-sql-plan-baseline\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/18c-dbms_xplan-note-about-failed-sql-plan-baseline\/\",\"name\":\"18c dbms_xplan note about failed SQL Plan Baseline - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2018-02-27T20:17:53+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/18c-dbms_xplan-note-about-failed-sql-plan-baseline\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/18c-dbms_xplan-note-about-failed-sql-plan-baseline\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/18c-dbms_xplan-note-about-failed-sql-plan-baseline\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"18c dbms_xplan note about failed SQL Plan Baseline\"}]},{\"@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":"18c dbms_xplan note about failed SQL Plan Baseline - 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\/18c-dbms_xplan-note-about-failed-sql-plan-baseline\/","og_locale":"en_US","og_type":"article","og_title":"18c dbms_xplan note about failed SQL Plan Baseline","og_description":"By Franck Pachot . SQL Plan Baselines is a great feature for plan stability: you capture the plans that you accept. However, if the data model changes and the accepted plans cannot reproduce, the optimizer will come with a new plan. In 18c we have a note from DBMS_XPLAN when the optimization ‘failed to use […]","og_url":"https:\/\/www.dbi-services.com\/blog\/18c-dbms_xplan-note-about-failed-sql-plan-baseline\/","og_site_name":"dbi Blog","article_published_time":"2018-02-27T20:17:53+00:00","author":"Oracle Team","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Oracle Team","Est. reading time":"8 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/18c-dbms_xplan-note-about-failed-sql-plan-baseline\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/18c-dbms_xplan-note-about-failed-sql-plan-baseline\/"},"author":{"name":"Oracle Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee"},"headline":"18c dbms_xplan note about failed SQL Plan Baseline","datePublished":"2018-02-27T20:17:53+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/18c-dbms_xplan-note-about-failed-sql-plan-baseline\/"},"wordCount":382,"commentCount":0,"keywords":["Oracle 18c","SPM"],"articleSection":["Oracle"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/18c-dbms_xplan-note-about-failed-sql-plan-baseline\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/18c-dbms_xplan-note-about-failed-sql-plan-baseline\/","url":"https:\/\/www.dbi-services.com\/blog\/18c-dbms_xplan-note-about-failed-sql-plan-baseline\/","name":"18c dbms_xplan note about failed SQL Plan Baseline - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2018-02-27T20:17:53+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/18c-dbms_xplan-note-about-failed-sql-plan-baseline\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/18c-dbms_xplan-note-about-failed-sql-plan-baseline\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/18c-dbms_xplan-note-about-failed-sql-plan-baseline\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"18c dbms_xplan note about failed SQL Plan Baseline"}]},{"@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\/10999","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=10999"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/10999\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=10999"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=10999"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=10999"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=10999"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}