Error SBL-APS-00118 When Adding Contact/Account Record in Siebel in Conjunction with Oracle Enterprise Data Quality (EDQ) 9.0.x (Doc ID 1479176.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel CRM Call Center - Version 8.1.1.4 SIA [21225] and later
Information in this document applies to any platform.

Symptoms

Siebel 8.1.1.7 (with ACRs 437 and 475) is being used along with Oracle Enterprise Data Quality (EDQ) 9.0.3 on RedHat Linux 5.7 (Tikanga).

When attempting to create a new Account record or update an existing one the following error occurs.

ERROR
-----------------------
SBL-APS-00118: Data Quality vendor-specific error: An error occurred when calling function 'sdq_init_connector ()' in connector '': "(-3) VM not found." Detailed error message: VM shared library could not be loaded.

There is an existing EDQ defect "DIR-13535: The Siebel Connector needs to support Oracle Linux 5 as well as 6."
Issue: The Siebel Connector was compiled on Oracle Linux 6, and therefore the shared libraries do not load on Oracle Linux 5.
Fix: The shared libraries have been recompiled, and therefore now work on Oracle Linux 5 and 6.

However, even after updating both EDQ and the Siebel Connector to version 9.0.4 the same error is still seen.

In order to enable Siebel Connector logging for EDQ the following two lines need to be added to the dnd.parms file:

logfile: sdq%05d.log
jlogfile: jsdq%05d.log

After adding this and reproducing the issue the following is seen in the Siebel Connector log:

sdq15667.log
15667: sdq_init_connector /mnt/disk07/apps/siebel/siebsrvr/SDQConnector/
15667: no libjvm loadable from /usr/java/jdk1.6.0_31/jre/lib/amd64/server/libjvm.so
15667: sdq_get_error_message -3

As per the EDQ Certification Matrix a 32 bit JDK needs to be used instead of a 64 bit version.

However, when using Oracle JDK 1.6.0_24 (32 bit) a crash is seen with the following call stack:

PROCESS 11585 CRASHED AFTER RECEIVING SIGNAL 11 IN THREAD 2893650832!!!

Called from:
/mnt/disk07/apps/siebel/siebsrvr/lib/libsslcosd.so[0x558dd951]
/mnt/disk07/apps/java/jdk1.6.0_24/jre/lib/i386/server/libjvm.so[0x669bf446]
/mnt/disk07/apps/java/jdk1.6.0_24/jre/lib/i386/server/libjvm.so[0x669bc203]
/mnt/disk07/apps/java/jdk1.6.0_24/jre/lib/i386/server/libjvm.so(JVM_handle_linux_signal+0x188)[0x669c0148]
/mnt/disk07/apps/java/jdk1.6.0_24/jre/lib/i386/server/libjvm.so[0x669bc124]
[0x55555410]
/mnt/disk07/apps/java/jdk1.6.0_24/jre/lib/i386/server/libjvm.so[0x669a8801]
/mnt/disk07/apps/java/jdk1.6.0_24/jre/lib/i386/server/libjvm.so[0x669f4d29]
/mnt/disk07/apps/java/jdk1.6.0_24/jre/lib/i386/server/libjvm.so[0x669f467f]
/mnt/disk07/apps/java/jdk1.6.0_24/jre/lib/i386/server/libjvm.so[0x669f40c2]
/mnt/disk07/apps/java/jdk1.6.0_24/jre/lib/i386/server/libjvm.so[0x666a73c0]
/mnt/disk07/apps/java/jdk1.6.0_24/jre/lib/i386/server/libjvm.so[0x666a4547]
/mnt/disk07/apps/java/jdk1.6.0_24/jre/lib/i386/server/libjvm.so[0x66631d6f]
/mnt/disk07/apps/java/jdk1.6.0_24/jre/lib/i386/server/libjvm.so[0x666ad73e]
/mnt/disk07/apps/java/jdk1.6.0_24/jre/lib/i386/server/libjvm.so[0x666acfb1]
/mnt/disk07/apps/java/jdk1.6.0_24/jre/lib/i386/server/libjvm.so[0x66ac4dd6]
/mnt/disk07/apps/java/jdk1.6.0_24/jre/lib/i386/server/libjvm.so[0x66abe04f]
/mnt/disk07/apps/java/jdk1.6.0_24/jre/lib/i386/server/libjvm.so[0x669bea6e]
/lib/libpthread.so.0[0x4dd85832]
/lib/libc.so.6(clone+0x5e)[0x4dcf04de]

 
The new EDQ Connector log shows that the failure is no longer in the sdq_init_connector function but in the sdq_set_global_parameter one instead:

sdq11585.log
11585: sdq_init_connector /mnt/disk07/apps/siebel/siebsrvr/SDQConnector/
11585: sdq_set_global_parameter <?xml version="1.0" encoding="UTF-8"?><?Siebel-Property-Set EscapeNames="true"?><Data></Data>

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