My Oracle Support Banner

Event_t Table Quickly Consuming Too Much Storage in the Database (Doc ID 2973695.1)

Last updated on SEPTEMBER 19, 2023

Applies to:

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


One user has a cloud-native Billing and Revenue Management (BRM) installation where they need to use session-event logging for auditing purposes. In this case, mainly they need to audit Billing Care (BC) and Billing Care Web Service (BCWS) accesses. They use the storable class “/user_activity” to obtain such information. However, they noticed that the “event_t” table is quickly consuming a lot of storage in the database, as all sessions are constantly stored.

The user is aware of the option to turn off Session-Event Logging via the “login_audit” entry, but they understand that this would make the BC and BCWS auditing process unfeasible.


Questions and Answers

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
Questions and Answers
 Is there any way to disable the session storage of the “BRM Server” modules but keep the session storage of Billing Care and BCWS?
 Is there any Oracle recommendation on how to save database storage? 
 Would turn off Session-Event Logging via the “login_audit” entry make the BC and BCWS auditing process unfeasible?

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.