My Oracle Support Banner

Issue In Performing Composite Aggregation Due To Data Getting Saved In Incorrect Table. (Doc ID 2788445.1)

Last updated on SEPTEMBER 21, 2022

Applies to:

Oracle Utilities Customer to Meter Base - Version 2.7.0.3.0 and later
Oracle Utilities Service and Measurement Data Foundation - Version 2.3.0.2.0 to 2.4.0.0.0 [Release 2.3 to 2.4]
Information in this document applies to any platform.

Symptoms

On: 2.7.0.3.0 version, Installation, and Patching

The issue in performing Composite Aggregation due to data getting saved in the incorrect table.

While performing Composite Aggregation via Aggregation Group Run, Aggregator Composite MC Set Participant is created successfully but aggregated data is not getting created from foundation MC set participants to Composite MC Set Participants. The issue seems to be that the system incorrectly expects ‘Measurement’ BO to be configured for the MC Set Type configuration instead of ‘Aggregation Measurement’ BO. This issue is occurring only for Composite Measuring Component Sets.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
Data Setup:
1. Configure Aggregation Group of Foundation Measuring Component Sets which retrieves data from physical measuring components.
Foundation Aggregation Group:
2. Set up Aggregation Group containing Composite Measuring Component Set which gets its aggregated value from foundation measuring component sets (referring to Step 1).
Composite Aggregation Group:
Measuring Component Set:
3. Configure Aggregator MC type for Composite MC Set
4. Set up Related Data Source:
5. Aggregator MC type configuration for Foundation MC Sets
This issue exists if highlighted Measurement Business Object is configured as ‘Aggregation Measurement’ on foundation aggregator MC Types. After changing this
Measurement Business Object to ‘Measurement’, the composite aggregation is done successfully. The issue is using the latter option is that it is saving the foundation MC
Sets aggregated data in the D1_MSRMT table and this will give a performance hit while retrieving the data from D1_MSRMT instead of the D1_AGG_MSRMT table.

Cause

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
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.