Why Partition Pruning Is Not Working In 7.4
(Doc ID 1481201.1)
Last updated on NOVEMBER 14, 2023
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.4.0.0.0 to 7.4.0.0.0 [Release 7.4.0]Information in this document applies to any platform.
Goal
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.
Reproducible steps:
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.0.1 /search -1
0 PIN_FLD_FLAGS INT [0] 256
0 PIN_FLD_TEMPLATE STR [0] " select X from /event/billing where ( event_t.poid_type like '/event/billing/adjustment%' ) and F1 = V1 "
0 PIN_FLD_ARGS ARRAY [1]
1 PIN_FLD_ACCOUNT_OBJ POID [0] 0.0.0.1 /account 1348934
0 PIN_FLD_RESULTS ARRAY [0] NULL
4. Check dm_oracle.pinlog not adding any extra conditions
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |