This content has been marked as final. Show 5 replies
This problem is quite often. While the ORA-600 error is "captured" as a handled exception in the Oracle source code, the ORA-7445 is an unhandled exception error due to an OS exception which should result in the creation of a core file. An ORA-7445 is a generic error, and can occur from anywhere in the Oracle code. The precise location of the error is identified by the core file and/or trace file it produces.
Whenever an ORA-7445 error is raised a core file is generated. There may be a trace file generated with the error as well.
Prior to 11g, the core files are located in the CORE_DUMP_DEST directory. Starting with 11g, there is a new advanced fault diagnosability infrastructure to manage trace data. Diagnostic files are written into a root directory for all diagnostic data called the ADR home. Core files at 11g will go to the ADR HOME/cdump directory.
Then visit My Oracle Support to access the ORA-00600 Lookup tool. The ORA-600/ORA-7445 Lookup tool may lead you to applicable content in My Oracle Support on the problem and can be used to investigate the problem with argument data from the error message or you can pull out key stack pointers from the associated trace file to match up against known bugs.
Don't try to fix it by yourself!
just adding in what kirill wrote:
Here is the note he is talking about. Just look after it on metalink.
*ORA-600/ORA-7445 Error Look-up Tool [ID 153788.1]*
So. what I can do ignore it or generate SR. If it is not critical then i ignore it.
Pls suggest me.
You just need to install a patch p5648872 (if you use metalink) or p5648872_10203_linux (if you use linux). You also can empty shared pool (that has lead to this error) or reboot it. Better use first solution.
If you have any questions, write me.