When I don’t need I feature, I don’t turn it on, or do not use it because it reduces the possibility to run into issues. Most of the times this is true, however, during the preparation for an RMAN workshop, the RMAN list failure command showed me the following dictionary issue.<\/p>\n
RMAN> list failure;\n\nusing target database control file instead of recovery catalog\nDatabase Role: PRIMARY\n\nList of Database Failures\n=========================\n\nFailure ID Priority Status Time Detected Summary\n---------- -------- --------- -------------------- -------\n2 CRITICAL OPEN 13-FEB-2017 10:12:26 SQL dictionary health check: seg$.type# 31 on object SEG$ failed<\/pre>\nI thought first, that it might be related to some incorrect errors shown by the health check (DBMS_HM), because there used to be some issues with that tool. But even after applying the following patch, nothing changed and the error still appears.<\/p>\n
19543595: INCORRECT HEALTHCHECK ERRORS FROM DBMS_HM – FALSE ERRORS ON TS$ , FILE$ OR USER<\/p>\n
So I started a manual health check again to get some more details.<\/p>\n
SQL> BEGIN\n 2 DBMS_HM.RUN_CHECK (check_name => 'Dictionary Integrity Check',\n 3 run_name => 'WilliamsDICTrun002',\n 4 input_params => 'CHECK_MASK=ALL');\n 5 END;\n 6 \/\n\nPL\/SQL procedure successfully completed.\n\nSQL> SELECT DBMS_HM.GET_RUN_REPORT('WilliamsDICTrun002') from dual;\n\nDBMS_HM.GET_RUN_REPORT('WILLIAMSDICTRUN002')\n---------------------------------------------------------------------\nBasic Run Information\n Run Name : WilliamsDICTrun002\n Run Id : 61\n Check Name : Dictionary Integrity Check\n Mode : MANUAL\n Status : COMPLETED\n Start Time : 2017-02-13 10:56:58.250100 +01:00\n End Time : 2017-02-13 10:56:58.689301 +01:00\n Error Encountered : 0\n Source Incident Id : 0\n Number of Incidents Created : 0\n\nInput Paramters for the Run\n TABLE_NAME=ALL_CORE_TABLES\n CHECK_MASK=ALL\n\nRun Findings And Recommendations\n Finding\n Finding Name : Dictionary Inconsistency\n Finding ID : 62\n Type : FAILURE\n Status : OPEN\n Priority : CRITICAL\n Message : SQL dictionary health check: seg$.type# 31 on object SEG$\n failed\n Message : Damaged rowid is AAAAAIAABAAAK+RAAc - description: Ts# 1\n File# 2 Block# 28032 is referenced<\/pre>\nNow I do have the ROWID, the file number and the block number of the affecting object. Let’s see what it is.<\/p>\n
SQL> select FILE#, BLOCK#, TYPE#, TS#, BLOCKS from seg$ where rowid='AAAAAIAABAAAK+RAAc';\n\n FILE# BLOCK# TYPE# TS# BLOCKS\n---------- ---------- ---------- ---------- ----------\n 2 28032 11 1 1024\n\t\t \n\nSQL> SELECT segment_name, segment_type, block_id, blocks\n 2 FROM dba_extents\n 3 WHERE\n 4 file_id = 2\n 5 AND\n 6 ( 28032 BETWEEN block_id AND ( block_id + blocks ) );\n\nSEGMENT_NAME SEGMENT_TYPE BLOCK_ID BLOCKS\n-------------------------- ------------------------ ---------- ----------\nHEATMAP SYSTEM STATISTICS 28032 1024<\/pre>\nReally strange. It is related to the HEATMAP segment, but I am not using the heat map feature, or used it in the past.<\/p>\n
SQL> show parameter heat\n\nNAME TYPE VALUE\n------------------------------------ ----------- ------------------------------\nheat_map string OFF\n\nSQL> select name, DETECTED_USAGES from DBA_FEATURE_USAGE_STATISTICS where name like 'Heat%';\n\nNAME DETECTED_USAGES\n------------------------ ---------------\nHeat Map 0<\/pre>\nBut how can I get this fixed now? You could either ignore this issue, create a SR at Oracle, or you can drop the statistics segment, in case you are not using the heatmap feature.<\/p>\n
In my case, I decided to the drop the statistics segment by issuing the following command. Dropping the statistics segment works by setting the underscore parameter “_drop_stat_segment” to 1.<\/p>\n
SQL> select SEGMENT_NAME, SEGMENT_TYPE from dba_extents where SEGMENT_TYPE = 'SYSTEM STATISTICS';\n\nSEGMENT_NAME SEGMENT_TYPE\n-------------------------- ------------------------\nHEATMAP SYSTEM STATISTICS\n\nSQL> ALTER SYSTEM SET \"_drop_stat_segment\"=1 scope=memory;\n\nSystem altered.\n\nSQL> select SEGMENT_NAME, SEGMENT_TYPE from dba_extents where SEGMENT_TYPE = 'SYSTEM STATISTICS';\n\nno rows selected<\/pre>\nThe heat map table is gone now. Let’s run the dictionary check again.<\/p>\n
SQL> BEGIN\n 2 DBMS_HM.RUN_CHECK (check_name => 'Dictionary Integrity Check',\n 3 run_name => 'WilliamsDICTrun003',\n 4 input_params => 'CHECK_MASK=ALL');\n 5 END;\n 6 \/\n\nPL\/SQL procedure successfully completed.\n\nSQL> SELECT DBMS_HM.GET_RUN_REPORT('WilliamsDICTrun003') from dual;\n\nDBMS_HM.GET_RUN_REPORT('WILLIAMSDICTRUN003')\n---------------------------------------------------------------------\nBasic Run Information\n Run Name : WilliamsDICTrun003\n Run Id : 81\n Check Name : Dictionary Integrity Check\n Mode : MANUAL\n Status : COMPLETED\n Start Time : 2017-02-13 11:17:15.190873 +01:00\n End Time : 2017-02-13 11:17:15.642501 +01:00\n Error Encountered : 0\n Source Incident Id : 0\n Number of Incidents Created : 0\n\nInput Paramters for the Run\n TABLE_NAME=ALL_CORE_TABLES\n CHECK_MASK=ALL\n\nRun Findings And Recommendations\n\n\nRMAN> list failure;\n\nusing target database control file instead of recovery catalog\nDatabase Role: PRIMARY\n\nno failures found that match specification<\/pre>\n<\/p>\n
Looks much better now.<\/p>\n
Conclusion<\/h3>\n
Even if you are not using some features, you can still have trouble with them. \ud83d\ude42<\/p>\n","protected":false},"excerpt":{"rendered":"
By William Sescu When I don’t need I feature, I don’t turn it on, or do not use it because it reduces the possibility to run into issues. Most of the times this is true, however, during the preparation for an RMAN workshop, the RMAN list failure command showed me the following dictionary issue. RMAN> […]<\/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":[229,198],"tags":[209,270],"type_dbi":[],"class_list":["post-9773","post","type-post","status-publish","format-standard","hentry","category-database-administration-monitoring","category-database-management","tag-oracle-12c","tag-rman"],"acf":[],"yoast_head":"\n
Oracle 12c - Issues with the HEATMAP Segment even if the heat map feature is not used - 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-12c-issues-with-the-heatmap-segment-even-if-the-heat-map-feature-is-not-used\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Oracle 12c - Issues with the HEATMAP Segment even if the heat map feature is not used\" \/>\n<meta property=\"og:description\" content=\"By William Sescu When I don’t need I feature, I don’t turn it on, or do not use it because it reduces the possibility to run into issues. Most of the times this is true, however, during the preparation for an RMAN workshop, the RMAN list failure command showed me the following dictionary issue. RMAN> […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/oracle-12c-issues-with-the-heatmap-segment-even-if-the-heat-map-feature-is-not-used\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2017-02-13T09:55:50+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=\"4 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-12c-issues-with-the-heatmap-segment-even-if-the-heat-map-feature-is-not-used\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/oracle-12c-issues-with-the-heatmap-segment-even-if-the-heat-map-feature-is-not-used\/\"},\"author\":{\"name\":\"Oracle Team\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee\"},\"headline\":\"Oracle 12c – Issues with the HEATMAP Segment even if the heat map feature is not used\",\"datePublished\":\"2017-02-13T09:55:50+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/oracle-12c-issues-with-the-heatmap-segment-even-if-the-heat-map-feature-is-not-used\/\"},\"wordCount\":291,\"commentCount\":0,\"keywords\":[\"Oracle 12c\",\"RMAN\"],\"articleSection\":[\"Database Administration & Monitoring\",\"Database management\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/oracle-12c-issues-with-the-heatmap-segment-even-if-the-heat-map-feature-is-not-used\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/oracle-12c-issues-with-the-heatmap-segment-even-if-the-heat-map-feature-is-not-used\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/oracle-12c-issues-with-the-heatmap-segment-even-if-the-heat-map-feature-is-not-used\/\",\"name\":\"Oracle 12c - Issues with the HEATMAP Segment even if the heat map feature is not used - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2017-02-13T09:55:50+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/oracle-12c-issues-with-the-heatmap-segment-even-if-the-heat-map-feature-is-not-used\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/oracle-12c-issues-with-the-heatmap-segment-even-if-the-heat-map-feature-is-not-used\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/oracle-12c-issues-with-the-heatmap-segment-even-if-the-heat-map-feature-is-not-used\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Oracle 12c – Issues with the HEATMAP Segment even if the heat map feature is not used\"}]},{\"@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 12c - Issues with the HEATMAP Segment even if the heat map feature is not used - 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-12c-issues-with-the-heatmap-segment-even-if-the-heat-map-feature-is-not-used\/","og_locale":"en_US","og_type":"article","og_title":"Oracle 12c - Issues with the HEATMAP Segment even if the heat map feature is not used","og_description":"By William Sescu When I don’t need I feature, I don’t turn it on, or do not use it because it reduces the possibility to run into issues. Most of the times this is true, however, during the preparation for an RMAN workshop, the RMAN list failure command showed me the following dictionary issue. RMAN> […]","og_url":"https:\/\/www.dbi-services.com\/blog\/oracle-12c-issues-with-the-heatmap-segment-even-if-the-heat-map-feature-is-not-used\/","og_site_name":"dbi Blog","article_published_time":"2017-02-13T09:55:50+00:00","author":"Oracle Team","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Oracle Team","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/oracle-12c-issues-with-the-heatmap-segment-even-if-the-heat-map-feature-is-not-used\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/oracle-12c-issues-with-the-heatmap-segment-even-if-the-heat-map-feature-is-not-used\/"},"author":{"name":"Oracle Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee"},"headline":"Oracle 12c – Issues with the HEATMAP Segment even if the heat map feature is not used","datePublished":"2017-02-13T09:55:50+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/oracle-12c-issues-with-the-heatmap-segment-even-if-the-heat-map-feature-is-not-used\/"},"wordCount":291,"commentCount":0,"keywords":["Oracle 12c","RMAN"],"articleSection":["Database Administration & Monitoring","Database management"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/oracle-12c-issues-with-the-heatmap-segment-even-if-the-heat-map-feature-is-not-used\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/oracle-12c-issues-with-the-heatmap-segment-even-if-the-heat-map-feature-is-not-used\/","url":"https:\/\/www.dbi-services.com\/blog\/oracle-12c-issues-with-the-heatmap-segment-even-if-the-heat-map-feature-is-not-used\/","name":"Oracle 12c - Issues with the HEATMAP Segment even if the heat map feature is not used - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2017-02-13T09:55:50+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/oracle-12c-issues-with-the-heatmap-segment-even-if-the-heat-map-feature-is-not-used\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/oracle-12c-issues-with-the-heatmap-segment-even-if-the-heat-map-feature-is-not-used\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/oracle-12c-issues-with-the-heatmap-segment-even-if-the-heat-map-feature-is-not-used\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Oracle 12c – Issues with the HEATMAP Segment even if the heat map feature is not used"}]},{"@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\/9773","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=9773"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/9773\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=9773"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=9773"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=9773"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=9773"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}