Is there a tool to troubleshoot ORA-00600 and ORA-07445 errors?
February 27th, 2006 By Fahd Mirza
ORA-00600 and ORA-07445 errors are the most esoteric erros in Oracle.
There is a tool called “ORA-600/ORA-7445 Troubleshooter” available at Metalink. It asks for the first argument of ORA-600 error with an optional database version number.
For example, to see the description of the error:
ORA-00600: internal error code, arguments: [723], [25908], [25908], [memory leak]
You enter 723 in the “ORA-600 First Argument” field. The first argument is a pointer to where in the code the error was caught and thus is the key information in identifying the problem.
You can also embed (copy/paste) the “Call Stack Trace” there, and, when you click on the “Search Call Stack” button an advanced MetaLink search is performed to find documents containing relevant sections from the call stack.
Call Stack extracts from the following files are supported:
- Generic foreground and background server trace files located in background_dump_dest and user_dump_dest
- OpenVMS NETV2 and BEQ log files located in ORA_ROOT:[NETWORK.LOG]
- WINDOWS CORE.LOG files
- GDB (debugger) backtrace call stacks (best endeavors)

February 28th, 2006 at 11:47 pm
Great!
Karl
March 3rd, 2006 at 3:58 am
Hi Karl,
This was some interesting reading I found the other day. Don’t know how it compares to the metalink tool, but I found this very informative. http://www.orafaq.com/papers/oradebug.pdf
Chris
March 5th, 2006 at 10:25 am
Wow Chris this tool goes very deep. It remembers me on teh time i used the AIX debugger to attach to any running process on the machine and step thru.
Greetings
Karl
March 27th, 2006 at 9:46 am
I am glad i came accross this page to learn about these two tools, the ora troublershooter just allowed me to know about a bug in Oracle 10g PQ servers
Ammar Sajdi
http://www.e-ammar.com