The day before yesterday when the application was tested, it was said that the Application encountered the ORA-24550: signalreceived: [si_signo6] [si_errno0] [si_code9] [si_addr0] error, Go
The day before yesterday when the application was tested, it was said that the Application encountered the ORA-24550: signal wrong ED: [si_signo = 6] [si_errno = 0] [si_code = 9] [si_addr = 0] error, Go
Application error with ORA-24550: signal marshed: [si_signo = 6] [si_errno = 0] [si_code = 9] [si_addr = 0]
The day before yesterday when the application was tested, it was said that the Application encountered an error of ORA-24550: signal inclued: [si_signo = 6] [si_errno = 0] [si_code = 9] [si_addr = 0 ,, google, the solution is on the Server side or Client side sqlnet. add the following content to the ora file:
DIAG_ADR_ENABLED = FALSE
DIAG_SIGHANDLER_EANABLED = FALSE
DIAG_DDE_ENABLED = FALSE
Then restart the listener. I use the Oracle 11g rac environment and scan, so I need to restart listener and scan_listener.One nodeRun the command!
[Rac11g2 @ root] # srvctl stop listener
[Rac11g2 @ root] # srvctl stop scan_listener
[Rac11g2 @ root] # srvctl start listener
[Rac11g2 @ root] # srvctl start scan_listener
Attach the official documents on MOS:
ORA-24550 Signal passed ed Error From Client Based Application [ID 1284564.1]
Modification time 01-JUL-2011 type PROBLEM status MODERATED
In this Document
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:
Oracle Server-Enterprise Edition-Version: 11.2.0.1And 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 wrongly ed.
Application connects to Server with Oracle 11g 11.2.0.1:
ORA-24550: signal encoded ED: [si_signo = 11] [si_errno = 0] [si_code = 50] [si_adr = 2020202020202020] killed
Depending on the Operating System the stack wocould differ. For example;
Linux x86-64 wocould be something like;
/Lib64/libpthread. so.0 [0x3412a0673d]/lib64/libc. so.6 (clone + 0x6d) [0x3411ed44bd] ORA-24550: signal encoded Ed: [si_signo = 6] [si_errno = 0] [si_code =-6] [si_int = 0] [si_ptr = 0x200000000] [si_addr = 0x1f400001c43] kpedbg_dmp_stack () + 314 <-kpedb0000ash () + 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
Bugs: 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