详解ORA-00600[4193]错误，ORA-00600[4193]错误从版本ORACLE 6.0开始被引入，出现该ORA-00600报错的主要原因是Redo记录和Rollback(undo)回滚记录的不一致。当Oracle在验证Undo Block sequence号时对比相关block change的Redo Block中的sequence number时发现不符。该错误属于Oracle内核事务Undo管理层。
由于该错误的出现可能导致Oracle实例奔溃crash。
其2个Argument的含义为：
Arg [a] Undo 记录的sequence number
Arg [b] Redo记录的sequence number
例如：
ORA-00600: internal error code, arguments: [4193], [8023], [8068], [], [], [], [], []
通常该ORA-00600[4193]错误可能与rollback segment回滚段损坏/讹误有关。一般情况下Oracle建议通过备份恢复修复该问题，在实在没有备份的情况下可以通过手动来修复。
如果自己搞不定可以找诗檀软件专业ORACLE数据库修复团队成员帮您恢复!
诗檀软件专业数据库修复团队
服务热线 ： 13764045638 QQ号:47079569 邮箱：service@parnassusdata.com
ORA-00600[4193]错误相关的bug如下：
|
NB |
Bug |
Fixed |
Description |
|
14034244 |
11.2.0.3.BP09, 12.1.0.0 |
Lost write type corruption using ASM in 11.2.0.3 |
|
|
8240762 |
10.2.0.5, 11.1.0.7.10, 11.2.0.1 |
Undo corruptions with ORA-600 [4193]/ORA-600 [4194] or ORA-600 [4137] / SMON may spin to recover transaction |
SYMPTOMS
Copying database from one server to another server and getting an ORA-600 {4193] error when trying to open the database on the destination server.
CAUSE
The online redo logs were copied when the source database was open, online redo logs should never be copied when the database is open.
SOLUTION
In this instance the datafiles were being copied properly after the tablespaces were put in to backup mode, however, online redo logs should only be copied if the source database is shutdown first before copying the online redo logs. The source database needed to remain open so, the datafiles were copied again (with the tablespaces in backup mode) and then a number of archivelogs were transferred over to the new server and after the last archivelog was applied the database could be opened with resetlogs and new online redo logs were created on the destination server.
REFERENCES
NOTE:39282.1 – ORA-600 [4193] “seq# mismatch while adding undo record”