ITPub博客

首页 > Linux操作系统 > Linux操作系统 > ORA-24550 Signal Received Error的解决方法

ORA-24550 Signal Received Error的解决方法

原创 Linux操作系统 作者:xccheese 时间:2012-02-21 09:49:49 0 删除 编辑
ORA-24550: signal received: [si_signo=11] [si_errno=0] [si_code=2] [si_addr=00000000]

----- Call Stack Trace -----
calling              call     entry                argument values in hex     
location             type     point                (? means dubious value)    
-------------------- -------- -------------------- ----------------------------
kpedbg_dmp_stack()+  call     kgdsdst()+880        7FFEA620 ? 0 ? 777AEF68 ?
368                                                716 ? D32895E0 ? FFFF8209 ?
                                                   18 ? 7FFCA6B4 ?
kpeDbgCrash()+160    call     kpedbg_dmp_stack()+  0 ? 0 ? 777AEF68 ? 610 ?
                              368                 
kpeDbgSignalHandler  call     kpeDbgCrash()+160    0 ? 5 ? D0CF21D0 ? 2 ? 4 ?
()+256                                             39 ? 4 ? 7FFEE208 ?
skgesig_sigactionHa  call     kpeDbgSignalHandler  7FFEDE00 ? 792 ? 777AEF68 ?
ndler()+480                   ()+256              
304ff420             call     skgesig_sigactionHa  7FFEE60C ? 7FFEE610 ? 187 ?
                              ndler()+480          777AEF68 ?
_etext_f()+3256976   call     304ff420             7FFEE800 ? B ? 7FFEE610 ? 0 ?
                                                   0 ? 0 ? 0 ? 0 ?
_etext_f()+1580752   call     _etext_f()+3256976   1401E50 ? 1402804 ? 139F9BC ?
                                                   20D5 ? 7FFF44E4 ? 141CB60 ?
                                                   7FFF5A20 ? 0 ?
_etext_f()+1556224   call     _etext_f()+1580752   7FFF5A20 ? 139D5F0 ? 44A1 ?
                                                   7FFF4B38 ? 6 ? 7FFF4B24 ?
                                                   7FFF4B28 ? 1BBF ?
_etext_f()+1406464   call     _etext_f()+1556224   7FFF4B24 ? 52 ? 6 ? 15B3 ?
                                                   157860 ? 8E49 ? 7FFF4B20 ?
                                                   7FFF4B28 ?
main_opd_entry()+80  call     _etext_f()+1406464   4352A8 ? 4352A0 ? 4 ?
                                                   C00427C0 ?

----- End of Call Stack Trace -----
 
 
 
 
In this Document
Symptoms
Changes
Cause
Solution
References

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.

Applies to:
Oracle Server - Enterprise Edition - Version: 11.2.0.1 and later [Release: 11.2 and later ]
Information in this document applies to any platform.
OCI, OCCI, Precompiler based Applications such as Pro*C, Pro*COBOL.
Symptoms
When trying to execute C program on Server - Oracle 11g 11.2.0.1 on IBM AIX 64 bit, 6.1, the following error message is received.

Application connects to Server with Oracle 11g 11.2.0.1:

ORA-24550 : signal received : [si_signo=11] [si_errno=0] [si_code=50] [si_adr = 2020202020202020] killed

Depending on the Operating System the stack would differ. For example;

Linux x86-64 would be something like;

/lib64/libpthread.so.0[0x3412a0673d] /lib64/libc.so.6(clone+0x6d)[0x3411ed44bd] ORA-24550: signal received: [si_signo=6] [si_errno=0] [si_code=-6] [si_int=0] [si_ptr=0x200000000] [si_addr=0x1f400001c43] kpedbg_dmp_stack()+314<-kpeDbgCrash()+166<-kpeDbgSignalHandler()+158<-skgesig_sigactionHandler()+217<-__restore_rt()<-gsignal()+53<-000000000DE723A0<-000000000DE723A0<...

Changes
Upgraded Database from Oracle 10g 10.2.0.1 to Oracle 11g 11.2.0.1
Cause
Diagnosability features which are turned on by default on Oracle 11g Release 2 causes the problem.

Parameters are:

DIAG_ADR_ENABLED
DIAG_SIGHANDLER_ENABLED
DIAG_DDE_ENABLED
Solution
1. Such errors can occur if the "Diagnosability" features are 'ON'.

To turn off the OCI signal handler and re-enable standard Operating System failure processing, place the following parameter setting in sqlnet.ora:

DIAG_SIGHANDLER_ENABLED=FALSE

By default this parameter is set to true.

If you want to see the old behavior. you can simply turn off the feature by placing the following parameter setting in your client side sqlnet.ora file under $ORACLE_HOME/network/admin directory.

2. In addition, please turn off other Diagnostics parameters as well by placing the following entries in the client side or server sqlnet.ora file. i.e., from where the application is run.

DIAG_ADR_ENABLED=OFF
DIAG_SIGHANDLER_ENABLED=FALSE
DIAG_DDE_ENABLED=FALSE

References
BUG:9342118 - OCISTMTRELEASE CRASHES WITH CORE DUMP WHEN CALLED OUTSIDE A TRANSACTION
NOTE:1062759.1 - ORA-24550 AND CRASH IN OCISTMTRELEASE after client upgrade to ORACLE 11.2

显示相关信息 相关的
产品

Oracle Database Products > Oracle Database > Oracle Database > Oracle Server - Enterprise Edition

来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/25148509/viewspace-716838/,如需转载,请注明出处,否则将追究法律责任。

下一篇: RMAN异机恢复总结
请登录后发表评论 登录
全部评论

注册时间:2010-12-27

  • 博文量
    14
  • 访问量
    52031