My Oracle Support Banner

Interval Averaging Rule Does Not Thrown Insufficient Data Exception. (Doc ID 2257842.1)

Last updated on SEPTEMBER 26, 2022

Applies to:

Oracle Utilities Meter Data Management - Version 2.1.0.3 to 2.2.0.1.0 [Release 2.1 to 2.2]
Information in this document applies to any platform.

Symptoms

On Meter Data Management 2.1.0.3 the Interval Averaging rule does not thrown insufficient Data exception.  Expected when there is no historical data available that the insufficient data exception is thrown.

Steps to Reproduce

The issue can be reproduced at will with the following steps:

Scenario 1:

  1. Load IMD for MC which does not have any data.
  2. Turn trace On and then VEE this IMD
  3. As there is no data for MC for any adjacent week, expectation is Interval Averaging for Scalar will throw “insufficient input data” exception.

Scenario 2:

  1. Load IMD for MC for a week from Monday- Thursday such as .11/2-11/6 -2015
  2. Load data for next immediate Friday 11/13/2015.
  3. Make sure there is no data for week of 11/9 except for 11/13 loaded above.
  4. Turn trace On and then VEE this IMD
  5. Averaging will find data for previous Friday (11/6) but based on settings on averaging rule it needs atleast 2 intervals to average. This fails.
  6. As there is no data for estimation available, expectation is Interval Averaging will throw “insufficient input data” exception

Changes

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
 Steps to Reproduce
Changes
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.