Records Are Not Getting Deleted Automatically From M_C_CONTACT (Doc ID 1532785.1)

Last updated on NOVEMBER 09, 2014

Applies to:

Siebel Marketing - Version 8.1.1 SIA [21111] and later
Information in this document applies to any platform.

Symptoms

On : 8.1.1.5 SIA [21229] version, Siebel Marketing, Oracle Business Intelligence 10.1.3.4.1 (Build 090414.1900)

The cache table M_C_CONTACT has grown very large. As a temporary workaround the customer has implemented the workaround in Document 1489958.1 - "11g Records Not Getting Deleted From Siebel Marketing M_C_CONTACT Table" namely:

Create a .bat file (windows) or a cron job (UNIX) that is scheduled to run around midnight each day and that includes the following steps:
1) Make sure no segments are running
2) Stop OBI presentation services
3) Truncate M_C_CONTACT
4) Use catalog manager to delete all cache files from \root\system\mktgcache\\ folder except sawguidstate
5) Restart OBI presentation service

According to the NQQuery.log there are many instances of:

DELETE FROM M_C_CONTACT WHERE GUID = '5340b5b9-0c40-1000-8029-0a2401140000'

In the sawlog.log file we see:

ERROR
-----------------------
Type: Error
Severity: 40
Time: Mon Oct 29 12:58:02 2012
File: project/webmarketing/cachemgr.cpp Line: 203
Properties: ThreadID-4984
Location:
saw.sqlNodeCacheMgr.cleanExpired
saw.taskScheduler.processJob
saw.threadPool
saw.threads

***kmsgErrorInDeletingCache: message text not found ***
Path not found (/system/mktgcache/PROCRMWEB41/5340b5b9-0c40-1000-8029-0a2401140000)
---------------------------------------
Type: Error
Severity: 40
Time: Mon Oct 29 12:58:02 2012
File: project/webthreads/webscheduler.cpp Line: 262
Properties: ThreadID-4984
Location:
saw.taskScheduler.processJob
saw.threadPool
saw.threads

Running job 'CleanupSqlCache' took 381640 milliseconds, 127.2% of job's frequency (300 seconds).

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Use Siebel Marketing with OBI for Segmentation
2. Run Segment jobs like Update Counts and cache results
3. Check back and redo jobs (e.g. after 24 hours).
4. Cache should be purged, but it remains in both the web catalog and M_C_CONTACT table.

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