My Oracle Support Banner

Siebel Data Cleansing using Trillium DQ is exhibiting memory leak behavior that leads to eventual memory exhausting on the component and crashing the Siebel server component (Doc ID 1678650.1)

Last updated on FEBRUARY 04, 2019

Applies to:

Siebel CRM Call Center - Version 8.1.1.11 [IP2013] and later
Information in this document applies to any platform.

Symptoms

On : 8.1.1.11 SIA [23030] version, Siebel EAI

ACTUAL BEHAVIOR
---------------
MQ Series Receiver component is experiencing a memory leak when executing a workflow process that invokes Siebel DQ Cleansing.

The same memory leak behaviour can also be observed when doing batch cleansing using the Siebel DQMgr component and Operation DataCleansing.

For this particular issue, the customer was using Trillium DQ with Siebel application.

EXPECTED BEHAVIOR
-----------------------
memory should be released / re used.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1.  Run a DQMgr task for Contact object and Operation type DataCleansing, the memory usage goes quickly to 1 GB

2.  Run another DQMgr task again for same object and operation, memory usage goes quickly to 1.7GB

3.  Continue to run subsequent DQMgr task for same object and operation, memory eventually climbs over 2 GB and exceeds the process limit on the OS and crashes the component pid

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users have to restart the component periodically to free up memory or experience crashes.

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!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.