oracle ORA-00600：内部错误代码，参数：[4194]、[65]、[51]
声明：本页面是StackOverFlow热门问题的中英对照翻译，遵循CC BY-SA 4.0协议，如果您需要使用它，必须同样遵循CC BY-SA许可，注明原文地址和作者信息，同时你必须将它归于原作者（不是我）：StackOverFlow
原文地址: http://stackoverflow.com/questions/18050871/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
ORA-00600: internal error code, arguments: [4194], [65], [51]
提问by ???
I have issue on Oracle.
我在 Oracle 上有问题。
When I execute startup to open database there is error in alert log that ORA-00600: internal error code.
当我执行启动以打开数据库时，警报日志中出现错误 ORA-00600: 内部错误代码。
Oracle was working without issue and suddenly this issue is arose.
Oracle 工作没有问题，突然出现了这个问题。
Oracle version is 10g express.
Oracle 版本是 10g express。
I just wonder if this issue can be happened when DBF file size is over 10G.
我只是想知道当 DBF 文件大小超过 10G 时是否会发生此问题。
I added another datafile to the tablespace last week.
上周我向表空间添加了另一个数据文件。
I wonder if express version can not add more datafiles.
我想知道是否express版本不能添加更多数据文件。
Could you please tell me what would be issue ?
你能告诉我会有什么问题吗？
ORA-00600: internal error code, arguments: [4194], [65], [51], [], [], [], [], []
ORA-00600：内部错误代码，参数：[4194]、[65]、[51]、[]、[]、[]、[]、[]
回答by APC
"I just wonder if this issue can be happened when DBF file size is over 10G."
“我只是想知道当 DBF 文件大小超过 10G 时是否会发生这个问题。”
Oracle XE is free but comes with various restrictions. In 10g the limit on User Data was 4GB (citation), although I would expect that limit to be enforced gracefully. Does that total cover all datafilesi.e. including Undo and Temporary tablespaces?
Oracle XE 是免费的，但有各种限制。在 10g 中，用户数据的限制为 4GB （引用），尽管我希望该限制能够正常执行。该总数是否涵盖所有数据文件，即包括撤消和临时表空间？
"I added another datafile to the tablespace last week."
“我上周在表空间中添加了另一个数据文件。”
When you added that additional file did you breach that 4GB User Data limit? Note that in 11g the User Data limit was raised to 11GB, so that would be a good reason for you to upgrade. Check it out.
当您添加该附加文件时，您是否违反了 4GB 用户数据限制？请注意，在 11g 中，用户数据限制提高到 11GB，因此这将是您升级的一个很好的理由。 检查一下。
Anyway, ORA-00600 is Oracle's generic message which it throws whenever it encounters unexpected behaviour, i.e. an internal bug. The usual advice for this is to contact Oracle Support but most XE users don't have Support contracts. In which case there is the Oracle TechNet forums, which include a site dedicated to XE issues. Find it here.
无论如何，ORA-00600 是 Oracle 的通用消息，它在遇到意外行为（即内部错误）时抛出。通常的建议是联系 Oracle 支持，但大多数 XE 用户没有支持合同。在这种情况下，有 Oracle TechNet 论坛，其中包括一个专门讨论 XE 问题的站点。 在这里找到它。
There should be more information in the Alert Log. You can find the Alert Log in the background dump directory. If you don't know where that is, locate it in SQL*Plus
警报日志中应该有更多信息。您可以在后台转储目录中找到警报日志。如果您不知道它在哪里，请在 SQL*Plus 中找到它
SQL> show parameter background_dump_dest
The chances are this is probably a corruption issue. You'll be fine (provided you have been doing proper back-ups) as Oracle's recovery utilities are pretty good. Find out more.
这很可能是腐败问题。您会没事的（前提是您进行了适当的备份），因为 Oracle 的恢复实用程序非常好。 了解更多。
回答by ParnassusData
ORA-600 [4194] "Undo Record Number Mismatch While Adding Undo Record"
VERSIONS:
versions 6.0 to 10.1
DESCRIPTION:
A mismatch has been detected between Redo records and rollback (Undo)
records.
We are validating the Undo record number relating to the change being
applied against the maximum undo record number recorded in the undo block.
This error is reported when the validation fails.
ARGUMENTS:
Arg [a] Maximum Undo record number in Undo block
Arg [b] Undo record number from Redo block
FUNCTIONALITY:
Kernel Transaction Undo called from Cache layer
IMPACT:
PROCESS FAILURE
POSSIBLE ROLLBACK SEGMENT CORRUPTION
You'd better restore your undo tablespace from rman backup ,it may fix this problem. If any backup is unavailable , then PRM-DUL (an Oracle Recovery/Rescue Tools ) can be your last resort .
你最好从 rman 备份恢复你的撤销表空间，它可能会解决这个问题。如果任何备份不可用，那么 PRM-DUL（一种 Oracle 恢复/救援工具）可能是您的最后手段。
回答by Vibin Vijay
First make the copy of table which creates problem. rename the table original table and then duplicate table to be given the name of original table.Then run query it will work.
首先制作产生问题的表的副本。重命名表原始表，然后复制表以赋予原始表的名称。然后运行查询它会起作用。
回答by mahi_0707
I encountered this error during PL/SQL development using TOAD. I opened a new session and the error disappeared!
我在使用TOAD 的PL/SQL 开发过程中遇到了这个错误。我打开了一个新会话，错误消失了！
