ORA-00600: internal error code, arguments: [4194], [65], [51]

1
votes

I have issue on Oracle.

When I execute startup to open database there is error in alert log that ORA-00600: internal error code.

Oracle was working without issue and suddenly this issue is arose.

Oracle version is 10g express.

I just wonder if this issue can be happened when DBF file size is over 10G.

I added another datafile to the tablespace last week.

I wonder if express version can not add more datafiles.

Could you please tell me what would be issue ?

ORA-00600: internal error code, arguments: [4194], [65], [51], [], [], [], [], []

4
oracleoracle-xeora-00600
10g Express Edition only supports 4GB. If you want to get around that limitation you'll either need to buy something, such as personal edition, or upgrade to 11g express edition. – Jon Heller

4 Answers

3
votes

"I just wonder if this issue can be happened when DBF file size is over 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 datafiles i.e. including Undo and Temporary tablespaces?

"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.

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.

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>  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.

0
votes
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 .

0
votes

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.

0
votes

I encountered this error during PL/SQL development using TOAD. I opened a new session and the error disappeared!