Why Partition Pruning Is Not Working In 7.4
Last updated on APRIL 13, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 7.4.0]
Information in this document applies to any platform.
Checked for relevance on 15-Aug-2014
There is a requirement to test by enabling partition pruning in dm_oracle pin.conf (which is a default value). In such scenario, the events are not being picked by the partition.
1. Create the partitioned object
2. Set dm_oracle pin.conf with the following value
- dm prune_partitions true
3. Run search on the object by using the following search tempate
0 PIN_FLD_POID POID  0.0.0.1 /search -1
0 PIN_FLD_FLAGS INT  256
0 PIN_FLD_TEMPLATE STR  " select X from /event/billing where ( event_t.poid_type like '/event/billing/adjustment%' ) and F1 = V1 "
0 PIN_FLD_ARGS ARRAY 
1 PIN_FLD_ACCOUNT_OBJ POID  0.0.0.1 /account 1348934
0 PIN_FLD_RESULTS ARRAY  NULL
4. Check dm_oracle.pinlog not adding any extra conditions
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