Last updated on APRIL 12, 2016
Applies to:Siebel Campaign Management - Version 18.104.22.168 [IP2013] and later
Information in this document applies to any platform.
Siebel 22.214.171.124 integrated with OBIEE 126.96.36.199.11
When using Update Count on Segment Trees within OBIEE to create the cache in OBIEE, Campaign Load is not using this cache but recreating another one. This causes the Campaign Load process to be slow.
Expected behavior is that the Campaign Load process should use the update count cache that was created in obiee.
Steps to reproduce:
1. Perform Update Count for a segment tree in OBIEE, so that the cache is created.
2. Create a campaign, and load the campaign.
It was observed that it is taking a long time during the first campaign load. It is not using the cache that was created in OBIEE when performing update Count for the segment trees. If you run Campaign Load again, then it is using the cache and much faster.
This was working previously in 7.8.x and users are expecting the same behavior in 8.1.x since this was the process they were using previously.
Addition Notes :
The updateCount, Campaign load job all are taking long time for the first time. they are expecting the jobs to be leveraging the same cache saved for the Segment or Segment tree.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms