"Dedup Token" Field causes performance issue

(Doc ID 1995129.1)

Last updated on MARCH 02, 2017

Applies to:

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


On : [IP2013] version, Client Functionality

Siebel is integrated with OEDQ for Deduplication.

Dedup Token Field in Contact BC is set to Force Active. Setting this field force active would unnecessarily include S_DQ_CON_KEY table in SQL where ever Contact BC is referenced.

This is causing performance issues.

Is there any reason why Dedup Token field set to Force Active? Can we set to Force Active Property to False?

Customer expects that DeDup Token is not force activated whenever Contact BC is referenced.

The issue can be reproduced at will with the following steps:
1. Configure and enable Siebel/EDQ integration
2. Make any update to a Contact BC record.

The issue has the following business impact:
Due to this issue, users cannot have a good performance when maintaining Contacts.


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