After Applying TT Table Fix, Performance Degradation Is Observed.

(Doc ID 2310403.1)

Last updated on SEPTEMBER 25, 2017

Applies to:

Siebel Marketing - Version 8.1.1.14.11 [IP2014] and later
Information in this document applies to any platform.

Symptoms

Note: This behavior is only seen depending on the Segment Design and RPD Configuration

After temporary fix (Bug 25036624) has been installed to fix the issue where TT tables (Persistent Pool) were created but NOT used by BI Server (Persistent Pool TT table not used in all subqueries (Doc ID 2281910.1)), then it is observed a huge performance degradation. From minutes to hours.


For a Segment like:

- “SEGMENT_TEST_SUBQUERY_OLAP_OLTP_KJ11” – Start: 01/06/2017 1:36:05 AM – End: 01/06/2017 4:39:45 AM
- Filters:

Start with “Last Name begins with B”
Keep 1: "Marketing Segmentation Assets"."Consumer"."Consumer Row ID" IN (SELECT "Siebel Campaign History"."Contact Id" from "Marketing Segmentation Targets" where "Siebel Campaign History"."Campaign Id" = '1-1JO3D3N')
Keep 2: "Marketing Segmentation Assets"."Consumer"."Consumer Row ID" IN (SELECT "Siebel Campaign History"."Contact Id" from "Marketing Segmentation Targets" where "Siebel Campaign History"."Campaign Id" <> '1-1JO3D3N_2')
Keep 3: "Marketing Segmentation Assets"."Consumer"."Consumer Row ID" IN (SELECT "Siebel Campaign History"."Contact Id" from "Marketing Segmentation Targets" where "Siebel Campaign History"."Campaign Id" <> '1-1JO3D3N_3')
Keep 4: "Marketing Segmentation Assets"."Consumer"."Consumer Row ID" IN (SELECT "Siebel Campaign History"."Contact Id" from "Marketing Segmentation Targets" where "Siebel Campaign History"."Campaign Id" <> '1-1JO3D3N_4')

- The following repeatedly queries were seen when running Update Counts:

 

 

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