<?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>《ORA-600 kghstack_free2异常恢复》的评论</title>
	<atom:link href="https://www.xifenfei.com/2013/02/ora-00600kghstack_free2%e5%bc%82%e5%b8%b8%e6%81%a2%e5%a4%8d.html/feed" rel="self" type="application/rss+xml" />
	<link>https://www.xifenfei.com/2013/02/ora-00600kghstack_free2%e5%bc%82%e5%b8%b8%e6%81%a2%e5%a4%8d.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/2013/02/ora-00600kghstack_free2%e5%bc%82%e5%b8%b8%e6%81%a2%e5%a4%8d.html/comment-page-1#comment-1275</link>
		<dc:creator><![CDATA[惜分飞]]></dc:creator>
		<pubDate>Wed, 20 Feb 2013 12:00:40 +0000</pubDate>
		<guid isPermaLink="false">https://www.xifenfei.com/?p=4162#comment-1275</guid>
		<description><![CDATA[ORA-00600 [kghstack_free2] and Database doesn&#039;t Open
[shell]
Cause
Because of the crash redo log have been corrupted.

This issue could reproduce in environments that are using IMU, see Bug 5762424


Solution
1) In order to open database you will have to use event 10513 to stop TX recovery.

    a) If using init.ora, update the file with this line and bounce database 

        event = &quot;10513 trace name context forever, level 2&quot; 

   b) If using spfile: 

       sqlplus /nolog 
       connect / as sysdba 
       startup mount 
       alter system set event= &#039;10513 trace name context forever, level 2&#039; scope=spfile; 
       shutdown 
       startup 

2) Find the offending object in the trace file looking at the current statement or based on a block dump

3) drop this object

4) remove event 10513

5) disable IMU

     _in_memory_undo=FALSE 

6) startup database.
[/shell]]]></description>
		<content:encoded><![CDATA[<p>ORA-00600 [kghstack_free2] and Database doesn&#8217;t Open</p>
<pre class="brush: bash; title: ; notranslate">
Cause
Because of the crash redo log have been corrupted.

This issue could reproduce in environments that are using IMU, see Bug 5762424


Solution
1) In order to open database you will have to use event 10513 to stop TX recovery.

    a) If using init.ora, update the file with this line and bounce database 

        event = &quot;10513 trace name context forever, level 2&quot; 

   b) If using spfile: 

       sqlplus /nolog 
       connect / as sysdba 
       startup mount 
       alter system set event= '10513 trace name context forever, level 2' scope=spfile; 
       shutdown 
       startup 

2) Find the offending object in the trace file looking at the current statement or based on a block dump

3) drop this object

4) remove event 10513

5) disable IMU

     _in_memory_undo=FALSE 

6) startup database.
</pre>
]]></content:encoded>
	</item>
</channel>
</rss>
