Patch Number 18791499 for Siebel Connector 9.0.7 with EDQ 11.1.1.7.4 generates error during matching - dedupRealtime failsafe fallback after: web service request failed with code 500 (Internal Server Error) (Doc ID 1907425.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel Data Quality - Version 8.1.1.10 [23021] and later
Information in this document applies to any platform.

Symptoms

SIEBEL VERSION:
---------------
Siebel 8.1.1.10

ISSUE STATEMENT:
----------------
Customer encountered a product defect with Siebel Connector 9.0.6 on AIX platform where it was truncating all data after the & character. To fix this, customer applied Patch Number 18791499 (Siebel Connector 9.0.7) with EDQ 9.0.8 and it has fixed the & character issue.

Now, customer has upgraded to EDQ 11.1.1.7.4 version and also trying to use the same Patch Number 18791499 (Siebel Connector 9.0.7). However, with this combination, when Siebel application sends a request to EDQ for matching data/deduplication, the record is not deduplicated and the request fails with the following error:

INFO: 03-Jul-2014 16:10:09: dedupRealtime failsafe fallback after: web service request failed with code 500 (Internal Server Error) (code 234,309)

Address cleansing is working however.

WHERE IT HAPPENED:
-------------------------------
The issue happens in customer's test environment.

STEPS TO REPRODUCE:
-------------------------------
The behaviour occurs as follows:

1. Setup Siebel Application SIA 8.1.1.10 version + EDQ 11.1.1.7.4 + Siebel Connector 9.0.7
2. Use Siebel UI to create a new account record which sends a request to EDQ for matching. This request fails and returns the reported error.

BEHAVIOR PATTERN:
-------------------------------
The behavior is consistently reproducible each time and happens only when deduplication is invoked.

EXPECTED BEHAVIOR:
-------------------------------
The expected behaviour is that record should be cleansed and match invoked without any error.

WHAT IS WORKING:
------------------------------
The cleansing feature is working, the record gets cleansed properly.

LOSS OF FUNCTIONALITY / BUSINESS IMPACT:
------------------------------
Due to the web service error, the record is not being matched and thus generating a lot of duplicate data.

ERROR MESSAGE:
-------------------
The error message that occurs with this issue is:

INFO: 03-Jul-2014 16:10:09: dedupRealtime failsafe fallback after: web service request failed with code 500 (Internal Server Error) (code 234,309)

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