Unable to Migrate More Than One Associated Extension Block per Event Type
(Doc ID 2301792.1)
Last updated on MARCH 25, 2019
Applies to:Oracle Communications Pricing Design Center - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
On : 126.96.36.199.0 version, Migration for PDC
In Pipeline configuration, it has <NAME> which contains the common fields for all event types. Along with that, it has separate associated extension blocks (for ex: <NAME>, <NAME> etc.,) per event type which contains event specific fields. In the rating configuration, it will use these fields from event specific extension block for quantity / price model selectors, and the <NAME> block for RUM / price model selector.
However, during migration of configuration (refer to Migrating All BRM Pricing Objects @http://docs.oracle.com/cd/E22185_01/doc.111/e40784/mig_setup_run_migration_ece.htm#PDCMU190), it only considered one extension block, and hence the price model selectors were not been migrated properly.
After these workaround STEPs
1. Applied patch p26007365_111080_Linux-x86-64
2. Modify the MigrationConfiguration.xml to have:
/event/delayed/<NAME>/cloud mapped to <NAME>
/event/delayed/<NAME>/cloud/legacy_server_uptime mapped to <NAME>
3. Add the following record in IFW_REF_MAP table:
<IFW_REF_MAP ID ="CustomerData" REF_OBJ ="/service/<NAME>/cloud " REF_PARAM ="/event/delayed/<NAME>/cloud" />
Still, there was the below error at the 12th step of migration configuration, i.e. MIGRATE_SERVICE_EVENT_MAP(MigrateBRMPricing -restart -pricing).
oracle.communications.brm.pdc.migration.util.MigrationAnalysisException: MIG-00048: Unable to process the RUM expression because the field, "DETAIL.<NAME>.DURATION", is not valid for the event, "/event/delayed/rax/cloud/load_balancer". Ensure that the event field mapping exists in the BRM system.
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