X1-MIGAD Completed With Error - PluginDrivenGenericStandardCommitWorker
(Doc ID 2894871.1)
Last updated on SEPTEMBER 11, 2022
Applies to:Oracle Utilities Customer Cloud Service - Version 22A and later
Oracle Utilities Customer to Meter Base - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
On: 22A version, Environment Related
X1-MIGAD completed with Error - PluginDrivenGenericStandardCommitWorker
Problem: X1-MIGAD completed with Error - PluginDrivenGenericStandardCommitWorker - GKMPSV15Metrology Firmware duplicate key error.
Context: AIS Oracle DM is converting the legacy meter types from manual to the smart meter and non-track to tracked of legacy Meter Types MMBBPVT, MMBBPVT, ESMT, and EMFM.
Issue 1a) In X1MigSpec (MIGAD), the inclusion of Meter Type in building the Specification should be applicable to all scenarios
Issue 1b) If X1MigSpec of MIGAD will include Meter Type in building the Specification regardless of scenarios, X1-MIGMT should also be aligned to this business rule
Issue 2) In X1MigSpec, why the code is throwing GKMPSV15Metrology Firmware duplicate key error even if the record does not exist in our database. 97% of the total 4.6 million client’s meters will fail
We need to convert 4-meter types along with 4.5 million meters as smart meters. This is a major blocker to our key project milestone.
We also observed that X1-MIGAD component(s) that if migration mode is staggered, there is a section that deletes Specification entity. However, it seems Specifications are not truly deleted.
Please see attached SR 3-29801521791_Patch 34316882_CTM-9352_RETEST FAILED_6Jul2022.docx
X1-MIGAD completed with Error - PluginDrivenGenericStandardCommitWorker - GKMPSV15Metrology Firmware duplicate key error.
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