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

Last updated on MARCH 20, 2023

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.2.1.0.0 and later
Information in this document applies to any platform.

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?

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

	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

Goal

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.

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

Applies to:

Goal

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!