Dm_oracle Optimization Adds Poid Ranges For Partition Historic, Delayed and Migrate (Doc ID 2317615.1)

Last updated on AUGUST 08, 2023

Applies to:

Goal

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:

Solution

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