How To Verify if BufferLimit And StoreLimit Are Updated For Duplicate Check (Doc ID 858380.1)

Last updated on JUNE 22, 2017

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.2.1.0.0 and later
Information in this document applies to any platform.
***Checked for relevance on 07-Aug-2013***

Goal

Q1: After installing <patch 8540293> on Pipeline, when running a semaphore (set_dup_check_limit.reg as below) to update BufferLimit and StoreLimit for duplicate check, the older rows in table "ifw_duplicatecheck" are not deleted. Who deletes the older rows?

test01:/portal/7.2.1/ifw/semaphore> more set_dup_check_limit.reg
ifw.Pipelines.PRE_PROCESS.Functions.Standard.FunctionPool.DuplicateCheck.Module.BufferLimit = 20090609
ifw.Pipelines.PRE_PROCESS.Functions.Standard.FunctionPool.DuplicateCheck.Module.StoreLimit = 20090604



Q2: Is there a way to choose accounts to be loaded into the pipeline memory?



Q3: Is there a way to check the current BufferLimit and StoreLimit value to confirm if it's set
correctly?


Solution

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