Siebel Application Object Manager with LDAP crashes on ldap_init on Solaris
Last updated on SEPTEMBER 26, 2016
Applies to:Siebel CRM - Version 8.1.1  and later
Information in this document applies to any platform.
On : 8.1.1  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:
PROCESS 8170 CRASHED AFTER RECEIVING SIGNAL 4 IN THREAD 16!!!
Current Time: 12/03/2014 15:09:15.418
/sb8app/ses/siebsrvr/mw/lib/libmwsafe.so'B_CreateAlgorithmObject+0x0 [0xfd72ab38] [Signal 4 (ILL)]
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
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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms