I think space is the only issue with a large undo_rention area. However do you really want a job to be running for 36 hours
Is the table not partitioned? If so then use the partition option of dbms_stats and break the job down into smaller sections
HTH
John
__ __
From: oracle-l-bounce@(protected) [mailto:oracle-l-bounce@(protected)] On Behalf Of Roger Xu Sent: 29 September 2005 22:33 To: Oracle-L@(protected) Org (E-mail) Subject: "snapshot too old" and undo_retention
Hi List,
Background: Oracle 9.2.0 w/ Auto Undo Management
We have a huge table and it takes more than 24 hours to collect its statistics.
But the undo_retention is set to 864000 i.e. 24 hours. As a result we see the following a lot.
Since we have lots of space in the undo tablespace, I am thinking of increasing undo_retention to 36 hours
via "ALTER SYSTEM SET UNDO_RETENTION = 129600;"
Is this my only choice?
What are the drawbacks to have a large undo_retention value assuming we never run out undo tablespace?
Thanks,
Roger Xu
This e-mail is intended solely for the person or entity to which it is addressed and may contain confidential and/or privileged information. Any review, dissemination, copying, printing or other use of this e-mail by persons or entities other than the addressee is prohibited. If you have received this e-mail in error, please contact the sender immediately and delete the material. __ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ _____ This email has been scanned for all viruses by the MessageLabs Email Security System. Any questions please call 972-721-8257 or email your request to tech_support@(protected)
<p class=MsoNormal><font size=2 color=blue face="Comic Sans MS"><span style='font-size:10.0pt;font-family:"Comic Sans MS";color:blue'>If it is a huge table then it does not really matter how accurate the statistics are so why bother gathering them. Estimate them instead.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Courier><span style='font-size:10.0pt; font-family:Courier'>I think space is the only issue with a large undo_rention area. However do you really want a job to be running for 36 hours<o:p></o:p>< /span></font></p>
<p class=MsoNormal><font size=2 face=Courier><span style='font-size:10.0pt; font-family:Courier'>Is the table not partitioned? If so then use the partition option of dbms_stats and break the job down into smaller sections<o:p></o:p>< /span></font></p>
<p><font size=2 face=Courier><span style='font-size:10.0pt;font-family:Courier' >We have a huge table and it takes more than 24 hours to collect its statistics.< /span></font><o:p></o:p></p>
<p><font size=2 face=Courier><span style='font-size:10.0pt;font-family:Courier' >But the undo_retention is set to 864000 i.e. 24 hours. As a result we see the following a lot.</span></font><o:p></o:p></p>
<p><font size=2 face=Courier><span style='font-size:10.0pt;font-family:Courier' >"ORA-01555 (See ORA-01555.ora-code.com): snapshot too old: rollback segment number 11 with name "_SYSSMU11$" too small"</span></font><o:p></o:p></p>
<p><font size=2 face=Courier><span style='font-size:10.0pt;font-family:Courier' >Since we have lots of space in the undo tablespace, I am thinking of increasing undo_retention to 36 hours</span></font><o:p></o:p></p>
<p><font size=2 face=Courier><span style='font-size:10.0pt;font-family:Courier' >Is this my only choice?</span></font><o:p></o:p></p>
<p><font size=2 face=Courier><span style='font-size:10.0pt;font-family:Courier' >What are the drawbacks to have a large undo_retention value assuming we never run out undo tablespace?</span></font><o:p></o:p></p>
<p><font size=3 face="Times New Roman"><span style='font-size:12.0pt'> <o :p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size: 12.0pt'><br> This e-mail is intended solely for the person or entity to which it is addressed and may contain confidential and/or privileged information. Any review, dissemination, copying, printing or other use of this e-mail by persons or entities other than the addressee is prohibited. If you have received this e-mail in error, please contact the sender immediately and delete the material. <br> __ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ _____<br> This email has been scanned for all viruses by the MessageLabs Email Security System. Any questions please call 972-721-8257 or email your request to tech_support@(protected)<o:p></o:p></span></font></p>