Multiple Rows in the AMR_CU_METERS and AMR_CU_METERS_HISTORY Tables Have the Same REQUEST_IDX For a Given METER_ID Value

(Doc ID 2326370.1)

Last updated on NOVEMBER 09, 2017

Applies to:

Oracle Utilities Network Management System - Version 1.12.0.3 to 2.3.0.1.0 [Release 1.12 to 2.3]
Oracle Network Management for Utilities - DMS - Version 1.12.0.3 to 2.3.0.1.0 [Release 1.12 to 2.3]
Information in this document applies to any platform.

Symptoms

The AMR_CU_METERS.request_idx column is not being cleared when a spontaneous meter status is received that is not associated with a ping request.

This causes both the AMR_CU_METERS and AMR_CU_METERS_HISTORY tables to have multiple rows with the same request_idx for a given meter_id.
 

The AMR adapter should not re-use the previous request_idx for an unsolicited status.

The issue can be reproduced at will with the following steps:
1. There is an active ping request for a meter, say request_idx 1000.
2. A power ON status is received for the meter.
3. The amr_cu_meters table is updated with the new result_time, status etc as well as the request_idx.
4. At some later time, another power ON (or OFF) status is received for the meter.
5 The amr_cu_meters table is updated again with the new result_time, status etc and the request_idx is left unchanged.


Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms