Last updated on SEPTEMBER 24, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.1 and later
Information in this document applies to any platform.
***Checked for relevance on 12-Jun-2013***
Checked for relevance on 2-Apr-2015
By default, object auditing is enabled on the "/group/sharing" values within the PIN_FLD_MEMBERS array. We have some large "/group/sharing/discounts" groups (For example, 10,000 members).
Every time a member enters or leaves the group an audit object is created (/au_group/sharing/discounts). This results in an additional 10,000 rows in AU_GROUP_SHARING_MEMBERS_T.
This causes a big performance impact as it adds up to 10 seconds of additional time to account activations.
Is it safe to disable auditing on those fields?
Will it have any negative affects on other types of "/group/sharing" ("/group/sharing/charges", monitor, profiles, etc.) objects?
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