My Oracle Support Banner

Incident With Wrong Call Time Created For AMR Last Gasp Message When Timestamp is Ambiguous (Doc ID 2905631.1)

Last updated on NOVEMBER 03, 2022

Applies to:

Oracle Utilities Network Management System - Version to [Release 2.5 to 2.6]
Oracle Network Management for Utilities - DMS - Version to [Release 2.5 to 2.6]
Information in this document applies to any platform.


On : version, Adapter

AMR last gasp message does not create an event

When testing the last-gasp API for meters in the AMR interface, the implementers found that the system did not create an event for the last gasp message.
They could see the AMR message was received and processed by JMService but the event_idx is set to 0.0.
Incidents table has incident recorded without event_idx .
We noticed that incident table has date format as US format (month/day/year) and message sent to AMR has date formatted by Australian standards (day/month/year).

Expected result: an incident is created in NMS with call time matching the last gasp time reported by AMI.

The issue can be reproduced at will with the following steps:
1. Make sure that Outage Detection is enabled per 'amrInterfacesEnabled' configuration rule.
2. Make sure that 'useMeterTimeForDetection' configuration rule is enabled.
3. Submit a last gasp message from AMI.




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
 Fix Description

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