{"id":18185,"date":"2022-07-29T13:59:03","date_gmt":"2022-07-29T11:59:03","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=18185"},"modified":"2022-07-29T16:01:01","modified_gmt":"2022-07-29T14:01:01","slug":"why-do-we-still-have-height-balanced-histograms-and-how-to-get-rid-of-them","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/why-do-we-still-have-height-balanced-histograms-and-how-to-get-rid-of-them\/","title":{"rendered":"Why do we still have HEIGHT BALANCED Histograms and how to get rid of them?"},"content":{"rendered":"\n<p>A customer, who is on 19c with his Oracle databases asked me recently why he still has Height Balanced Histograms in his database? E.g.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>SQL&gt; select histogram, count(*) from dba_tab_columns where histogram &lt;&gt; 'NONE' group by histogram order by 2;\n\nHISTOGRAM         COUNT(*)\n--------------- ----------\nTOP-FREQUENCY            4\nHEIGHT BALANCED          5\nHYBRID                  39\nFREQUENCY              492\n\nSQL&gt; <\/code><\/pre>\n\n\n\n<p>In 12.1. Oracle introduced Top Frequency and Hybrid Histograms, which should replace Height Balanced histograms. There are 2 main reasons why Height Balanced histograms may still be there:<\/p>\n\n\n\n<p><strong>1. Top Frequency and\/or Hybrid histograms are disabled<\/strong><\/p>\n\n\n\n<p>By setting the preference ENABLE_HYBRID_HISTOGRAMS and ENABLE_TOP_FREQ_HISTOGRAMS to 0 (globally or on table level) you can disable the new histogram types. The default value is 3 and enables the 2 new histogram types:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>SQL&gt; select dbms_stats.get_prefs('ENABLE_HYBRID_HISTOGRAMS') hist_enabled from dual;\n\nHIST_ENABLED\n------------\n3\n\nSQL&gt; select dbms_stats.get_prefs('ENABLE_TOP_FREQ_HISTOGRAMS') hist_enabled from dual;\n\nHIST_ENABLED\n------------\n3\n\nSQL&gt; <\/code><\/pre>\n\n\n\n<p><strong>2. When gathering statistics and using a non-default value for ESTIMATE_PERCENT (default is DBMS_STATS.AUTO_SAMPLE_SIZE) then Height Balanced histograms will be used instead of the new histogram types.<\/strong><\/p>\n\n\n\n<p>The question is on how to find out what caused HEIGHT BALANCED histograms to be created?<\/p>\n\n\n\n<p>First let&#8217;s check what table-columns have Height Balanced histograms and when they&#8217;ve been created:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>SQL&gt; select table_name, column_name, last_analyzed from dba_tab_columns where histogram='HEIGHT BALANCED';\n\nTABLE_NAME                       COLUMN_NAME                      LAST_ANALYZED\n-------------------------------- -------------------------------- -------------------\nT1                               TIMESTAMP                        27.07.2022 13:11:31\nT1                               LAST_DDL_TIME                    27.07.2022 13:11:31\nT1                               CREATED                          27.07.2022 13:11:31\nT1                               OBJECT_ID                        27.07.2022 13:11:31\nT1                               OBJECT_NAME                      27.07.2022 13:11:31\n\nSQL&gt; <\/code><\/pre>\n\n\n\n<p>Ok, I do only have a test table T1 (copy of ALL_OBJECTS) where 5 columns have a HEIGHT BALANCED histogram. What caused them to be created?<\/p>\n\n\n\n<p>Are the new histogram types disabled?<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>SQL&gt; select dbms_stats.get_prefs('ENABLE_HYBRID_HISTOGRAMS') hist_enabled from dual;\n\nHIST_ENABLED\n------------\n3\n\nSQL&gt; select dbms_stats.get_prefs('ENABLE_TOP_FREQ_HISTOGRAMS') hist_enabled from dual;\n\nHIST_ENABLED\n------------\n3\n\nSQL&gt; <\/code><\/pre>\n\n\n\n<p>REMARK: Alternatively you may also run this query to get the global preferences:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>SQL&gt; select sname, nvl(to_char(sval1),spare4) value\n  2  from sys.optstat_hist_control$\n  3  where sname like '%HISTOGRAMS';\n\nSNAME                          VALUE\n------------------------------ --------------------------------\nENABLE_TOP_FREQ_HISTOGRAMS     3\nENABLE_HYBRID_HISTOGRAMS       3\n\nSQL&gt; <\/code><\/pre>\n\n\n\n<p>So globally the new histogram types are enabled and I could also check if something specific has been set on table-level:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>SQL&gt; select dbms_stats.get_prefs('ENABLE_HYBRID_HISTOGRAMS',ownname=&gt;'CBLEILE',tabname=&gt;'T1') hist_enabled from dual;\n\nHIST_ENABLED\n------------\n3\n\nSQL&gt; select dbms_stats.get_prefs('ENABLE_TOP_FREQ_HISTOGRAMS',ownname=&gt;'CBLEILE',tabname=&gt;'T1') hist_enabled from dual;\n\nHIST_ENABLED\n------------\n3\n\nSQL&gt; <\/code><\/pre>\n\n\n\n<p>I.e. the new histogram types are enabled. So that&#8217;s not the reason I still have height balanced histograms. To find out how statistics were gathered on table T1 the NOTES column on DBA_OPTSTAT_OPERATIONS is very useful. I split this into 2 SQL-statements to improve the readability:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>SQL&gt; select target, end_time, operation\n  2  from dba_optstat_operations\n  3  where end_time between to_date('27-JUL-2022 13:11:00','dd-mon-yyyy hh24:mi:ss')\n  4  and to_date('27-JUL-2022 13:12:00','dd-mon-yyyy hh24:mi:ss');\n\nTARGET          END_TIME                            OPERATION\n--------------- ----------------------------------- ------------------------\n\"CBLEILE\".\"T1\"  27-JUL-22 01.11.31.849682 PM +01:00 gather_table_stats\n\nSQL&gt; select notes\n  2  from dba_optstat_operations\n  3  where end_time between to_date('27-JUL-2022 13:11:00','dd-mon-yyyy hh24:mi:ss')\n  4  and to_date('27-JUL-2022 13:12:00','dd-mon-yyyy hh24:mi:ss');\n\nNOTES\n--------------------------------------------------\n&lt;params&gt;&lt;param name=\"block_sample\" val=\"FALSE\"\/&gt;&lt;p\naram name=\"cascade\" val=\"NULL\"\/&gt;&lt;param name=\"concu\nrrent\" val=\"FALSE\"\/&gt;&lt;param name=\"degree\" val=\"NULL\n\"\/&gt;&lt;<strong>param name=\"estimate_percent\" val=\"50\"<\/strong>\/&gt;&lt;param\n name=\"force\" val=\"FALSE\"\/&gt;&lt;param name=\"granularit\ny\" val=\"AUTO\"\/&gt;&lt;param name=\"method_opt\" val=\"FOR A\nLL COLUMNS SIZE 254\"\/&gt;&lt;param name=\"no_invalidate\"\nval=\"NULL\"\/&gt;&lt;param name=\"ownname\" val=\"CBLEILE\"\/&gt;&lt;\nparam name=\"partname\" val=\"\"\/&gt;&lt;param name=\"reporti\nng_mode\" val=\"FALSE\"\/&gt;&lt;param name=\"statid\" val=\"\"\/\n&gt;&lt;param name=\"statown\" val=\"\"\/&gt;&lt;param name=\"statta\nb\" val=\"\"\/&gt;&lt;param name=\"stattype\" val=\"DATA\"\/&gt;&lt;par\nam name=\"tabname\" val=\"T1\"\/&gt;&lt;\/params&gt;<\/code><\/pre>\n\n\n\n<p>So statistics were gathered with dbms_stats.gather_table_stats and ESTIMATE_PERCENT =&gt; 50 was used (see the NOTES column). Hence HEIGHT BALANCED histograms were created.<\/p>\n\n\n\n<p>To fix this there are 2 possibilities:<\/p>\n\n\n\n<ol class=\"wp-block-list\"><li>Tell the developer or DBA who gathers statistics to use the default for ESTIMATE_PERCENT so that he can fix the code accordingly.<\/li><li>Ignore non-default settings when gathering statistics. I.e. there is a preference PREFERENCE_OVERRIDES_PARAMETER which actually ignores parameters provided in dbms_stats and uses the preference on the table instead. E.g.<\/li><\/ol>\n\n\n\n<pre class=\"wp-block-code\"><code>SQL&gt; select dbms_stats.get_prefs('ESTIMATE_PERCENT','CBLEILE','T1') from dual;\n\nDBMS_STATS.GET_PREFS('ESTIMATE_PERCENT','CBLEILE','T1')\n------------------------------------------------------------------------------\nDBMS_STATS.AUTO_SAMPLE_SIZE\n\nSQL&gt; exec dbms_stats.set_table_prefs('CBLEILE','T1','PREFERENCE_OVERRIDES_PARAMETER','TRUE');\nSQL&gt; exec dbms_stats.gather_table_stats('CBLEILE','T1',ESTIMATE_PERCENT=&gt;50,options=&gt;'GATHER',method_opt=&gt;'FOR ALL COLUMNS SIZE 254');\nSQL&gt; select column_name, histogram from user_tab_columns\n  2  where table_name='T1' and histogram &lt;&gt; 'NONE';\n\nCOLUMN_NAME                      HISTOGRAM\n-------------------------------- ---------------\nOBJECT_TYPE                      FREQUENCY\n\nSQL&gt;\n<\/code><\/pre>\n\n\n\n<p>Why do I only have a frequency based histogram and no other histograms anymore?<\/p>\n\n\n\n<p>The reason is that the setting<br>method_opt=&gt;&#8217;FOR ALL COLUMNS SIZE 254&#8242;<br>has also been overwritten by the preference on the table:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>SQL&gt; select dbms_stats.get_prefs('METHOD_OPT','CBLEILE','T1') t1_prefs from dual;\n\nT1_PREFS\n----------------------------\nFOR ALL COLUMNS SIZE AUTO\n<\/code><\/pre>\n\n\n\n<p>I.e. to use &#8216;FOR ALL COLUMNS SIZE 254&#8217; I have to set the preference as well (here for test purposes):<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>SQL&gt; exec dbms_stats.set_table_prefs('CBLEILE','T1','METHOD_OPT','FOR ALL COLUMNS SIZE 254');\n\nSQL&gt; exec dbms_stats.gather_table_stats('CBLEILE','T1',ESTIMATE_PERCENT=&gt;50,options=&gt;'GATHER',method_opt=&gt;'FOR ALL COLUMNS SIZE 1');\n<\/code><\/pre>\n\n\n\n<p>REMARK: I used method_opt=&gt;&#8217;FOR ALL COLUMNS SIZE 1&#8242; on purpose which means &#8220;disable histograms&#8221;.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>SQL&gt; select column_name, histogram from user_tab_columns\n  2  where table_name='T1' and histogram &lt;&gt; 'NONE';\n\nCOLUMN_NAME                      HISTOGRAM\n-------------------------------- ---------------\nOWNER                            FREQUENCY\nOBJECT_NAME                      HYBRID\nSUBOBJECT_NAME                   HYBRID\nOBJECT_ID                        HYBRID\nDATA_OBJECT_ID                   HYBRID\nOBJECT_TYPE                      FREQUENCY\nCREATED                          HYBRID\nLAST_DDL_TIME                    HYBRID\nTIMESTAMP                        HYBRID\nSTATUS                           FREQUENCY\nTEMPORARY                        FREQUENCY\nGENERATED                        FREQUENCY\nSECONDARY                        FREQUENCY\nNAMESPACE                        FREQUENCY\nSHARING                          FREQUENCY\nEDITIONABLE                      FREQUENCY\nORACLE_MAINTAINED                FREQUENCY\nAPPLICATION                      FREQUENCY\nDEFAULT_COLLATION                FREQUENCY\nDUPLICATED                       FREQUENCY\nSHARDED                          FREQUENCY\n\n21 rows selected.\n\nSQL&gt; <\/code><\/pre>\n\n\n\n<p>I.e. with the preference PREFERENCE_OVERRIDES_PARAMETER = TRUE I can &#8220;force&#8221; to use all preferences set on the table (or the global preferences if the table preferences have not been set). So I overwrote my manual settings ESTIMATE_PERCENT=&gt;50 and method_opt=&gt;&#8217;FOR ALL COLUMNS SIZE 1&#8242; here.<\/p>\n\n\n\n<p>REMARK: Check if statistics have been gathered, because options=&gt;&#8217;GATHER&#8217; may also have been overwritten with the preference on the table.<\/p>\n\n\n\n<p>Be careful with PREFERENCE_OVERRIDES_PARAMETER = TRUE because it may have unwanted side-effects (as seen above) or statistics gathering in the application may take longer than before.<\/p>\n\n\n\n<p><strong>Summary: <\/strong>If you still see HEIGHT BALANCED histograms in your database then you probably use ESTIMATE_PERCENT &lt;&gt; Default when gathering statistics. It&#8217;s recommended to fix that and gather statistics with ESTIMATE_PERCENT =&gt; DBMS_STATS.AUTO_SAMPLE_SIZE. There have been lots of improvements since 11g to speed up stats gathering (like e.g. the use of approx_for_count_distinct = TRUE). Hence settings like ESTIMATE_PERCENT =&gt; 1 to speed up stats gathering on huge tables are usually not necessary anymore today.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A customer, who is on 19c with his Oracle databases asked me recently why he still has Height Balanced Histograms in his database? E.g. In 12.1. Oracle introduced Top Frequency and Hybrid Histograms, which should replace Height Balanced histograms. There are 2 main reasons why Height Balanced histograms may still be there: 1. Top Frequency [&hellip;]<\/p>\n","protected":false},"author":35,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[59],"tags":[2630,2635,397,2636,2637],"type_dbi":[],"class_list":["post-18185","post","type-post","status-publish","format-standard","hentry","category-oracle","tag-19c-2","tag-height-balanced","tag-histogram","tag-hybrid","tag-top-frequency"],"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>Why do we still have HEIGHT BALANCED Histograms and how to get rid of them? - 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\/why-do-we-still-have-height-balanced-histograms-and-how-to-get-rid-of-them\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Why do we still have HEIGHT BALANCED Histograms and how to get rid of them?\" \/>\n<meta property=\"og:description\" content=\"A customer, who is on 19c with his Oracle databases asked me recently why he still has Height Balanced Histograms in his database? E.g. In 12.1. Oracle introduced Top Frequency and Hybrid Histograms, which should replace Height Balanced histograms. There are 2 main reasons why Height Balanced histograms may still be there: 1. Top Frequency [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/why-do-we-still-have-height-balanced-histograms-and-how-to-get-rid-of-them\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2022-07-29T11:59:03+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2022-07-29T14:01:01+00:00\" \/>\n<meta name=\"author\" content=\"Clemens Bleile\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@ifgtxD2SrQ8r!YuXj\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Clemens Bleile\" \/>\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\/why-do-we-still-have-height-balanced-histograms-and-how-to-get-rid-of-them\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/why-do-we-still-have-height-balanced-histograms-and-how-to-get-rid-of-them\/\"},\"author\":{\"name\":\"Clemens Bleile\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0ac04011f60f2e93c115358d0789c2da\"},\"headline\":\"Why do we still have HEIGHT BALANCED Histograms and how to get rid of them?\",\"datePublished\":\"2022-07-29T11:59:03+00:00\",\"dateModified\":\"2022-07-29T14:01:01+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/why-do-we-still-have-height-balanced-histograms-and-how-to-get-rid-of-them\/\"},\"wordCount\":631,\"commentCount\":0,\"keywords\":[\"19c\",\"height balanced\",\"Histogram\",\"hybrid\",\"top-frequency\"],\"articleSection\":[\"Oracle\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/why-do-we-still-have-height-balanced-histograms-and-how-to-get-rid-of-them\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/why-do-we-still-have-height-balanced-histograms-and-how-to-get-rid-of-them\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/why-do-we-still-have-height-balanced-histograms-and-how-to-get-rid-of-them\/\",\"name\":\"Why do we still have HEIGHT BALANCED Histograms and how to get rid of them? - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2022-07-29T11:59:03+00:00\",\"dateModified\":\"2022-07-29T14:01:01+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0ac04011f60f2e93c115358d0789c2da\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/why-do-we-still-have-height-balanced-histograms-and-how-to-get-rid-of-them\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/why-do-we-still-have-height-balanced-histograms-and-how-to-get-rid-of-them\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/why-do-we-still-have-height-balanced-histograms-and-how-to-get-rid-of-them\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Why do we still have HEIGHT BALANCED Histograms and how to get rid of them?\"}]},{\"@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\/0ac04011f60f2e93c115358d0789c2da\",\"name\":\"Clemens Bleile\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/1f596609fc67cb28ed714e7bccc81ed4cd73b8582a8148a490c77daeb2fde21a?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/1f596609fc67cb28ed714e7bccc81ed4cd73b8582a8148a490c77daeb2fde21a?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/1f596609fc67cb28ed714e7bccc81ed4cd73b8582a8148a490c77daeb2fde21a?s=96&d=mm&r=g\",\"caption\":\"Clemens Bleile\"},\"description\":\"Clemens Bleile has more than 30 years of IT experience, thirteen in Oracle Support and fifteen in Oracle Consulting. He is specialized in Oracle Database Performance Tuning (SQL Tuning, DB Tuning) and developing an Oracle DB IT architecture (highly available, low-maintenance, cost efficient storage of data). He is an expert in problem analysis and resolution. Prior to joining dbi services, Clemens Bleile was Manager of the EMEA Database Performance team at the Oracle Global Customer Support Services. Clemens Bleile is Oracle Certified Professional 11g, 12c and Oracle Certified Expert for Performance Management and Tuning and holds a Master Degree, Business Information Systems from the Fachhochschule Furtwangen, Germany.\",\"sameAs\":[\"https:\/\/www.dbi-services.com\",\"https:\/\/x.com\/ifgtxD2SrQ8r!YuXj\"],\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/clemens-bleile\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Why do we still have HEIGHT BALANCED Histograms and how to get rid of them? - 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\/why-do-we-still-have-height-balanced-histograms-and-how-to-get-rid-of-them\/","og_locale":"en_US","og_type":"article","og_title":"Why do we still have HEIGHT BALANCED Histograms and how to get rid of them?","og_description":"A customer, who is on 19c with his Oracle databases asked me recently why he still has Height Balanced Histograms in his database? E.g. In 12.1. Oracle introduced Top Frequency and Hybrid Histograms, which should replace Height Balanced histograms. There are 2 main reasons why Height Balanced histograms may still be there: 1. Top Frequency [&hellip;]","og_url":"https:\/\/www.dbi-services.com\/blog\/why-do-we-still-have-height-balanced-histograms-and-how-to-get-rid-of-them\/","og_site_name":"dbi Blog","article_published_time":"2022-07-29T11:59:03+00:00","article_modified_time":"2022-07-29T14:01:01+00:00","author":"Clemens Bleile","twitter_card":"summary_large_image","twitter_creator":"@ifgtxD2SrQ8r!YuXj","twitter_misc":{"Written by":"Clemens Bleile","Est. reading time":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/why-do-we-still-have-height-balanced-histograms-and-how-to-get-rid-of-them\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/why-do-we-still-have-height-balanced-histograms-and-how-to-get-rid-of-them\/"},"author":{"name":"Clemens Bleile","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0ac04011f60f2e93c115358d0789c2da"},"headline":"Why do we still have HEIGHT BALANCED Histograms and how to get rid of them?","datePublished":"2022-07-29T11:59:03+00:00","dateModified":"2022-07-29T14:01:01+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/why-do-we-still-have-height-balanced-histograms-and-how-to-get-rid-of-them\/"},"wordCount":631,"commentCount":0,"keywords":["19c","height balanced","Histogram","hybrid","top-frequency"],"articleSection":["Oracle"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/why-do-we-still-have-height-balanced-histograms-and-how-to-get-rid-of-them\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/why-do-we-still-have-height-balanced-histograms-and-how-to-get-rid-of-them\/","url":"https:\/\/www.dbi-services.com\/blog\/why-do-we-still-have-height-balanced-histograms-and-how-to-get-rid-of-them\/","name":"Why do we still have HEIGHT BALANCED Histograms and how to get rid of them? - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2022-07-29T11:59:03+00:00","dateModified":"2022-07-29T14:01:01+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0ac04011f60f2e93c115358d0789c2da"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/why-do-we-still-have-height-balanced-histograms-and-how-to-get-rid-of-them\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/why-do-we-still-have-height-balanced-histograms-and-how-to-get-rid-of-them\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/why-do-we-still-have-height-balanced-histograms-and-how-to-get-rid-of-them\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Why do we still have HEIGHT BALANCED Histograms and how to get rid of them?"}]},{"@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\/0ac04011f60f2e93c115358d0789c2da","name":"Clemens Bleile","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/1f596609fc67cb28ed714e7bccc81ed4cd73b8582a8148a490c77daeb2fde21a?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/1f596609fc67cb28ed714e7bccc81ed4cd73b8582a8148a490c77daeb2fde21a?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/1f596609fc67cb28ed714e7bccc81ed4cd73b8582a8148a490c77daeb2fde21a?s=96&d=mm&r=g","caption":"Clemens Bleile"},"description":"Clemens Bleile has more than 30 years of IT experience, thirteen in Oracle Support and fifteen in Oracle Consulting. He is specialized in Oracle Database Performance Tuning (SQL Tuning, DB Tuning) and developing an Oracle DB IT architecture (highly available, low-maintenance, cost efficient storage of data). He is an expert in problem analysis and resolution. Prior to joining dbi services, Clemens Bleile was Manager of the EMEA Database Performance team at the Oracle Global Customer Support Services. Clemens Bleile is Oracle Certified Professional 11g, 12c and Oracle Certified Expert for Performance Management and Tuning and holds a Master Degree, Business Information Systems from the Fachhochschule Furtwangen, Germany.","sameAs":["https:\/\/www.dbi-services.com","https:\/\/x.com\/ifgtxD2SrQ8r!YuXj"],"url":"https:\/\/www.dbi-services.com\/blog\/author\/clemens-bleile\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/18185","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\/35"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=18185"}],"version-history":[{"count":8,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/18185\/revisions"}],"predecessor-version":[{"id":18193,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/18185\/revisions\/18193"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=18185"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=18185"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=18185"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=18185"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}