Purging Of Old Events Before Upgrade Cut
(Doc ID 790946.1)
Last updated on MARCH 22, 2019
Applies to:
Oracle Communications Billing and Revenue Management - Version 6.2.0.0.0 and laterInformation in this document applies to any platform.
Goal
Currently the user have135 million events with over 80 items representing 11 million bills and related invoices. The top event types in database equates to over 100 million of these events and include the following:
19,037,887 /event/billing/item/transfer
16,856,177 /event/session/dialup
16,475,388 /event/billing/adjustment/item
11,644,776 /event/billing/cycle/tax
8,671,513 /event/billing/product/fee/cycle/cycle_forward_monthly
6,775,714 /event/session
6,476,799 /event/billing/cycle/fold
This includes data from over 8 years of running in production. Is there any harm in deleting the oldest say 6 years of this data and leaving only 2 years online? This would remove a lot of unnecessary disk space and ensure the upgrade scripts complete in a reasonable time frame.
Ideally the user was thinking a purge process to select the oldest bills, then from the bills find the items and using the items find the event associations and purge the events, then purge the items and related bills, and finally purge the invoice object which have been archived.
Please advise if safe to follow these procedures and if supported. Do you see anything here that could cause problems?
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 |