Estimation Batch Creates Non-midnight Reads (10 PM Reads) When Period Includes Two DST Transitions.
(Doc ID 2261995.1)
Last updated on SEPTEMBER 28, 2022
Applies to:
Oracle Utilities Meter Data Management - Version 2.1.0.3 to 2.2.0.1.0 [Release 2.1 to 2.2]Information in this document applies to any platform.
Symptoms
**Examples provided in this article do not represent real life personal/confidential information**
**Disclaimer:** This KM article may include the following abbreviations:
DST - Daylight Saving Time
Estimation batch (D1-SMMTR) is creating non-midnight reads (10 PM reads) when the period includes two DST transitions and the batch run date is in DST.
Ex: Period is from Nov 1st 2016 to Mar 14th 2017.
There are 2 DST transitions for this period: Nov 6th 1:59:59 2016 and March 12th 1:59:59 2017.
Steps to Recreate
1. Create a device, device configuration and install it on a service point.
2. Create a set read for the measuring component on 11/04/2016 12:00AM.
3. Run batch in DST (suggested March 14, 2017 onwards).
4. Non midnight estimation happens during an estimation batch run at DST trying to estimate missing reads in which DST end was included.
Sample: Estimation Batch Run: March 14, 2017
Missing Reads to be estimated: 11/05/2016 to 11/14/2016 10 PM estimation will start at DST end 11/06/2016
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 |