Modifying Tablespace Details in BRM (Doc ID 1324523.1)

Last updated on SEPTEMBER 24, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.0.0.0.0 and later
Information in this document applies to any platform.
***Checked for relevance on 26-Jan-2014***

Goal

Scenario:

The database of the Oracle application Billing and Revenue Management (BRM) was created with tablespaces (pin00, pinX00, pintemp, aggregate_ts_*, integrate_ts_*) locally managed with uniform size 64k as recommended by Oracle consultants. However, we now have some objects in production with extents over 10000.

What can one do to reduce the number of extents of these objects?
The BRM application supports tablespaces with different names and uniform size, so, could one create more tablespaces with uniform size, multiples of 64k, to move these objects to reduce the number of extents ?

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms