Troubleshooting the dreaded "ORA-07445" and "ORA-00600" errors

ORA-07445 and ORA-00600 core dump errors are very generic and it does not give users any specific error message. It becomes the task of a DBA to find out the cause and the solution of the error.The million dollar question is how to find the cause of the error? There are no direct messages printed on the screen to start with.

In such case, we start with alert_SID.log file. Every ORA-07445 and ORA-00600 errors will get recorded in the alert_SID.log file with proper time and related trace file information.

We will use the information in trace file to find out the actual cause of the error and the solution through metalink. Metalink provides a very useful "ORA-600/ORA-7445 Troubleshooter tool (Metalink Note:153788.1)"

Login into the Metalink account and search for doc id "153788.1" in the Quick find search bar and open the document. Now navigate to the error in alert_SID.log file and find the related trace file from UDUMP directory.

There are 2 ways to lookup the error:

1. Lookup by code

a. Select the correct Error code (ORA-00600 or ORA-07445)

b. Provide the first argument or failing function

c. Select the appropriate database version

d. Click Lookup Error button

2. Search Call Stack

a. Select the correct Error code (ORA-00600 or ORA-07445)

b. Select the appropriate database version

c. Enter the Call Stack info in the "Search Call Stack box"

d. Click Search Call Stack button

Metalink will search it's database and will show all the possibilities that can cause the problem and also it's solutions. In case the error is not in the metalink database, they make a note of this new error too.

This tool plays important role in identifying bugs in the database.

Aalap Sharma :)