My Oracle Support Banner

Questions Around Partitioning Database Tables Using The BRM Utility partition_utils.pl (Doc ID 1561112.1)

Last updated on SEPTEMBER 25, 2019

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.4.0.0.0 to 7.5.0.0.0 [Release 7.4.0 to 7.5.0]
Information in this document applies to any platform.

Purpose

Customer need to run partition_utils.pl utility to create partitions in event_t table for BRM 7.4 database. There are some questions around this utility to understand the impacts.

Scenario is:

The last partition in event_t table is: P_R_05102013 (i.e. 10-May-2013). The data beyond this partition is stored in default partition: PARTITION_LAST in event_t table.

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
 Is there a way to create partitions from 11-May-2013 (which is an old date as compared to today 21-May-2013) without any data loss?
If yes, will the data from the default partition: PARTITION_LAST be updated in these new partitions properly? e.g.
 If this utility is run with 2 days later date, where will the data of the default partition: PARTITION_LAST be moved? e.g.
 What about todays and tomorrows data, if we are going to create the partition from day after tomorrow?
 How does the PARTITION_LAST behaves? Does the data in this gets moved as soon as we run the utility or on the day actual partition starts?
 What is a suitable way to create backdated partition using partition_utils.pl, in current scenario?


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