My Oracle Support Banner

Reconnect Reads Are Received Prior To Reconnect And Failing (Doc ID 2627890.1)

Last updated on JANUARY 17, 2020

Applies to:

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

Symptoms

On : 2.1.0.3 version, Environment

Reconnect Reads are Received Prior to Reconnect and Failing

MDMPRD IMD ID 06934540975013 start time was 03:35:41PM, but MDM doesn't show the meter was reconnected until 03:38:54AM.
Because of the IMD period was within a disconnected period of time, MDM created a to do.

It seems like MDM needs the IMD From date/time to be exactly on the date/time of the reconnect time which is 09-09-2019 03:38:54PM
Because the read came earlier before the reconnect, that future IMDs were in exception because MDM registered usage during a disconnected period.

Also another example wherein Reconnect received 2 seconds earlier reconnect event date time and causes future reads to fail through

not able to figure out this is an MDM, SOM, or head end system issue


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1.Create a device ( smart meter ), device configuration, measuring component of auto read registers type. MC is capable of measuring reads on daily basis
2 Install the device at the service point.Install event should be in Connected/Commissioned state.
4.Add the reads on daily basis.
5 Initiate cut service for non-payment activity.
6.Cut for non-payment field task is created as a sub activity instead of remote disconnect.
7 Disconnect evnet get completed at 09-06-2019 01:01:28 PM and same recorded on Device On/Off status history
8 Initiate reconnect service that creates sub activity of remote connect.
9 Reconnect event gets completed at 09-09-2019 03:38:54PM and initiates Contingency Read scalar communication to HES for On Demand Read between 09-08-2019 03:38:54PM to 09-09-2019 03:38:54PM.
10 The reconnect read received of 09-09-2019 03:35:41 PM and gets finalized.
11 The future read read received goes into exception because Inactive Measurement Check VEE Rule showing the reason that
'Non-zero measurement were detected on disconnected device.

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
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.