ces_control_zones.ces Generates "4803.new feeder - (zone1.ncg) != (zone2.)" Errors

(Doc ID 1103747.1)

Last updated on JUNE 15, 2016

Applies to:

Oracle Utilities Network Management System - Version 1.10.0.6 and later
Oracle Network Management for Utilities - DMS - Version 1.10.0.6 and later
Information in this document applies to any platform.

Symptoms

Running 'ces_control_zones.ces' generates warnings that follow the form:

WARNING - line=### 4803.<feeder name> - (<substation name 1>.<substation 1's control zone#>)!=(<substation name 2>.)


For example:
You have previously run 'ces_control_zones.ces' successfully against this data file:

Oracle
FUZZY
Redwood Shores|Oracle Northeast|Oracle Grove Sub|SUB_ORACLE_GROVE
Redwood Shores|Oracle Northeast|Oracle Grove Sub|Grove Feeder 1
Redwood Shores|Oracle Northeast|Oracle Forest Sub|SUB_ORACLE_FOREST
Redwood Shores|Oracle Northeast|Oracle Forest Sub|Forest Feeder 1

The system assigned these control zones:

Control Zone NameControl Zone #
Redwood Shores 1001
Oracle Northeast 1010
Oracle Grove Sub 1100
Oracle Forest Sub 1101
SUB_ORACLE_GROVE 2001
Grove Feeder 1 2002
SUB_ORACLE_FOREST 2003
Forest Feeder 1 2004

You are adding several future expansion zones.  This is the updated control_zones.dat file:

Oracle
FUZZY
Redwood Shores|Oracle Northeast|Oracle Grove Sub|SUB_ORACLE_GROVE
Redwood Shores|Oracle Northeast|Oracle Grove Sub|Grove Feeder 1
Redwood Shores|Oracle Northeast|Oracle Grove Sub|Expansion 1
Redwood Shores|Oracle Northeast|Oracle Grove Sub|Expansion 2
Redwood Shores|Oracle Northeast|Oracle Forest Sub|SUB_ORACLE_FOREST
Redwood Shores|Oracle Northeast|Oracle Forest Sub|Forest Feeder 1
Redwood Shores|Oracle Northeast|Oracle Forest Sub|Expansion 1
Redwood Shores|Oracle Northeast|Oracle Forest Sub|Expansion 2

Running 'ces_control_zones.ces' against that file, will generate these errors:

WARNING - line=9 4803.Expansion 1 - (Oracle Grove Sub.1100)!=(Oracle Forest Sub.)
WARNING - line=10 4803.Expansion 2 - (Oracle Grove Sub.1100)!=(Oracle Forest Sub.)

Changes

Adding new control zone entries can trigger this problem.

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