<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>《9i库遇到ORA-01595/ORA-01594》的评论</title>
	<atom:link href="https://www.xifenfei.com/2012/05/9i%e5%ba%93%e9%81%87%e5%88%b0ora-01595ora-01594.html/feed" rel="self" type="application/rss+xml" />
	<link>https://www.xifenfei.com/2012/05/9i%e5%ba%93%e9%81%87%e5%88%b0ora-01595ora-01594.html</link>
	<description>提供7*24专业数据库(Oracle,SQL Server,MySQL,PostgreSQL等)恢复和技术支持@Tel:17813235971</description>
	<lastBuildDate>Thu, 11 Dec 2025 02:46:14 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>作者：惜分飞</title>
		<link>https://www.xifenfei.com/2012/05/9i%e5%ba%93%e9%81%87%e5%88%b0ora-01595ora-01594.html/comment-page-1#comment-824</link>
		<dc:creator><![CDATA[惜分飞]]></dc:creator>
		<pubDate>Mon, 14 May 2012 05:19:36 +0000</pubDate>
		<guid isPermaLink="false">https://www.xifenfei.com/?p=3142#comment-824</guid>
		<description><![CDATA[OERR: ORA 1594 &quot;attempt to wrap into rollback segment (%s) extent (%s) which i [ID 18992.1]
[shell]
Error:  ORA 1594
Text:   attempt to wrap into rollback segment (%s) extent (%s) which is being fr
        eed
-------------------------------------------------------------------------------
Cause:  Undo generated to free a rollback segment extent is attempting
        to write into the same extent due to small extents and/or too
        many extents to free
Action: The rollback segment shrinking will be rollbacked by the system;
        increase the optimal size of the rollback segment.
 

*** Important: The notes below are for experienced users - See Note:22080.1


Explanation:
        1594 is reported when a rollback segment is being shrunk but there is 
        not enough space in the current undo extent to complete the job. 
        Shrinking uses whatever is available in the current extent in the 
        rollback segment. If no more space is left and the extent you 
        would move into is one that is being freed you will get 1594. 
        This error is harmless. When you retry, chances are you will not get 
        the same error again. 
 
        Usually this is caused by running a transaction after a huge 
        transaction commits. Because of the setting of OPTIMAL, a very large 
        number of extents need to be deallocated all at once.

        One way to avoid this problem is to have larger extent size. 
        Another way is to have a larger OPTIMAL setting, so that only a smaller
        number of extents will be removed at one time. 

        SET TRANSACTION USE ROLLBACK SEGMENT is also a good idea for large
        jobs so you know which rollback segment they will use.
 
        
Note:   There are changes to the way SMON shrinks rollback segments
        in 7.2. It should try to shrink a small number of extents at
        a time.
[/shell]]]></description>
		<content:encoded><![CDATA[<p>OERR: ORA 1594 &#8220;attempt to wrap into rollback segment (%s) extent (%s) which i [ID 18992.1]</p>
<pre class="brush: bash; title: ; notranslate">
Error:  ORA 1594
Text:   attempt to wrap into rollback segment (%s) extent (%s) which is being fr
        eed
-------------------------------------------------------------------------------
Cause:  Undo generated to free a rollback segment extent is attempting
        to write into the same extent due to small extents and/or too
        many extents to free
Action: The rollback segment shrinking will be rollbacked by the system;
        increase the optimal size of the rollback segment.
 

*** Important: The notes below are for experienced users - See Note:22080.1


Explanation:
        1594 is reported when a rollback segment is being shrunk but there is 
        not enough space in the current undo extent to complete the job. 
        Shrinking uses whatever is available in the current extent in the 
        rollback segment. If no more space is left and the extent you 
        would move into is one that is being freed you will get 1594. 
        This error is harmless. When you retry, chances are you will not get 
        the same error again. 
 
        Usually this is caused by running a transaction after a huge 
        transaction commits. Because of the setting of OPTIMAL, a very large 
        number of extents need to be deallocated all at once.

        One way to avoid this problem is to have larger extent size. 
        Another way is to have a larger OPTIMAL setting, so that only a smaller
        number of extents will be removed at one time. 

        SET TRANSACTION USE ROLLBACK SEGMENT is also a good idea for large
        jobs so you know which rollback segment they will use.
 
        
Note:   There are changes to the way SMON shrinks rollback segments
        in 7.2. It should try to shrink a small number of extents at
        a time.
</pre>
]]></content:encoded>
	</item>
	<item>
		<title>作者：惜分飞</title>
		<link>https://www.xifenfei.com/2012/05/9i%e5%ba%93%e9%81%87%e5%88%b0ora-01595ora-01594.html/comment-page-1#comment-823</link>
		<dc:creator><![CDATA[惜分飞]]></dc:creator>
		<pubDate>Mon, 14 May 2012 05:18:52 +0000</pubDate>
		<guid isPermaLink="false">https://www.xifenfei.com/?p=3142#comment-823</guid>
		<description><![CDATA[With AUM Enabled ORA-01594 and ORA-01595 Found in the alert.log [ID 280151.1]
[shell]Applies to:
Oracle Server - Enterprise Edition - Version: 9.2.0.1 to 9.2.0.8 - Release: 9.2 to 9.2
Information in this document applies to any platform.

Symptoms
The following errors are logged to alert.log:

ORA-01595: error freeing extent (2) of rollback segment (10))
ORA-01594: attempt to wrap into rollback segment (10) extent (2) which is being freed

Automatic Undo Management is enabled.

Cause
This is a known problem and there is an Internal Bug:2181139 for this Issue.

The error is signaled because smon is shrinking a rollback segment and this 
fails because we need an extent to store some rollback information. 
This is a failure message for the shrinking. Subsequently smon would succeed in doing that.

Solution
Ignore these error messages.
Normally adding more undo space should solve the problem, 
but if space is not correcting the problem, please file an SR for assistance.

This error message logging is fixed in 10g.[/shell]]]></description>
		<content:encoded><![CDATA[<p>With AUM Enabled ORA-01594 and ORA-01595 Found in the alert.log [ID 280151.1]</p>
<pre class="brush: bash; title: ; notranslate">Applies to:
Oracle Server - Enterprise Edition - Version: 9.2.0.1 to 9.2.0.8 - Release: 9.2 to 9.2
Information in this document applies to any platform.

Symptoms
The following errors are logged to alert.log:

ORA-01595: error freeing extent (2) of rollback segment (10))
ORA-01594: attempt to wrap into rollback segment (10) extent (2) which is being freed

Automatic Undo Management is enabled.

Cause
This is a known problem and there is an Internal Bug:2181139 for this Issue.

The error is signaled because smon is shrinking a rollback segment and this 
fails because we need an extent to store some rollback information. 
This is a failure message for the shrinking. Subsequently smon would succeed in doing that.

Solution
Ignore these error messages.
Normally adding more undo space should solve the problem, 
but if space is not correcting the problem, please file an SR for assistance.

This error message logging is fixed in 10g.</pre>
]]></content:encoded>
	</item>
</channel>
</rss>
