Orphaned Record Created In S_DEDUP_RESULT Table When Deleting Data From Siebel Client > Administration - Data Quality > Duplicate Account or Duplicate Contact List View (Doc ID 2244502.1)

Last updated on MARCH 15, 2017

Applies to:

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

Symptoms

PRODUCT VERSIONS:
------------------------------
SIEBEL VERSION: Siebel 16.5 [IP2016]
SIEBEL APP O/S: Linux x86

ISSUE STATEMENT:
----------------------------

When deleting data through Siebel Client > Administration - Data Quality > Duplicate Accounts View, some records still remain in the S_DEDUP_RESULT table which are no longer displayed in the Siebel Client UI Duplicate Accounts View.

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

1. Create multiple Account records in Siebel Accounts view which are duplicates of each other.

2. Go to the Administration - Data Quality > Duplicate Accounts View > drill down into an account which has duplicates:

a. The bottom Possible Matches applet has 2 records:

1-RLEV Account 21-FEB-17 11.01.42 1-R1IP 1-R1IP 1-RLEU
1-RLEU Account 21-FEB-17 11.01.42 1-R171 1-R1IP 1-RLEU 93

However, there are no "Delete Record" menu option and CTRL+D does not allow to delete any records in this applet.

b. In the top applet, the "Delete Record" menu option is available. Use this menu option to delete the record. The record is removed from the UI and no longer displayed.

3. However, query for the records at the DB table level:

select ROW_ID, OBJ_NAME, CREATED, DUP_OBJ_ID, OBJ_ID, DEDUP_REQ_ID, TOT_SCORE_VAL from S_DEDUP_RESULT;

There are still records from the match earlier which is in the table but no longer shows up in the Siebel Client UI:

1-RLEU Account 21-FEB-17 11.01.42 1-R171 1-R1IP 1-RLEU 93

EXPECTED BEHAVIOR:
-------------------------------
The expected behaviour is that the UI deletion of the duplicates record would do a cascading delete of the driver record and all the records which are matches to it.

LOSS OF FUNCTIONALITY / BUSINESS IMPACT:
--------------------------------------------
Only the driver record is deleted but none of its matches are deleted. This results in data in the S_DEDUP_RESULT table not getting cleaned up properly and as a result, they are also not showing up on the Siebel Client UI, so it is misleading to the user as if the data was delete completely when infact it is not.

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