<?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[2037]与ORA-07445[kcbs_dump_adv_state]错误》的评论</title>
	<atom:link href="https://www.xifenfei.com/2013/04/ora-6002037%e4%b8%8eora-07445kcbs_dump_adv_state%e9%94%99%e8%af%af.html/feed" rel="self" type="application/rss+xml" />
	<link>https://www.xifenfei.com/2013/04/ora-6002037%e4%b8%8eora-07445kcbs_dump_adv_state%e9%94%99%e8%af%af.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/04/ora-6002037%e4%b8%8eora-07445kcbs_dump_adv_state%e9%94%99%e8%af%af.html/comment-page-1#comment-1377</link>
		<dc:creator><![CDATA[惜分飞]]></dc:creator>
		<pubDate>Tue, 16 Apr 2013 06:34:08 +0000</pubDate>
		<guid isPermaLink="false">https://www.xifenfei.com/?p=4262#comment-1377</guid>
		<description><![CDATA[During Startup (Open Database) Alert Log Shows ORA-600[2037] and ORA-7445[kcbs_dump_adv_state] [ID 551993.1]
[shell]
Applies to:

Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 10.2.0.3 - Release: 10.2 to 10.2
Information in this document applies to any platform.
***Checked for relevance on 22-Feb-2012***
Symptoms

The database may crash and fail to open due to undo/redo corruption if you are using distributed transactions. 
The following error may be seen in the alert log:

     ORA-00600: internal error code, arguments: [2037]

The call stack can look like this:
     kcoexam kcbtema kcrpap kcrpdv kxfprdp ...

In addition, the following error may also be seen in the alert log:

     ORA-07445: exception encountered: core dump [kcbs_dump_adv_state]


Cause

The problem is caused by Bug 4899479  Undo/redo corruption if distributed transactions used.

Details:            
     Redo/undo corruption and associated dumps and/or ORA-600 errors/memory corruption can 
     occur from a transaction which uses &quot;in memory undo&quot; pool memory if the transaction also 
     includes distributed operations.  e.g.: Insert using buffered inserts, distributed operation, 
     subsequent insert can lead to this problem if the first insert uses in-memory undo.


Solution

To resolve the corruption, you will need to do a point in time recovery from a good backup.

To prevent the bug from occurring, you may choose either of these options:

     1. Apply the 10.2.0.4 patchset which was not available at the time of this writing (Feb 2008).
     2. Check MetaLink for backport Patch 4899479 for your operating system and database release.
[/shell]]]></description>
		<content:encoded><![CDATA[<p>During Startup (Open Database) Alert Log Shows ORA-600[2037] and ORA-7445[kcbs_dump_adv_state] [ID 551993.1]</p>
<pre class="brush: bash; title: ; notranslate">
Applies to:

Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 10.2.0.3 - Release: 10.2 to 10.2
Information in this document applies to any platform.
***Checked for relevance on 22-Feb-2012***
Symptoms

The database may crash and fail to open due to undo/redo corruption if you are using distributed transactions. 
The following error may be seen in the alert log:

     ORA-00600: internal error code, arguments: [2037]

The call stack can look like this:
     kcoexam kcbtema kcrpap kcrpdv kxfprdp ...

In addition, the following error may also be seen in the alert log:

     ORA-07445: exception encountered: core dump [kcbs_dump_adv_state]


Cause

The problem is caused by Bug 4899479  Undo/redo corruption if distributed transactions used.

Details:            
     Redo/undo corruption and associated dumps and/or ORA-600 errors/memory corruption can 
     occur from a transaction which uses &quot;in memory undo&quot; pool memory if the transaction also 
     includes distributed operations.  e.g.: Insert using buffered inserts, distributed operation, 
     subsequent insert can lead to this problem if the first insert uses in-memory undo.


Solution

To resolve the corruption, you will need to do a point in time recovery from a good backup.

To prevent the bug from occurring, you may choose either of these options:

     1. Apply the 10.2.0.4 patchset which was not available at the time of this writing (Feb 2008).
     2. Check MetaLink for backport Patch 4899479 for your operating system and database release.
</pre>
]]></content:encoded>
	</item>
</channel>
</rss>
