Skip to Main Content
Forums

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

OCI-21500: internal error code, arguments: [17177], [0x000000000], [], [], [], [], [], []

AkpatseJun 29 2015 — edited Jun 30 2015

Hi,

I have a multi-threaded application configured such that each thread has it's own database connection. When the threads are spawned and they try to connect to oracle, I get the errors below and then a Segmentation fault (core dumped).

OCI-21500: internal error code, arguments: [17177], [0x000000000], [], [], [], [], [], []

`▒▒`▒▒`▒▒`▒▒`▒▒`▒▒`▒▒`▒▒ORA-24550: signal received: [si_signo=11] [si_errno=0] [si_code=2] [si_int=-1023562872] [si_ptr=0x7f61c2fdab88] [si_addr=0x7f61c33a2e32]

Has anyone encountered this before?

Additional Information:

  • Each thread connects to the database using  Pro*C "exec connect" with it's own runtime context  (I also enabled threads before the threads were created)
  • Each thread also opens an OCI session from the Pro*C connection using SQLEnvGet()
    • I get the same error if I open OCI session using OCIEnvNlsCreate( (...., OCI_THREADED|OCI_OBJECT, ......)

Note: I know someone will wonder why using both Pro*C and OCI at the same time. This is old code that we are making multi-thread to handle increased customers. The old code uses both Pro*C and OCI and it's over 1M lines of code

          so it's not an option now to use just one i.e.  ProC or OCI.

Thanks

Richard

Comments

Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Jul 28 2015
Added on Jun 29 2015
#database-and-application-migrations
1 comment
2,013 views