nms_load_crews Can Corrupt Crew Data if Crew Files Contain Bad Control Zone Information (Doc ID 2289774.1)

Last updated on JULY 24, 2017

Applies to:

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

Symptoms

On : 2.3.0.0.0 version, Web Workspace

When running "nms_load_crews", the crews that are created are not assigned to the correct control zones.



The issue can be reproduced at will with the following steps:

Create the three required data files -- crews.csv, members.csv and vehicles.csv.


crews.csv
CREW_KEY,CREW_TYPE,TEMP_FLAG,ZONE_NAME,ZONE_CLS,ZONE_IDX,CREW_SIZE,CONTACT,CREW_NAME,MOBILE_NUM,PAGER_NUM,MDT_CREW,EXTERNAL_KEY,OUT_OF_RANGE,MOBILE_FLAG,MEMBERS,VEHICLES
13,Service,N,Lake,4802,1000009,3,JOE,Trouble Crew,,,Y,003,N,,00213:00215,201:202
14,Service,N,Lake,,,3,JOE,Trouble Crew 2,,,Y,003,N,,Fred,Rover



members.csv
MEMBER_NAME,MEMBER_CLASS,MEMBER_EMP_NUMB
Jennifer,Troubleman,00213
Fred,Trimmer,00214
JOE,Foreman,00215

vehicles.csv
VEHICLE_TYPE,VEHICLE_NUMB
Rover,201
Pole Truck,202


Run this command:
nms_load_crews -add -crews crews.csv -members members.csv -vehicles vehicles.csv  -status on-shift

Run this command:
Action any.JMService dump crews

You will notice that no warnings are printed for "Trouble Crew 2" even though no members or vehicles get added and that the zone handle is not valid.
Also, no warnings are printed that Fred is not used.


Changes

 

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