Records For ITEM_T Going Into PARTITION_MIGRATE Instead Of Monthly Custom Partitions
Last updated on SEPTEMBER 14, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
Records for ITEM_T going into PARTITION_MIGRATE instead of monthly custom partitions
We have 2 different poid ranges for ITEM_T
1. Realtime poid range - we can get this using pin_partition.maxpoid(,0 )
Currently this partition contains all items which are corresponding to /event/delayed/session types ( usage events )
2. Poid range generated by sequencer POID_IDS2
Currently this partition contains all items which are of /item/cycle_forward or /item/purchase_fee.
We have created custom monthly partitions using partition_utils using REALTIME option.
But, all /item/cycle_forward and /item/purchase_fee items are going into PARTITION_MIGRATE as per their poid range.
How to redirect /item/cycle_forward and /item/purchase_fee item poids to custom monthly partitions ( having realtime poid range ) ?
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