Siebel Application Object Manager with LDAP crashes on ldap_init on Solaris (Doc ID 1953337.1)

Last updated on SEPTEMBER 26, 2016

Applies to:

Siebel CRM - Version 8.1.1 [21112] and later
Information in this document applies to any platform.

Symptoms

On : 8.1.1 [21112] version, Security / Authentication

When attempting to access Siebel application with Oracle LDAP client on Solaris platform, Application Object Manager (AOM) process crashes and FDR file is generated and the following error occurs in call stack:

ERROR
-----------------------
PROCESS 8170 CRASHED AFTER RECEIVING SIGNAL 4 IN THREAD 16!!!
Current Time: 12/03/2014 15:09:15.418

Called from:
/sb8app/ses/siebsrvr/lib/libsslcosd.so'0x4ba40 [0xfe70ba40]
/lib/libc.so.1'__sighndlr+0xc [0xf2875b90]
/lib/libc.so.1'call_user_handler+0x370 [0xf2868f80]
/lib/libc.so.1'sigacthandler+0x58 [0xf2869288]
/sb8app/ses/siebsrvr/mw/lib/libmwsafe.so'B_CreateAlgorithmObject+0x0 [0xfd72ab38] [Signal 4 (ILL)]
/sb8app/Oracle_LDAP_Client/product/11.2.0/dbhome_1/lib/libnnz11.so'nzty1as_algstart+0x150 [0xf6ac9bc0]
/sb8app/Oracle_LDAP_Client/product/11.2.0/dbhome_1/lib/libnnz11.so'0x4b588 [0xf6acb588]
/sb8app/Oracle_LDAP_Client/product/11.2.0/dbhome_1/lib/libnnz11.so'0x4b0d0 [0xf6acb0d0]


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Setup Siebel application for LDAP
2. Setup Oracle LDAP Client and make sure that it is installed correctly
3. Check to see if LDAP initialization happens and whether AOM is accessible and does not crash

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot access Siebel with LDAP on Solaris and this was causing a setback.

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms