My Oracle Support Banner

Oracle OCI7 Call Crashes With Sigsegv In Kpuhh.C in 11.1 and Higher (Doc ID 1097815.1)

Last updated on FEBRUARY 26, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 11.1.0.6 to 11.2.0.1.0 [Release 11.1 to 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
***Checked for relevance on 22nd Aug 2016***

Symptoms

An application written with OCI7 calls such as olog crashes when SEC_USER_AUDIT_ACTION_BANNER=/<path>/banner.txt  is set in the sqlnet.ora.
Sample OCI7 calls / code to reproduce the issue can be found in <Note 43956.1>, or if the Oracle examples are installed, in $ORACLE_HOME/rdbms/demo/cdemo3.c 

Stack generated from core file will contain below entry :

kpuhhalp, kpuadef, upiini, upiah0, upiahm, upilgni, upilgn, upilogc, upilog, ocilog, main 

Other possible errors are :

oci-24550 [11] [[si_signo=11] [si_errno=0] [si_code=1] [si_addr=c]] [] [] [] [] [] [] [] [] [] []

You may also see trace file with below entry 

Breaking the connection before proto/dty negotiation, error raised 3113

 

Changes

11g introduced few sqlnet parameters SEC_USER_UNAUTHORIZED_ACCESS_BANNER & SEC_USER_AUDIT_ACTION_BANNER to warn users against unauthorized access and possible auditing of user actions.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.