{"id":2308,"date":"2011-09-01T12:18:00","date_gmt":"2011-09-01T10:18:00","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/compression-advisor-excessive-redo-log-file-generation\/"},"modified":"2011-09-01T12:18:00","modified_gmt":"2011-09-01T10:18:00","slug":"compression-advisor-excessive-redo-log-file-generation","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/compression-advisor-excessive-redo-log-file-generation\/","title":{"rendered":"Compression advisor: excessive redo log file generation"},"content":{"rendered":"<p>Last week at a customer site, we experienced an excessive redo log generation rapidly filling up the FRA (Flash\/Fast Recovery Area) with archivelog files. This eventually caused the database to crash.<\/p>\n<p><!-- \t\t@page { margin: 0.79in } \t\tP { margin-bottom: 0.08in } \t--><\/p>\n<p>As usual, we started the problem analysis by scanning the alert.log file. The trouble began at 7 am when the DEFAULT_MAINTENANCE_PLAN started.<br \/>\nIn less than 10 minutes more than 100 archivelog files of 50 Mb each were generated (cf. Below):<\/p>\n<pre class=\"brush: actionscript3; gutter: true; first-line: 1\"><code style=\"margin-bottom: 0in;\"><\/code>Setting Resource Manager plan SCHEDULER[0x3109]:DEFAULT_MAINTENANCE_PLAN via scheduler window \nThu Jun 30 07:00:38 2011 \nThread 1 advanced to log sequence 2648 (LGWR switch) \n\u2026....\n\u2026....\nThu Jun 30 07:09:44 2011 \nThread 1 advanced to log sequence 2749 (LGWR switch) Errors in file X:ORACLEdiagrdbmsmydb_site1mydbtracemydb_m000_2196.trc: \nORA-19815: WARNING: db_recovery_file_dest_size of 5368709120 bytes is 100.00% used, and has 0 remaining bytes available. <code style=\"margin-bottom: 0in;\"><\/code><\/pre>\n<p>As this output did not reveal that much, we started generating the AWR reports for the period when the database crashed (see AWR below).<br \/>\nHere are the top SQL consumers sorted by different criteria:<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"caption\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/SQL-OrderedByCPU-Time.png\" alt=\"\" width=\"658\" height=\"46\" \/><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/SQL-OrderedByElepsedTime.png\" alt=\"\" width=\"660\" height=\"77\" \/><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/SQL-OrderedByGets.png\" alt=\"\" width=\"661\" height=\"46\" \/><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/SqlOrderedByUse-IO-Wait-Time.png\" alt=\"\" width=\"660\" height=\"45\" \/><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/Sql-OrderedByReads.png\" alt=\"\" width=\"660\" height=\"41\" \/><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/SQL-OrderedByPhysicalRead.png\" alt=\"\" width=\"656\" height=\"42\" \/><\/p>\n<p>Based on these reports, we observed that the SQL Module consuming all the resources was always the DBMS_SCHEDULER which calls the stored procedure dbms_space.AUTO_SPACE_ADVISOR_JOB.<\/p>\n<h4>What does it mean?<\/h4>\n<p>During the default Oracle maintenance window, the DBMS.SCHEDULER package starts the AUTO_SPACE_ADVISOR_JOB job. This job&#8217;s purpose is to trigger the DBMS_SPACE.AUTO_SPACE_ADVISOR_JOB_PROC stored procedure. This last one itself triggers the Automatic Segment Advisor which uses the Compression Advisor in order to identify all the segments which should benefit from table compression (Oracle Compression Feature).<\/p>\n<p>Going deeper in our investigations about this Compression Advisor, we found out that this problem was due to bug 8896202 (Oracle Support) which should have been fixed in version 11.2.0.2 (cf. below). However, our customer was still hit by this issue.<\/p>\n<p><code>METALINK<br \/>\nHow Does Compression Advisor Work? [ID 1284972.1]<br \/>\nCompression advisor is a new advisor added in 11gR2.<br \/>\nIt is shipped with Segment Advisor, and will be executed whenever Segment Advisor task run.<br \/>\nWe can't disable it separately at this point of time, but an enhancement request has been submitted to separate it from Segment Advisor.<br \/>\nSegments that are at least 10MB in size and with at least 3 indexes will be evaluated for compressibility (but not all the tables which meet the requirements will be evaluated, an internal algorithm will decide which segment should be evaluated).<br \/>\nThe dbms_compression package will be invoked to estimate how much space can be saved. It will create two internal tables (DBMS_TABCOMP_TEMP_UNCMP, DBMS_TABCOMP_TEMP_CMP) in the tablespace which hosts the segment.<br \/>\nDBMS_TABCOMP_TEMP_UNCMP is created with 99% sample blocks by default.<br \/>\nDBMS_TABCOMP_TEMP_CMP is created with compress option based on DBMS_TABCOMP_TEMP_UNCMP.<br \/>\nCOMPRESSION_RATIO is generated by comparing DBMS_TABCOMP_TEMP_UNCMP and DBMS_TABCOMP_TEMP_CMP. These two tables will be dropped immediately after the estimation.<br \/>\nThe recommendations of compressing table can be obtained from EM DB console.<br \/>\nPlease note the following impacts:<br \/>\nWithout applying unpublished bug 8896202, excessive redo log will be generated. (This is fixed in 11.2.0.2) however this bug still occurred on our site.<br \/>\nBut be aware that bug 8896202 might not eliminate redo generation if object containing LOB data which is not having NOCACHE NOLOGGING option; check note\u00a0 976722.1 for details.<br \/>\nOra-20000 against tables DBMS_TABCOMP_TEMP_CMP and DBMS_TABCOMP_TEMP_UNCMP might be seen when performing dbms_stats<br \/>\nExtra disk space might be required to host DBMS_TABCOMP_TEMP_CMP and DBMS_TABCOMP_TEMP_UNCMP, it can result in space pressure in some cases.<\/code><\/p>\n<p>So we again had a look at the AWR report and noticed that the top SQL statement was the TEMPORARY table creation against a table containing LOB segments:<\/p>\n<p><span style=\"font-family: verdana,geneva; font-size: 12pt;\"><img loading=\"lazy\" decoding=\"async\" src=\"http:\/\/dbi-services.com\/blog\/wp-content\/uploads\/images\/stories\/blog\/sme\/compressionAdvisor\/sql-statement.png\" alt=\"sql-statement\" width=\"621\" height=\"19\" \/><br \/>\n<\/span><\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">SQL&gt; select owner,table_name,column_name,cache,logging from dba_lobs where owner='BS_ZG' and table_name='G91_DOK_DMS';\nOWNER\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 TABLE_NAME\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 COLUMN_NAME\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 CACHE\u00a0\u00a0\u00a0\u00a0\u00a0 LOGGING\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0\nBS_ZG\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 G91_DOK_DMS\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 G91_DOC_BLOB\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 NO\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 YES\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0\nBS_ZG\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 G91_DOK_DMS\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 G91_DOC_CLOB\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 NO\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 YES<\/pre>\n<p><samp>\u00a0<\/samp><\/p>\n<h4>Root cause and Workaround<\/h4>\n<p>&#8220;If a source table contains a LOB segment with &#8220;CACHE\/LOGGING&#8221; enabled then despite the database NOLOGGING clause setting, Oracle will still generate excessive redo logs as the NOLOGGING for LOBS can only be invoked when the LOB segment is in &#8216;NOCACHE and NOLOGGING&#8217;.&#8221;<\/p>\n<p>In our case we did not have cache enabled, however, our customer still was affected by the bug!<br \/>\nTherefore we implemented the following workaround:<\/p>\n<ul>\n<li>Disable the Automatic Segment Advisor.<\/li>\n<\/ul>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">SQL&gt;execute dbms_scheduler.disable('sys.auto_space_advisor_job');<\/pre>\n<p>or<\/p>\n<pre class=\"brush: actionscript3; gutter: true; first-line: 1\">BEGIN\ndbms_auto_task_admin.disable(\nclient_name =&gt; 'auto space advisor',\noperation =&gt; NULL,\nwindow_name =&gt; NULL);\nEND;\n\/<\/pre>\n<p>Of course we are now awaiting (as several customers) the patch set 11.2.0.3 in order to verify if the bug is fixed even if the &#8220;auto space advisor&#8221; is enabled.<br \/>\nHope this helped\u00a0\ud83d\ude00<\/p>\n","protected":false},"excerpt":{"rendered":"<p><span style=\"font-family: verdana,geneva; font-size: 12pt;\">Last week by a customer, we experienced an excessive redo log generation filling up rapidly the FRA (Flash\/Fast Recovery Area) with archivelog files which caused the database to crash.<\/span><\/p>\n","protected":false},"author":28,"featured_media":2309,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[197],"tags":[281,206,17,278,282,34,44],"type_dbi":[],"class_list":["post-2308","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-application-integration-middleware","tag-dbms_scheduler","tag-lob","tag-oracle-11g","tag-oracle-support","tag-redo-log","tag-segments","tag-troubleshooting"],"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>Compression advisor: excessive redo log file generation - dbi Blog<\/title>\n<meta name=\"description\" content=\"Last week at a customer site, we experienced an excessive redo log generation rapidly filling up the FRA (Flash\/Fast Recovery Area) with archivelog files. This eventually caused the database to crash.\" \/>\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\/compression-advisor-excessive-redo-log-file-generation\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Compression advisor: excessive redo log file generation\" \/>\n<meta property=\"og:description\" content=\"Last week at a customer site, we experienced an excessive redo log generation rapidly filling up the FRA (Flash\/Fast Recovery Area) with archivelog files. This eventually caused the database to crash.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/compression-advisor-excessive-redo-log-file-generation\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2011-09-01T10:18:00+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/SQL-OrderedByCPU-Time.png\" \/>\n\t<meta property=\"og:image:width\" content=\"872\" \/>\n\t<meta property=\"og:image:height\" content=\"61\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Open source 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=\"Open source 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\/compression-advisor-excessive-redo-log-file-generation\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/compression-advisor-excessive-redo-log-file-generation\/\"},\"author\":{\"name\":\"Open source Team\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/59554f0d99383431eb6ed427e338952b\"},\"headline\":\"Compression advisor: excessive redo log file generation\",\"datePublished\":\"2011-09-01T10:18:00+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/compression-advisor-excessive-redo-log-file-generation\/\"},\"wordCount\":388,\"commentCount\":0,\"image\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/compression-advisor-excessive-redo-log-file-generation\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/SQL-OrderedByCPU-Time.png\",\"keywords\":[\"dbms_scheduler\",\"LOB\",\"Oracle 11g\",\"Oracle support\",\"Redo log\",\"Segments\",\"Troubleshooting\"],\"articleSection\":[\"Application integration &amp; Middleware\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/compression-advisor-excessive-redo-log-file-generation\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/compression-advisor-excessive-redo-log-file-generation\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/compression-advisor-excessive-redo-log-file-generation\/\",\"name\":\"Compression advisor: excessive redo log file generation - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/compression-advisor-excessive-redo-log-file-generation\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/compression-advisor-excessive-redo-log-file-generation\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/SQL-OrderedByCPU-Time.png\",\"datePublished\":\"2011-09-01T10:18:00+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/59554f0d99383431eb6ed427e338952b\"},\"description\":\"Last week at a customer site, we experienced an excessive redo log generation rapidly filling up the FRA (Flash\/Fast Recovery Area) with archivelog files. This eventually caused the database to crash.\",\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/compression-advisor-excessive-redo-log-file-generation\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/compression-advisor-excessive-redo-log-file-generation\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/compression-advisor-excessive-redo-log-file-generation\/#primaryimage\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/SQL-OrderedByCPU-Time.png\",\"contentUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/SQL-OrderedByCPU-Time.png\",\"width\":872,\"height\":61},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/compression-advisor-excessive-redo-log-file-generation\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Compression advisor: excessive redo log file generation\"}]},{\"@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\/59554f0d99383431eb6ed427e338952b\",\"name\":\"Open source Team\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/eb4fb12e386e8c41fdef0733e8114594cf2653e4f55e9fa2161442b8eaf3f657?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/eb4fb12e386e8c41fdef0733e8114594cf2653e4f55e9fa2161442b8eaf3f657?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/eb4fb12e386e8c41fdef0733e8114594cf2653e4f55e9fa2161442b8eaf3f657?s=96&d=mm&r=g\",\"caption\":\"Open source Team\"},\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/open-source-team\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Compression advisor: excessive redo log file generation - dbi Blog","description":"Last week at a customer site, we experienced an excessive redo log generation rapidly filling up the FRA (Flash\/Fast Recovery Area) with archivelog files. This eventually caused the database to crash.","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\/compression-advisor-excessive-redo-log-file-generation\/","og_locale":"en_US","og_type":"article","og_title":"Compression advisor: excessive redo log file generation","og_description":"Last week at a customer site, we experienced an excessive redo log generation rapidly filling up the FRA (Flash\/Fast Recovery Area) with archivelog files. This eventually caused the database to crash.","og_url":"https:\/\/www.dbi-services.com\/blog\/compression-advisor-excessive-redo-log-file-generation\/","og_site_name":"dbi Blog","article_published_time":"2011-09-01T10:18:00+00:00","og_image":[{"width":872,"height":61,"url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/SQL-OrderedByCPU-Time.png","type":"image\/png"}],"author":"Open source Team","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Open source Team","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/compression-advisor-excessive-redo-log-file-generation\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/compression-advisor-excessive-redo-log-file-generation\/"},"author":{"name":"Open source Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/59554f0d99383431eb6ed427e338952b"},"headline":"Compression advisor: excessive redo log file generation","datePublished":"2011-09-01T10:18:00+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/compression-advisor-excessive-redo-log-file-generation\/"},"wordCount":388,"commentCount":0,"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/compression-advisor-excessive-redo-log-file-generation\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/SQL-OrderedByCPU-Time.png","keywords":["dbms_scheduler","LOB","Oracle 11g","Oracle support","Redo log","Segments","Troubleshooting"],"articleSection":["Application integration &amp; Middleware"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/compression-advisor-excessive-redo-log-file-generation\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/compression-advisor-excessive-redo-log-file-generation\/","url":"https:\/\/www.dbi-services.com\/blog\/compression-advisor-excessive-redo-log-file-generation\/","name":"Compression advisor: excessive redo log file generation - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/compression-advisor-excessive-redo-log-file-generation\/#primaryimage"},"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/compression-advisor-excessive-redo-log-file-generation\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/SQL-OrderedByCPU-Time.png","datePublished":"2011-09-01T10:18:00+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/59554f0d99383431eb6ed427e338952b"},"description":"Last week at a customer site, we experienced an excessive redo log generation rapidly filling up the FRA (Flash\/Fast Recovery Area) with archivelog files. This eventually caused the database to crash.","breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/compression-advisor-excessive-redo-log-file-generation\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/compression-advisor-excessive-redo-log-file-generation\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbi-services.com\/blog\/compression-advisor-excessive-redo-log-file-generation\/#primaryimage","url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/SQL-OrderedByCPU-Time.png","contentUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/SQL-OrderedByCPU-Time.png","width":872,"height":61},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/compression-advisor-excessive-redo-log-file-generation\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Compression advisor: excessive redo log file generation"}]},{"@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\/59554f0d99383431eb6ed427e338952b","name":"Open source Team","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/eb4fb12e386e8c41fdef0733e8114594cf2653e4f55e9fa2161442b8eaf3f657?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/eb4fb12e386e8c41fdef0733e8114594cf2653e4f55e9fa2161442b8eaf3f657?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/eb4fb12e386e8c41fdef0733e8114594cf2653e4f55e9fa2161442b8eaf3f657?s=96&d=mm&r=g","caption":"Open source Team"},"url":"https:\/\/www.dbi-services.com\/blog\/author\/open-source-team\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/2308","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\/28"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=2308"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/2308\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media\/2309"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=2308"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=2308"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=2308"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=2308"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}