Oracle Database ORA-600 4194/ORA-600 4193/ORA-600 4137 troubleshooting

General steps for handling common undo exception errors, ORA-600 4193, ORA-600 4194, ORA-600 4137, etc.
Applicable version
Oracle Database-Enterprise Edition-Version 9.2.0.1 to 11.2.0.4 [Release 9.2 to 11.2]
Information in this document applies to any platform.
Error message
The following error is occurring in the alert. log right before the database crashes.
 
ORA-00600: internal error code, arguments: [4194], [#], [#], [], [], [], [], [], []
 
This error indicates that a mismatch has been detected between redo records and rollback (undo) records.
 
ARGUMENTS:
 
Arg [a]-Maximum Undo record number in Undo block
Arg [B]-Undo record number from Redo block
 
Since we are adding a new undo record to our undo block, we wowould perform CT that the new record number
Is equal to the maximum record number in the undo block plus one. Before Oracle can add
A new undo record to the undo block it validates that this is correct. If this validation fails,
Then an ORA-600 [4194] will be triggered.
Error cause
This also can be cause by the following defect
 
Bug 8240762 Abstract: Undo events uptions with ORA-600 [4193]/ORA-600 [4194] or ORA-600 [4137] after SHRINK
 
Details:
Undo Upload uption may be caused after a shrink and the same undo block may be used
For two different transactions causing several internal errors like:
ORA-600 [4193]/ORA-600 [4194] for new transactions
ORA-600 [4137] for a transaction rollback
Procedure
Best practice to create a new undo tablespace.
This method implements des segment check.
 
Create pfile from spfile to edit
> Create pfile from spfile;
 
1. Shutdown the instance
 
2. set the following parameters in the pfile
Undo_management = manual
Event = '10513 trace name context forever, level 2'
 
3.> startup restrict pfile = <initsid. ora>
 
4.> select tablespace_name, status, segment_name from dba_rollback_segs where status! = 'Offline ';
 
This is critical-we are looking for all undo segments to be offline-System will always be online.
 
If any are 'partly available' or 'needs RECOVERY '-Please open an issue with Oracle Support or update the current SR.
 
If all offline then continue to the next step
 
5. Create new undo tablespace-example
> Create undo tablespace <new undo tablespace> datafile <datafile> size 2000 M;
 
6. Drop old undo tablespace
> Drop tablespace <old undo tablespace> including contents and datafiles;
 
7.> shutdown immediate;
 
8> startup nomount; --> Using your Original spfile
 
9 modify the spfile with the new undo tablespace name
 
Alter system set undo_tablespace = '<new tablespace created in step 5>' scope = spfile;
 
10.> shutdown immediate;
 
11.> startup; --> Using spfile
 
 
 
The reason we create a new undo tablespace first is to use new undo segment numbers
That are higher then the current segments being used.
This way when a transaction goes to do block clean-out
The reference to that undo segment does not exist and continues with the block clean-out.