Troubleshooting ORA-1555&nb…

<wbr><p style="mso-margin-top-alt:auto;mso-margin-bottom-alt: auto;text-align:left;mso-pagination:widow-orphan;mso-outline-level:3" align="left"><b><span style="font-size:13.5pt;font-family:宋体;mso-bidi-font-family:宋体; mso-font-kerning:0pt" lang="EN-US">Troubleshooting ORA-1555 (Doc ID 1307334.1)</span></b></p> <p style="mso-margin-top-alt:auto;mso-margin-bottom-alt: auto;text-align:left;mso-pagination:widow-orphan;mso-outline-level:4" align="left"><b><span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体; mso-font-kerning:0pt" lang="EN-US">By khrobins on</span></b> <span lang="EN-US"><a href="https://blogs.oracle.com/db/entry/troubleshooting_ora_1555"><b><span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体;color:blue; mso-font-kerning:0pt"> May 16, 2011</span></b></a></span></p> <p style="text-align:left;mso-pagination:widow-orphan" align="left"> <span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体; mso-font-kerning:0pt" lang="EN-US">This article is intended to assist in finding tips and techniques to assist with finding solutions to ORA-1555 errors. The document will cover the following topics:<br><br> Concepts/Definitions<br> Diagnosing<br> Common Causes/Solutions</span></p> <p style="mso-margin-top-alt:auto;mso-margin-bottom-alt: auto;text-align:left;mso-pagination:widow-orphan;mso-outline-level:3" align="left"><b><span style="font-size:13.5pt;font-family:宋体;mso-bidi-font-family:宋体; mso-font-kerning:0pt" lang="EN-US">Concepts/Definitions</span></b></p> <p style="text-align:left;mso-pagination:widow-orphan" align="left"> <span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体; mso-font-kerning:0pt" lang="EN-US">The ORA-1555 errors can happen when a query is unable to access enough undo to build<br> a copy of the data at the time the query started. Committed “versions” of blocks are<br> maintained along with newer uncommitted “versions” of those blocks so that queries can<br> access data as it existed in the database at the time of the query. These are referred to as<br> “consistent read” blocks and are maintained using Oracle undo management.<br><br> See</span> <span lang="EN-US"><a href="https://support.oracle.com/CSP/main/article?cmd=show&amp;type=NOT&amp;id=40689.1" title="ORA-1555 "><span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体;color:blue; mso-font-kerning:0pt"> Note 40689.1</span></a></span> <span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体;mso-font-kerning: 0pt" lang="EN-US">- ORA-1555 "Snapshot too old" - Detailed Explanation for more about<br> these errors.</span></p> <p style="mso-margin-top-alt:auto;mso-margin-bottom-alt: auto;text-align:left;mso-pagination:widow-orphan;mso-outline-level:3" align="left"><b><span style="font-size:13.5pt;font-family:宋体;mso-bidi-font-family:宋体; mso-font-kerning:0pt" lang="EN-US">Diagnosing</span></b></p> <p style="text-align:left;mso-pagination:widow-orphan" align="left"> <span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体; mso-font-kerning:0pt" lang="EN-US">Due to space limitations, it is not always feasible to keep undo blocks on hand for the life of the instance. Oracle Automatic Undo Management (AUM) helps to manage the time frame that undo blocks are stored. The time frame is the “retention” time for those blocks.<br><br> There are several ways to investigate the ORA-1555 error. In most cases, the error is a legitimate problem with getting to an undo block that has been overwritten due to the undo “retention” period having passed.<br><br> AUM will automatically tune up and down the “retention” period, but often space limitations or configuration of the undo tablespace will throttle back continuous increases to the “retention” period.<br><br> The error message is reported in the user session and often is not captured in the alert log. The user could see a message like<br><br> Using rollback segment functionality:<br> ORA-1555: snapshot too old (rollback segment too small)<br><br> or<br><br> Using AUM:<br> ORA-01555: snapshot too old: rollback segment number 9 with name "_SYSSMU9$" too small<br><br> If the error is captured in the alert.log, you would see something like<br><br> Tue May 26 16:16:57 2009<br> ORA-01555 caused by SQL statement below (SQL ID: 54yn3n36w24ft, Query Duration=922 sec, SCN: 0x0007.8a55f4e3)</span></p> <p style="mso-margin-top-alt:auto;mso-margin-bottom-alt: auto;text-align:left;mso-pagination:widow-orphan;mso-outline-level:4" align="left"><b><span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体; mso-font-kerning:0pt" lang="EN-US">Initial Investigation</span></b></p> <p style="mso-margin-top-alt:auto;mso-margin-bottom-alt: auto;text-align:left;mso-pagination:widow-orphan;mso-outline-level:5" align="left"><b><span style="font-size:10.0pt;font-family:宋体;mso-bidi-font-family:宋体; mso-font-kerning:0pt" lang="EN-US">Rollback Segments:</span></b></p> <p style="text-align:left;mso-pagination:widow-orphan" align="left"> <span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体; mso-font-kerning:0pt" lang="EN-US">With Oracle 10g and later versions of Oracle, you can still use a Rollback Segments configuration. ORA-1555 errors in that environment still follow older guidelines as described in<br><br></span> <span lang="EN-US"><a href="https://support.oracle.com/CSP/main/article?cmd=show&amp;type=NOT&amp;id=10579.1" title="How many Rollback Segments to Have"><span style="font-size:12.0pt; font-family:宋体;mso-bidi-font-family:宋体;color:blue;mso-font-kerning:0pt"> Note 10579.1</span></a></span> <span style="font-size:12.0pt;font-family: 宋体;mso-bidi-font-family:宋体;mso-font-kerning:0pt" lang="EN-US">- How many Rollback Segments to Have<br></span><span lang="EN-US"><a href="https://support.oracle.com/CSP/main/article?cmd=show&amp;type=NOT&amp;id=107085.1" title="Tuning Rollback Segments"><span style="font-size:12.0pt;font-family: 宋体;mso-bidi-font-family:宋体;color:blue;mso-font-kerning:0pt">Note 107085.1</span></a></span> <span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体; mso-font-kerning:0pt" lang="EN-US">- Tuning Rollback Segments<br></span><span lang="EN-US"><a href="https://support.oracle.com/CSP/main/article?cmd=show&amp;type=NOT&amp;id=69464.1" title="Rollback Segment Configuration &amp; Tips"><span style="font-size:12.0pt; font-family:宋体;mso-bidi-font-family:宋体;color:blue;mso-font-kerning:0pt">Note 69464.1</span></a></span> <span style="font-size:12.0pt;font-family: 宋体;mso-bidi-font-family:宋体;mso-font-kerning:0pt" lang="EN-US">- Rollback Segment Configuration &amp; Tips</span></p> <p style="mso-margin-top-alt:auto;mso-margin-bottom-alt: auto;text-align:left;mso-pagination:widow-orphan;mso-outline-level:5" align="left"><b><span style="font-size:10.0pt;font-family:宋体;mso-bidi-font-family:宋体; mso-font-kerning:0pt" lang="EN-US">Automatic Undo Management:</span></b></p> <p style="text-align:left;mso-pagination:widow-orphan" align="left"> <span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体; mso-font-kerning:0pt" lang="EN-US">The database will be self tuning for undo when using Automatic Undo Management. This does not eliminate ORA-1555 completely, but does minimize ORA-1555 as long as there is adequate space in the undo tablespace and workloads tend to follow repeatable patterns. In some cases with periodic changes to workload (large data updates particularly with LOB data) the self tuning of undo can become aggressive and lead to undo issues.<br><br></span><span lang="EN-US"><a href="https://support.oracle.com/CSP/main/article?cmd=show&amp;type=NOT&amp;id=461480.1" title="FAQ Automatic Undo Management (AUM) / System Managed Undo (SMU)"><span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体;color:blue; mso-font-kerning:0pt">Note 461480.1</span></a></span> <span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体;mso-font-kerning: 0pt" lang="EN-US">- FAQ Automatic Undo Management (AUM) / System Managed Undo (SMU)<br></span><span lang="EN-US"><a href="https://support.oracle.com/CSP/main/article?cmd=show&amp;type=NOT&amp;id=135053.1" title="How to Create a Database with Automatic Undo Management"><span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体;color:blue; mso-font-kerning:0pt">Note 135053.1</span></a></span> <span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体;mso-font-kerning: 0pt" lang="EN-US">-How to Create a Database with Automatic Undo Management<br></span><span lang="EN-US"><a href="https://support.oracle.com/CSP/main/article?cmd=show&amp;type=NOT&amp;id=268870.1" title="How to Shrink the datafile of Undo Tablespace"><span style="font-size: 12.0pt;font-family:宋体;mso-bidi-font-family:宋体;color:blue;mso-font-kerning:0pt">Note 268870.1</span></a></span> <span style="font-size:12.0pt;font-family: 宋体;mso-bidi-font-family:宋体;mso-font-kerning:0pt" lang="EN-US">- How to Shrink the datafile of Undo Tablespace<br></span><span lang="EN-US"><a href="https://support.oracle.com/CSP/main/article?cmd=show&amp;type=NOT&amp;id=40689.1" title="How to switch a Database from AUM back to using Rollback Segments"><span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体;color:blue; mso-font-kerning:0pt">Note 231776.1</span></a></span> <span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体;mso-font-kerning: 0pt" lang="EN-US">- How to switch a Database from Automatic Undo Management (AUM) back to using Rollback Segments<br></span><span lang="EN-US"><a href="https://support.oracle.com/CSP/main/article?cmd=show&amp;type=NOT&amp;id=296863.1" title="How to Keep all UNDO Segments from Being Offlined in Oracle 10g - Fast Ramp-Up"><span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体;color:blue; mso-font-kerning:0pt">Note 296863.1</span></a></span> <span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体;mso-font-kerning: 0pt" lang="EN-US">- How to Keep All UNDO Segments from Being Offlined in Oracle 10g - Fast Ramp-Up</span></p> <p style="mso-margin-top-alt:auto;mso-margin-bottom-alt: auto;text-align:left;mso-pagination:widow-orphan;mso-outline-level:5" align="left"><b><span style="font-size:10.0pt;font-family:宋体;mso-bidi-font-family:宋体; mso-font-kerning:0pt" lang="EN-US">LOB Issues:</span></b></p> <p style="text-align:left;mso-pagination:widow-orphan" align="left"> <span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体; mso-font-kerning:0pt" lang="EN-US">Out-of-row LOB undo is maintained in the LOB segment. So the UNDO tablespace and undo retention is not associated with most LOB ORA-1555 issues. Instead the LOB column is created using either PCT_VERSION or RETENTION to manage how much space within blocks or time transpires before the LOB undo is overwritten. In environments with high updates, deletes on rows including LOBs, the chances of ORA-1555 on LOB undo is very high.<br><br> PCT_VERSION and RETENTION are not auto-tuned. To “tune” those configuration settings, you must change the values for PCT_VERSION or RETENTION. Changes to UNDO_RETENTION does not change LOB retention time frames.<br><br></span><span lang="EN-US"><a href="https://support.oracle.com/CSP/main/article?cmd=show&amp;type=NOT&amp;id=162345.1" title="LOBS - Storage, Read Consistency and Rollback"><span style="font-size: 12.0pt;font-family:宋体;mso-bidi-font-family:宋体;color:blue;mso-font-kerning:0pt">Note 162345.1</span></a></span> <span style="font-size:12.0pt;font-family: 宋体;mso-bidi-font-family:宋体;mso-font-kerning:0pt" lang="EN-US">- LOBS - Storage, Read-consistency and Rollback<br></span><span lang="EN-US"><a href="https://support.oracle.com/CSP/main/article?cmd=show&amp;type=NOT&amp;id=386341.1" title="How to determine the actual size of the LOB segments and free unused space"><span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体;color:blue; mso-font-kerning:0pt">Note 386341.1</span></a></span> <span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体;mso-font-kerning: 0pt" lang="EN-US">- How to determine the actual size of the LOB segments and how to free the deleted/unused space above/below the HWM<br></span><span lang="EN-US"><a href="https://support.oracle.com/CSP/main/article?cmd=show&amp;type=NOT&amp;id=563470.1" title="Lob retention not changing when undo_retention is changed"><span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体;color:blue; mso-font-kerning:0pt">Note 563470.1</span></a></span> <span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体;mso-font-kerning: 0pt" lang="EN-US">– Lob retention not changing when undo_retention is changed<br></span><span lang="EN-US"><a href="https://support.oracle.com/CSP/main/article?cmd=show&amp;type=NOT&amp;id=422826.1" title="How to identify LOB Segment Use PCTVERSION or RETENTION"><span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体;color:blue; mso-font-kerning:0pt">Note 422826.1</span></a></span> <span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体;mso-font-kerning: 0pt" lang="EN-US">– How to identify LOB Segment Use PCTVERSION or RETENTION from Data Dictionary</span></p> <p style="mso-margin-top-alt:auto;mso-margin-bottom-alt: auto;text-align:left;mso-pagination:widow-orphan;mso-outline-level:4" align="left"><b><span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体; mso-font-kerning:0pt" lang="EN-US">Error Tracing</span></b></p> <p style="text-align:left;mso-pagination:widow-orphan" align="left"> <span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体; mso-font-kerning:0pt" lang="EN-US">Undo error tracing can be done for normal undo operations using the following events:<br><br> NOTE: Normal undo operations will be indicated in the error message in that the error message includes a segment name like<br><br> …. name "_SYSSMU1$" too small<br><br> If the error doesn’t show a segment name<br><br> … name "" too small<br><br> the problem is often related to LOB undo<br> If using pfile:<br><br> event="10442 trace name context forever, level 10"<br><br> If using spfile:<br><br> Alter system set events '10442 trace name context forever, level 10';<br><br> Reproduce the ORA-1555 error and upload the trace file to Oracle Support.<br><br> LOB undo error tracing is more difficult. Set additional tracing events as follows:<br><br> Start Session 1<br> Alter session set events '10046 trace name context forever, level 12';<br> Reproduce the error<br> Exit Session 1<br><br> Start Session 2<br> Alter session set events '10051 trace name context forever, level 1';<br> Reproduce the error<br> Exit Session 2<br><br> Start Session<br> Alter session set events '1555 trace name errorstack forever, level 3';<br> Reproduce the error<br> Exit Session 3<br><br> Additional resources to review:<br></span><span lang="EN-US"><a href="https://support.oracle.com/CSP/main/article?cmd=show&amp;type=NOT&amp;id=846079.1" title="LOBs and ORA-1555"><span style="font-size:12.0pt;font-family:宋体; mso-bidi-font-family:宋体;color:blue;mso-font-kerning:0pt">Note 846079.1</span></a></span> <span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体; mso-font-kerning:0pt" lang="EN-US">– LOBs and ORA-1555 troubleshooting<br></span><span lang="EN-US"><a href="https://support.oracle.com/CSP/main/article?cmd=show&amp;type=NOT&amp;id=253131.1" title="Concurrent Writes May Corrupt LOB Segment"><span style="font-size:12.0pt; font-family:宋体;mso-bidi-font-family:宋体;color:blue;mso-font-kerning:0pt">Note 253131.1</span></a></span> <span style="font-size:12.0pt;font-family: 宋体;mso-bidi-font-family:宋体;mso-font-kerning:0pt" lang="EN-US">–Concurrent Writes May Corrupt LOB Segment When Using Auto Segment Space Management<br></span><span lang="EN-US"><a href="https://support.oracle.com/CSP/main/article?cmd=show&amp;type=NOT&amp;id=467872.1" title="TROUBLESHOOTING GUIDE (TSG) - ORA-1555"><span style="font-size:12.0pt; font-family:宋体;mso-bidi-font-family:宋体;color:blue;mso-font-kerning:0pt">Note 467872.1</span></a></span> <span style="font-size:12.0pt;font-family: 宋体;mso-bidi-font-family:宋体;mso-font-kerning:0pt" lang="EN-US">– TROUBLESHOOTING GUIDE (TSG) – ORA-1555</span></p> <p style="mso-margin-top-alt:auto;mso-margin-bottom-alt: auto;text-align:left;mso-pagination:widow-orphan;mso-outline-level:4" align="left"><b><span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体; mso-font-kerning:0pt" lang="EN-US">V$UNDOSTAT Analysis</span></b></p> <p style="text-align:left;mso-pagination:widow-orphan" align="left"> <span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体; mso-font-kerning:0pt" lang="EN-US">The V$UNDOSTAT view holds undo statistics for 10 minute intervals. This view<br> represents statistics across instances, thus each begin time, end time, and<br> statistics value will be a unique interval per instance.<br><br> This does not track undo related to LOB<br></span><span lang="EN-US"><a href="https://support.oracle.com/CSP/main/article?cmd=show&amp;type=NOT&amp;id=262066.1" title="How to Size UNDO Tablespace for AUM"><span style="font-size:12.0pt; font-family:宋体;mso-bidi-font-family:宋体;color:blue;mso-font-kerning:0pt">Note 262066.1</span></a></span> <span style="font-size:12.0pt;font-family: 宋体;mso-bidi-font-family:宋体;mso-font-kerning:0pt" lang="EN-US">– How To Size UNDO Tablespace For Automatic Undo Management<br></span><span lang="EN-US"><a href="https://support.oracle.com/CSP/main/article?cmd=show&amp;type=NOT&amp;id=1112363.1" title="When Does UNDO Used Space Become Available?"><span style="font-size: 12.0pt;font-family:宋体;mso-bidi-font-family:宋体;color:blue;mso-font-kerning:0pt">Note 1112363.1</span></a></span> <span style="font-size:12.0pt;font-family: 宋体;mso-bidi-font-family:宋体;mso-font-kerning:0pt" lang="EN-US">– When Does Undo Used Space Become Available?<br></span><span lang="EN-US"><a href="https://support.oracle.com/CSP/main/article?cmd=show&amp;type=NOT&amp;id=240746.1" title="10g NEW FEATURE on AUTOMATIC UNDO RETENTION"><span style="font-size: 12.0pt;font-family:宋体;mso-bidi-font-family:宋体;color:blue;mso-font-kerning:0pt">Note 240746.1</span></a></span> <span style="font-size:12.0pt;font-family: 宋体;mso-bidi-font-family:宋体;mso-font-kerning:0pt" lang="EN-US">– 10g NEW FEATURE on AUTOMATIC UNDO RETENTION</span></p> <p style="mso-margin-top-alt:auto;mso-margin-bottom-alt: auto;text-align:left;mso-pagination:widow-orphan;mso-outline-level:4" align="left"><b><span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体; mso-font-kerning:0pt" lang="EN-US">Diagnostics Scripts</span></b></p> <p style="text-align:left;mso-pagination:widow-orphan" align="left"> <span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体; mso-font-kerning:0pt" lang="EN-US">Refer to</span> <span lang="EN-US"><a href="https://support.oracle.com/CSP/main/article?cmd=show&amp;type=NOT&amp;id=746173.1" title="Common Diagnostics Scripts"><span style="font-size:12.0pt;font-family: 宋体;mso-bidi-font-family:宋体;color:blue;mso-font-kerning:0pt"> Note 746173.1</span></a></span> <span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体; mso-font-kerning:0pt" lang="EN-US">: Common Diagnostic Scripts for AUM problems<br> and</span> <span lang="EN-US"><a href="https://support.oracle.com/CSP/main/article?cmd=show&amp;type=NOT&amp;id=877613.1" title="AUM Common Analysis/Diagnostic Scripts"><span style="font-size:12.0pt; font-family:宋体;mso-bidi-font-family:宋体;color:blue;mso-font-kerning:0pt"> Note 877613.1</span></a></span> <span style="font-size:12.0pt;font-family: 宋体;mso-bidi-font-family:宋体;mso-font-kerning:0pt" lang="EN-US">: AUM Common Analysis/Diagnostic Scripts</span></p> <p style="mso-margin-top-alt:auto;mso-margin-bottom-alt: auto;text-align:left;mso-pagination:widow-orphan;mso-outline-level:3" align="left"><b><span style="font-size:13.5pt;font-family:宋体;mso-bidi-font-family:宋体; mso-font-kerning:0pt" lang="EN-US">Common Causes/Solutions</span></b></p> <p style="mso-margin-top-alt:auto;mso-margin-bottom-alt: auto;text-align:left;mso-pagination:widow-orphan;mso-outline-level:4" align="left"><b><span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体; mso-font-kerning:0pt" lang="EN-US">Using Rollback Segments functionality:</span></b></p> <p style="text-align:left;mso-pagination:widow-orphan" align="left"> <span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体; mso-font-kerning:0pt" lang="EN-US">* Problem happening on SYSTEM tablespace that still uses old Rollback Segment functionality even when configured for Automatic Undo Management (AUM).<br><br> * There are not enough rollback segments to manage the undo needed for long running queries.<br><br> * Rollback Segments are too small and undo is overwritten before long running queries complete.</span></p> <p style="mso-margin-top-alt:auto;mso-margin-bottom-alt: auto;text-align:left;mso-pagination:widow-orphan;mso-outline-level:5" align="left"><b><span style="font-size:10.0pt;font-family:宋体;mso-bidi-font-family:宋体; mso-font-kerning:0pt" lang="EN-US">Reference:</span></b></p> <p style="text-align:left;mso-pagination:widow-orphan" align="left"> <span lang="EN-US"><a href="https://support.oracle.com/CSP/main/article?cmd=show&amp;type=NOT&amp;id=69464.1" title="Rollback Segment Configuration &amp; Tips"><span style="font-size:12.0pt; font-family:宋体;mso-bidi-font-family:宋体;color:blue;mso-font-kerning:0pt"> Note 69464.1</span></a></span> <span style="font-size:12.0pt;font-family: 宋体;mso-bidi-font-family:宋体;mso-font-kerning:0pt" lang="EN-US">– Rollback Segment Configuration &amp; Tips<br></span><span lang="EN-US"><a href="https://support.oracle.com/CSP/main/article?cmd=show&amp;type=NOT&amp;id=40689.1" title="ORA-1555: "><span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体;color:blue; mso-font-kerning:0pt">Note 10630.1</span></a></span> <span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体;mso-font-kerning: 0pt" lang="EN-US">– ORA-1555: “Snapshot too old” – Overview<br></span><span lang="EN-US"><a href="https://support.oracle.com/CSP/main/article?cmd=show&amp;type=NOT&amp;id=862469.1" title="ORA-604 &amp; ORA-1555 Rollback Segment 0 with Name "><span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体;color:blue; mso-font-kerning:0pt">Note 862469.1</span></a></span> <span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体;mso-font-kerning: 0pt" lang="EN-US">– ORA-604 &amp; ORA-1555 Rollback Segment 0 with Name “System” Too Small</span></p> <p style="mso-margin-top-alt:auto;mso-margin-bottom-alt: auto;text-align:left;mso-pagination:widow-orphan;mso-outline-level:4" align="left"><b><span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体; mso-font-kerning:0pt" lang="EN-US">Using Automatic Undo Management (AUM):</span></b></p> <p style="text-align:left;mso-pagination:widow-orphan" align="left"> <span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体; mso-font-kerning:0pt" lang="EN-US">* TUNED_UNDORETENTION in V$UNDOSTAT around the time of the error is lower than the QUERY DURATION indicated in the error message. This is a legitimate ORA-1555 and if queries are going to run for very long time frames, UNDO_RETENTION may need to be larger. Auto-tuned retention may not be able to keep up with the undo workload and staying within space limitations on the UNDO tablespace.<br><br> * LOB updates and/or deletes are frequent and a higher PCT_VERSION is required to provide enough space in the LOB Segment to accommodate the LOB undo. RETENTION on LOBs that are updated or deleted frequently can run into problems holding UNDO long enough for queries.<br><br> * QUERY DURATION shown in the error message is 30+ years and therefore, no amount of undo will satisfy the consistent read blocks.<br><br></span><span lang="EN-US"><a href="https://support.oracle.com/CSP/main/article?cmd=show&amp;type=NOT&amp;id=750195.1" title="ORA-1555 Shows Unrealistic Query Duration"><span style="font-size:12.0pt; font-family:宋体;mso-bidi-font-family:宋体;color:blue;mso-font-kerning:0pt">Note 750195.1</span></a></span> <span style="font-size:12.0pt;font-family: 宋体;mso-bidi-font-family:宋体;mso-font-kerning:0pt" lang="EN-US">– ORA-1555 Shows Unrealistic Query Duration (billions of seconds)<br><br> * QUERY DURATION shown in the error message is 0. NOTE: This has been filed as a bug on many release levels and has been very difficult to narrow down to a specific problem.<br><br></span><span lang="EN-US"><a href="https://support.oracle.com/CSP/main/article?cmd=show&amp;type=NOT&amp;id=761128.1" title="ORA-1555 Error when Query Duration as 0 Seconds"><span style="font-size: 12.0pt;font-family:宋体;mso-bidi-font-family:宋体;color:blue;mso-font-kerning:0pt">Note 761128.1</span></a></span> <span style="font-size:12.0pt;font-family: 宋体;mso-bidi-font-family:宋体;mso-font-kerning:0pt" lang="EN-US">– ORA-1555 Error when Query Duration as 0 Seconds<br><br> * QUERY DURATION is lower than TUNED_UNDRETENTION. Undo header information can sometimes get overwritten or you could be seeing a bug.<br><br> * TUNED_UNDORETENTION stays very high and UNDO tablepsace continues to grow continuously or getting space errors.<br><br></span><span lang="EN-US"><a href="https://support.oracle.com/CSP/main/article?cmd=show&amp;type=NOT&amp;id=1112431.1" title="Undo Remains Unexpired"><span style="font-size:12.0pt;font-family:宋体; mso-bidi-font-family:宋体;color:blue;mso-font-kerning:0pt">Note 1112431.1</span></a></span> <span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体; mso-font-kerning:0pt" lang="EN-US">– Undo Remains Unexpired When Using Non-autoextensible Datafiles for Undo Tablespace.</span></p> <p style="mso-margin-top-alt:auto;mso-margin-bottom-alt: auto;text-align:left;mso-pagination:widow-orphan;mso-outline-level:4" align="left"><b><span style="font-size:12.0pt;font-family:宋体;mso-bidi-font-family:宋体; mso-font-kerning:0pt" lang="EN-US">Additional Reference:</span></b></p> <p style="text-align:left;mso-pagination:widow-orphan" align="left"> <span lang="EN-US"><a href="https://communities.oracle.com/portal/server.pt/community/database_administration/227" title="Database Administration Community"><span style="font-size:12.0pt; font-family:宋体;mso-bidi-font-family:宋体;color:blue;mso-font-kerning:0pt"> Database Administration Community</span></a></span></p> <p><span lang="EN-US"><wbr></wbr></span></p> </wbr>

你可能感兴趣的:(nbsp)