Modifying Partitions On /event, /item And /journal Classes With Monthly Tablespace Name
(Doc ID 2453371.1)
Last updated on AUGUST 10, 2023
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.5.0.18.0 and laterInformation in this document applies to any platform.
Purpose
On 7.5PS18, with ECE as rating engine, user wants to have the data for each month to be in respective monthly tablespaces.
As a best practice, one should not be maintaining single tablespace for all data and index because it would lead to severe space management issues later. Hence, partitions should be distributed in respective monthly Tablespaces.
Following queries are raised with respect to this scenario.
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
| Purpose |
| Questions and Answers |
| How to modify existing table/indexes partitioned for monthly tablespace names ? Are these partitions required for /event, /item and /journal objects ? |
| How to provide tablespace name to OOB utility partition_utils to perform future partitions for /event (delayed and realtime) ? |
| It is observed that patch set 18 does not contain partition upgrade package. Please provide the Partition upgrade package. |
| References |