Audit for Custom Services
(Doc ID 1344080.1)
Last updated on SEPTEMBER 17, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
Is it necessary to turn on audit for all sub classes of /service? It is required audit to be on only for selected services and not all services. However, got errors due to not turning audit on for such custom classes.
Is it recommended by Oracle to do so? i.e to turn on audit for all sub classes of /service in 7.4?
Steps to Reproduce
Upgraded from Infranet 6.5 to BRM 7.4 using the OOB scripts. Post upgrade, trying to execute the basic opcodes like pcm_op_cust_modify_customer on upgraded custom services.
However, this fails giving an error saying that the au_<custom service> object does not exist. However, we do not want to maintain audit for such custom services either as this would lead to additional overhead of purging such data later and also hit performance.
However, understand from the below article that auditing must be turned on in the base /service class.
This will lead to additional storage of considerable amount of unwanted data as we are not using pipeline to rate them. Please suggest what needs to be done or is there any alternative for the same so as to keep auditing off for selected services?
Did read an article from Oracle support with below comment
"Due to design changes , from BRM (Oracle Communications Billing and Revenue Management) product Release 7.0 onwards, it is mandatory that every custom service/profile table and extended custom service/profile tables must have an associated audit table."
We understand from the above article that audit needs to be maintained for all services. Is it necessary to keep all the sub-classes of /service also auditable?
We expect the audit to be maintained only for selected services. Not all services.
When do not enable audit for sub classes of service, gets the below error (dm_oracle.pinlog):
By following the suggested approach (i.e. to turn on audit for all sub classes of /service) the error shown got resolved.
Question is, whether we actually need to introduce audit for all extensions of /service class? Isn't it possible to keep audit only for selected /service class extensions? Also, as introduction of complete auditing
will lead to considerable amount of data storage, what is recommended purge mechanism for the same?
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