AMR Adapter - Meter Pings Fail to Process Meter Status
(Doc ID 2296876.1)
Last updated on JUNE 02, 2024
Applies to:
Oracle Utilities Network Management System - Version 1.12.0.3 to 2.3.0.0.0 [Release 1.12 to 2.3]Oracle Network Management for Utilities - DMS - Version 1.12.0.3 to 2.3.0.0.0 [Release 1.12 to 2.3]
Information in this document applies to any platform.
Goal
**Disclaimer:** This KM article may include the following abbreviations:
AMR - Automatic Meter Reading
NMS - Oracle Network Management System
Meter Pings stop processing update in, the response is coming back from AMI but the update does not get written to the database:
Error was displayed in log4j.log
Call: UPDATE AMR_CU_METERS SET RESULT_TIME = ? WHERE (METER_ID = ?)
bind => [2 parameters bound]
Query: UpdateObjectQuery(AmrMeter [altMeterNumber=G159212218, amrEnabled=Y, lastGaspTime=Mon May 30 01:24:59 EDT 2016, meterId=4960422, meterNumber=G159212218, powerUpTime=Thu Aug 03 23:26:17 EDT 2017, resultTime=Fri Aug 04 06:57:51 EDT 2017, status=NO_REPLY])
at org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:333)
at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.processExceptionForCommError(DatabaseAccessor.java:1494)
at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:636)
at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor
The error below indicates the query against the AMR_CU_METERS table timing out in WebLogic.
Query: ReadAllQuery(name="AmrMeter.findByAltNumber" referenceClass=AmrMeter sql="SELECT METER_ID, ALT_METER_NO, AMR_ENABLED, LAST_GASP_TIME, METER_NO, POWER_UP_TIME, PROBABILITY, REQUEST_IDX, RESULT_TIME, STATUS FROM AMR_CU_METERS WHERE (ALT_METER_NO = ?)")>
<Aug 4, 2017 4:42:40 AM EDT> <Error> <EJB> <BEA-011088> <The following error occurred while invoking the ejbTimeout(javax.ejb.Timer) method of EJB 'AmrBean(Application: nms-amr-NMSP#1.12.0.3.24, EJBComponent: nms-amr-ejb.jar)'.
javax.ejb.EJBException: Transaction Rolledback.: weblogic.transaction.internal.TimedOutException: Transaction timed out after 34 seconds
Solution
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
Goal |
Solution |
References |