ORA-07445

ORA-07445篇

以下是Maclean Liu工作中遇到过的一些Oracle ORA-07445错误的解决经验:



Oracle内部错误:ORA-07445[kcflfi()+466] [INT_DIVIDE_BY_ZERO]一例

ORA-07445: [__lwp_kill()+8] [SIGIOT]错误一例

Oracle内部错误ORA-07445:[_memcmp()+88] [SIGSEGV]一例

Oracle内部错误ORA-07445[kpopfr()+339] [SIGFPE]一例

ORA-07445:[SIGFPE] [Integer divide by zero]内部错误一例

Oracle内部错误ORA-07445: [ACCESS_VIOLATION] [unable_to_trans_pc][UNABLE_TO_READ]

ORA-07445 [SIGBUS] [Object specific hardware error]错误一例

PMON: TERMINATING INSTANCE DUE TO ERROR 600 on 8i

ora-7445 [kghalp+0500] [SIGSEGV]错误

 

 

ORA-7445 是与ORA-600齐名的著名Oracle错误,同ORA-600比较起来ORA-7445更多地由操作系统OS的异常或者bug引起。以下是ORA-7445的一些官方解释:

 

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.

As the ORA-7445 error indicates an unhandled exception in the Oracle source code, your search in the Oracle Knowledge Base will need to focus on the stack data from the core file or the trace file.

关注dbDao.com的新浪微博

扫码关注dbDao.com 微信公众号:

Speak Your Mind

TEL/電話+86 13764045638
Email service@parnassusdata.com
QQ 47079569