Unable to Migrate More Than One Associated Extension Block per Event Type

Last updated on SEPTEMBER 11, 2017

Applies to:

Symptoms

On : 11.1.0.8.0 version, Migration for PDC

In Pipeline configuration, it has ASS_XXX_EXT which contains the common fields for all event types.  Along with that, it has separate associated extension blocks (for ex: ASS_SRVR_UPTIME_EXT, ASS_SRVR_BW_EXT 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 ASS_XXX_EXT 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/XXX/cloud mapped to ASS_RAX_EXT
    /event/delayed/XXX/cloud/legacy_server_uptime mapped to ASS_SRVR_UPTIME_EXT
3. Add the following record in IFW_REF_MAP table:
    <IFW_REF_MAP ID ="CustomerData" REF_OBJ ="/service/XXX/cloud " REF_PARAM ="/event/delayed/XXX/cloud" />

Still, there was the below error at the 12th step of migration configuration, i.e. MIGRATE_SERVICE_EVENT_MAP(MigrateBRMPricing -restart -pricing).

ERROR
=====
oracle.communications.brm.pdc.migration.util.MigrationAnalysisException: MIG-00048: Unable to process the RUM expression because the field, "DETAIL.ASS_RAX_EXT.DURATION", is not valid for the event, "/event/delayed/rax/cloud/load_balancer". Ensure that the event field mapping exists in the BRM system.

Changes

Cause