How BRM Behaves Inserting Records In Partitions Based On Non-Poid Column (Doc ID 2105648.1)

Last updated on MARCH 15, 2016

Applies to:

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

Goal

Scenario:

* During a performance testing activity on a custom table where partition was created based on poid and indexes also created, experienced some performance issue wherein pcm_op_search is taking more time than expected.

Question:

* In this context, one would like to know how brm will behave if one creates partition on non-poid columns. Whether records will be inserted in correct partition or not?

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