Why Birth Patch Values Do Not Match for the Same Object in Model Tables
(Doc ID 1400143.1)
Last updated on DECEMBER 03, 2019
Applies to:Oracle Utilities Network Management System - Version 1.7.5 and later
Oracle Network Management for Utilities - DMS - Version 22.214.171.124 to 126.96.36.199 [Release 1.10]
Information in this document applies to any platform.
Active supply nodes in the SUPPLY_NODES and NETWORK_NODES tables are mismatched when considering the birth_patch. For the same birth_patch, the supply node will be active in one table but not the other. The following scenario demonstrates this behavior:
Change the phase of a transformer in the GIS.
Extract and model build the tile containing the transformer.
Edit the .mp file containing the transformer to change the phase designation and
Then model build the .mp file.
The SUPPLY_NODES table will have a new row for the transformer because the phases attribute will have changed. The NETWORK_NODES table will remain unchanged for the supply node.
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
|Questions and Answers|