Is It OK To Stop Auditing Of /account Class ?
Last updated on MAY 13, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 7.5.0]
Information in this document applies to any platform.
On : BRM 18.104.22.168.0 version,
Customer is looking into turning off auditing of the /account class and purge the au_account_t table.
Currently only these two fields PIN_FLD_BAL_GRP_OBJ and PIN_FLD_OBJECT_CACHE_TYPE are being audited as per default setting for BRM 7.5.
Customer is using only one one balance group per account.
We also see the au_account_t table being accessed by several jobs like pin_collect and pin_deposit using the following query:
select min( au_account_t.effective_t ) from au_account_t where au_account_t.au_parent_obj_ID0 = :1
Please confirm whether we need not audit these fields in the /account class and if not, can we purge records from the existing au_account_t table?
Are there any possible side effects?.
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