My Oracle Support Banner

Orphaned Records In CS_INCIDENT_LINKS_EXT After Service Request Data Purge (Doc ID 2397653.1)

Last updated on MAY 12, 2018

Applies to:

Oracle Teleservice - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

In 12.1.3

Orphaned records in cs_incident_links_ext still exist after running concurrent request 'Service request data purge' (CSSRPGP).
Service Request Purge program not purging records in cs_incident_links_ext table even though Service Requests are purged.


SELECT
 COUNT(*)
FROM
 cs_incident_links_ext ext
WHERE
 NOT EXISTS (
  SELECT
  NULL
  FROM
  cs_incidents_all_b inc
  WHERE
  inc.incident_id = ext.from_incident_id );

From the ETRM, it states that this table shouldn't even be in use after 11.5.9, however it is getting populated.
Can development provide a script to purge records on cs_incident_links_ext?

Changes

 

Cause

To view full details, 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 a vibrant support community of peers and Oracle experts.