Last updated on MARCH 02, 2017
Applies to:Siebel Campaigns - Version 188.8.131.52  and later
Siebel Marketing - Version 184.108.40.206  and later
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 220.127.116.11 
Database: Oracle 18.104.22.168
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: HP 9000 Series HP-UX
***Checked for relevance on 02-Set-2013***
This document was previously published as Siebel SR 38-3450727901.
We are currently using the caching functionality for Siebel Marketing Segmentation to improve system performance. We have the default cache expiration time set to 24 hours. Our understanding is that when segmentation results are cached they are written to the M_C_CONTACT table in the warehouse. After 24 hours, the results expire and the Siebel server runs a SQL script to delete the cached records from M_C_CONTACT.
We have found that this delete process does not work consistently. Even though cache records are expired, they are not always deleted from M_C_CONTACT. This table continues to grow and eventually becomes a perormance bottleneck because the cache table gets so large. We've implemented a workaround where we truncate M_C_CONTACT manually once per week to alleviate the issue. My question is why aren't expired cache records consistently deleted from M_C_CONTACT?
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