ORA-600 [4194] Description

 

I. Description

A friend's library cannot be opened. The error message is as follows:

 

Errors in filef: \ app \ Administrator \ diag \ RDBMS \ orcl \ trace \ orcl_ora_assist.trc (incident = 89062 ):

ORA-00600: Internal error code, parameter: [4194], [78], [8], [], [], [], [], [], [], [], [], [], []

ORA-00600: Internal error code, parameter: [4194], [78], [8], [], [], [], [], [], [], [], [], [], []

Incident Details in: F: \ app \ Administrator \ diag \ RDBMS \ orcl \ incident \ incdir_89062 \ orcl_ora_1__i89062.trc

Trace dumping is required mingid = [cdmp_20120730184640]

Errors in file F: \ app \ Administrator \ diag \ RDBMS \ orcl \ trace \ orcl_ora_assist.trc:

ORA-00600: Internal error code, parameter: [4194], [78], [8], [], [], [], [], [], [], [], [], [], []

ORA-00600: Internal error code, parameter: [4194], [78], [8], [], [], [], [], [], [], [], [], [], []

Mon Jul 30 18:46:41 2012

Errors in filef: \ app \ Administrator \ diag \ RDBMS \ orcl \ trace \ orcl_ora_assist.trc (incident = 90109 ):

ORA-00603: Oracle Server session terminatedby fatal error

ORA-00600: Internal error code, arguments: [4194], [78], [8], [], [], [], [], [], [], [], [], [], []

ORA-00600: Internal error code, arguments: [4194], [78], [8], [], [], [], [], [], [], [], [], [], []

Incident Details in: F: \ app \ Administrator \ diag \ RDBMS \ orcl \ incident \ incdir_90109 \ orcl_ora_1__i90109.trc

Errors in filef: \ app \ Administrator \ diag \ RDBMS \ orcl \ incident \ incdir_90109 \ orcl_ora_pai_i90109.trc:

ORA-00603: Oracle Server session terminatedby fatal error

ORA-00600: Internal error code, arguments: [4194], [78], [8], [], [], [], [], [], [], [], [], [], []

ORA-00600: Internal error code, arguments: [4194], [78], [8], [], [], [], [], [], [], [], [], [], []

 

The ORA-600 in [41xx] format is related to undo.

 

Ii. Description of MOS ORA-600 [4194]

 

ORA-600 [4194] "undo record numbermismatch while adding undo record" [ID 39283.1]

 

Error:

Format: ORA-600 [4194] [a] [B]

 

Versions:

Versions 6.0 to 10.1

 

Description:

 

Amismatch has been detected between redo records and rollback (UNDO) records.

-- This error indicates that the redo records and rollback (UNDO) records are inconsistent.

 

Weare validating the Undo Record Number relating to the change being appliedagainst the maximum undo record number recorded in the Undo block.

 

Thiserror is reported when the validation fails.

 

Arguments:

Arg [a] maximum undo record number in undo Block

-- The parameter [a] Here is the maximum number of Undo records in the Undo block.

Arg [B] Undo record number from redo Block

-- The parameter [B] is the Undo records in the redo block.

 

Functionality:

Kernel transaction undo called from cache Layer

 

Impact:

Processfailure

Possible rollback segment failed uption

 

Suggestions:

This error may indicate a rollback segment failed uption.

This may require a recovery from a database backup depending on thesituation.

 

 

Iii. Solution

Recreate the Undo tablespace. For more information, see:

How to deal with currentonline redo and undo corruption

Http://blog.csdn.net/tianlesoftware/article/details/6261475

 

 

Related links:

Oracle undo tablespace Management

Http://blog.csdn.net/tianlesoftware/article/details/5689558

 

OracleORA-600 [4193] solution description

Http://blog.csdn.net/tianlesoftware/article/details/7238771

 

 

 

 

 

 

Bytes -------------------------------------------------------------------------------------------------------

All rights reserved. reprinted articles are allowed, but source addresses must be indicated by links. Otherwise, the documents will be held legally responsible!

Skype: tianlesoftware

QQ: tianlesoftware@gmail.com

Email: tianlesoftware@gmail.com

Blog: http://www.tianlesoftware.com

WEAVER: http://weibo.com/tianlesoftware

Twitter: http://twitter.com/tianlesoftware

Facebook: http://www.facebook.com/tianlesoftware

LinkedIn: http://cn.linkedin.com/in/tianlesoftware

 

 

------- Add a group to describe the relationship between Oracle tablespace and data files in the remarks section. Otherwise, reject the application ----

Dba1 group: 62697716 (full); dba2 group: 62697977 (full) dba3 group: 62697850 (full)

Super DBA group: 63306533 (full); dba4 group: 83829929 dba5 group: 142216823

Dba6 group: 158654907 dba7 group: 172855474 DBA group: 104207940