ORA-00600 internal error code


ORA-00600 internal error code, arguments: [string], [string], [string], [string], [string], [string], [string], [string]

Cause: This is the generic internal error number for Oracle program exceptions.
This indicates that a process has encountered a low-level, unexpected condition.
Causes of this message include:
- timeouts
- file corruption
- failed data checks in memory
- hardware, memory, or I/O errors
- incorrectly restored files

Action: Report as a bug - the first argument is the internal error number

Reference: Oracle Documentation


Description of ORA-00600:
A typical ORA-00600 error does not include descriptive text. The message text can be followed by up to six arguments, which indicate the origin and attributes of the error. The first argument is the internal error number. Other arguments are various numbers, names, and character strings. The numbers may change meanings between different versions of Oracle. Empty brackets may be ignored.

In addition to being returned to the user, internal errors are also written to the Alert file along with additional information about the event. The Alert file also lists any trace files that may have been generated because of an internal error.

If you receive an ORA-00600 message, report it to Oracle Support Services.


Troubleshooting ORA-00600:
Assume we encounter following ORA-00600 exception
- ORA-00600: internal error code, arguments: [17069],[18798616],[],[],[]

Metalink provides a very useful ORA-00600 Troubleshooter tool (Metalink Note:153788.1) to allow you to get the description for an ORA-00600 error. In this web tool, we can enter the 17069 (first argument) for the 17069 error:

Login into the Metalink account and search for doc id “153788.1? in the Quick find search bar and open the document.

Follow following steps to lookup by code:
a. Select the correct Error code ORA-00600
b. Provide first argument of ORA-00600
c. Select the appropriate database version
d. Click Lookup Error button



Related Posts:
ORA-04031: unable to allocate n bytes of shared memory
- ORA-01157: cannot identify/lock data file string - see DBWR trace file
- ORA-00849: SGA_TARGET cannot be set to more than MEMORY_MAX_TARGET
- ORA-27101: shared memory realm does not exist
- ORA-00604: error occurred at recursive SQL level string
- ORA-00257: archiver error. Connect internal only, until freed
- ORA-16000: database open for read-only access

7 comments:

  1. One of the best article I read on Ora-00600, thanks for your efforts.

    ReplyDelete
  2. Thanks, helpful article.

    ReplyDelete
  3. Write more, thats all I have to say. Literally, it
    seems as though you relied on the video to make your point.

    You obviously know what youre talking about,
    why waste your intelligence on just posting videos to your blog when you could be giving us something informative to read?


    Also visit my site; Path of Exile Wraeclast

    ReplyDelete
  4. Great explanation Nimish.

    Thanks
    Ajay

    ReplyDelete
  5. Oracle site says : Visit My Oracle Support to access the ORA-00600 http://docs.oracle.com/cd/E11882_01/server.112/e17766/e0.htm

    ReplyDelete