My Oracle Support Banner

AMR Adapter is not Processing Meter "Power Ups" (Doc ID 2070505.1)

Last updated on MAY 31, 2024

Applies to:

Oracle Utilities Network Management System - Version 1.11.0.4 and later
Oracle Network Management for Utilities - DMS - Version 1.11.0.4 and later
Information in this document applies to any platform.

Symptoms

No power ups in NMS

You don't see any power ups in NMS, all power ups are blanks even some that have AMI requests = Yes.

Should be able to see power ups in Work Agenda to determine the number of customers that are up.

On the NMS side:
See the following error in the multispeak adapter log:
2015-09-22 20:02:16,964 ERROR amr.AmrImpl       (                   Logger.java:153)     - sendMeterState: got exception This RJVM has already been shutdown -2893037805884055578S:example.com:[7001,7001,-1,-1,-1,-1,-1]:nms:nms1; nested exception is: java.rmi.ConnectException: This RJVM has already been shutdown -2893037805884055578S:example.com:[7001,7001,-1,-1,-1,-1,-1]:nms:nms1
2015-09-22 20:02:21,511 WARN  avl.AVLBean       (                   Logger.java:264)     - Failure to convert coordinates This RJVM has already been shutdown -2893037805884055578S:example.com:[7001,7001,-1,-1,-1,-1,-1]:nms:nms1; nested exception is: java.rmi.ConnectException: This RJVM has already been shutdown -2893037805884055578S:example.com:[7001,7001,-1,-1,-1,-1,-1]:nms:nms1

The following kept growing in the log file over time to large values indicating the messages weren't being successfully transmitted:
loaded 61394 pending ping requests
sending 59545 meter statuses to NMS


On the NMS side the only place records would be backing up is in the AMR_RESPONSES database table. When the MultiSpeak adapter gets a meter status from AMI, it writes it into this table. It has a separate thread which periodically loads new records from that table and processes them.

If that periodic thread somehow got stuck, stopped or disappeared in some other way, then information from AMI would accumulate in the AMR_RESPONSES table.

If the issue is occurring, you could check that table for rows where REQ_STATUS = 'P' and RESULT_TIME is not null. These are the instances where meter status has been received from AMI but not yet processed and delivered to JMService.

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.