ORA-00600: internal error code, arguments: , , , , , , , 
Our production database encountered with above oracle error. Our database server stuck after sending error. We are be able to select and perform some work using super user with sysdba privilege but other user were unable to perform transaction.
We checked Oracle support documentation and found workaround for this bug.
The error “ORA-00600: internal error code, arguments: , , , , , , , ” is received when problems with UNDO space occur.
How to fix and what is the solution?
Oracle support provides following workaround.
Making a new UNDO tablespace:
create undo tablespace undotbs3 datafile ‘… / oracle / oradata / testdb / undotbs3.dbf ’size 400m;
we define the problem segment using following SELECT query using SYSDBA privilege.
select segment_name, status from dba_rollback_segs;
Now we need to assign a new UNDO tablespace to the system:
alter system set undo_tablespace = undotbs3 scope = both;
In the init.ora initialization file, add the line:
_corrupted_rollback_segments = ”_ SYSSMU3$” _SYSSMU3$ is our corrupted rollback segment.
Load the database with our new init.ora parameter file using command startup pfile=<name with full destination of parameter file>
Then we delete the damaged or corrupted rollback segment:
drop rollback segment "_SYSSMU3$";
Reasons behind this kind of ORA-600 errors and more detailing about ORA 600 errors you can find out from my main article called Why ORA-00600 errors are irritating Oracle DBA Specialists? You can find this link. For more Oracle DBA tutorials and tips stay connected with our Expert DBA Club Blog and this blog is running by Dbametrix Team.