ORA-00600 ORA-07445 ORA-00700 : How to Diagnose and Fix Them
A quick note to explain how to deal with these errors, so I don't have to keep answering the same questions.
Oracle trap errors and gives them a specific error number. Looking up this error number in the Database Error Messages manual will typically give you an indication of the cause of the error and the action necessary to fix it.
In addition to trapping specific errors, Oracle also has some catch-all error messages that are issued when something unexpected happens, the most important being the following.
- ORA-00600: internal error code, arguments: [string], [string], [string], [string], [string], [string], [string], [string], [string], [string], [string], [string]
- ORA-07445: exception encountered: core dump [string] [string] [string] [string] [string] [string]
- ORA-00700: soft internal error, arguments: [string], [string], [string], [string], [string], [string], [string], [string], [string], [string], [string], [string]
These may be caused by something trivial, but they could also indicate something disastrously wrong has happened. It's impossible to tell by just looking at the error message and the description in the Database Error Messages manual.
This article explains what you should do if you encounter one of these types of messages.
ORA-600/ORA-7445/ORA-700 Error Look-up Tool
You should typically use the following process.
- Log on to My Oracle Support.
- Go to the ORA-600/ORA-7445/ORA-700 Error Look-up Tool.
- Select the type of error (ORA-600/ORA-7445/ORA-700), enter the value of the first argument (the value within the first set of square brackets [?????]) and select the database version from the dropdown list.
- Click the "Lookup Error" button.
- Read the popup message and take the appropriate action.
The popup will contain one of two types of messages.
- If the issue has been encountered before, the popup will usually include a reference to a support note that will explain how to fix it. This may be a manual configuration change, or the application of a patch.
- If the issue has not been encountered before, you will be asked to raise a new Support Request (SR) so Oracle Support can investigate it.
You can of course Google for a solution, but for these types of errors I would suggest that is a bad idea and you may be putting your system at risk by doing so!
For more information see:
Hope this helps. Regards Tim...