Dm_oracle Optimization Adds Poid Ranges For Partition Historic, Delayed and Migrate
Last updated on NOVEMBER 07, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
Qn1: How the dm_oracle does this optimization and if there is a way to turn it off for different partition types that are not using?
When doing an event search using created_t, the dm_oracle optimization automatically adds poid ranges for partitions delayed, historic and migrate.
This poid ranges are also being added if these partitions do not exist.
Also, even set the partitioning mode to 1 for all events and do not have a partition historic, dm_oracle adds the poid range to check for potential records in the partition historic.
This is the search flist:
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