My Oracle Support Banner

System Fails to Start Processing FLISR Events After Upgrade from NMS 1.12.0.3 to 2.3.0.2 (Doc ID 2422051.1)

Last updated on MARCH 08, 2019

Applies to:

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

Symptoms

On : 2.3.0.2.0 version, Web DMS - Oracle Network Management for Utilities

Oracle Network Management System (NMS) 2.3 is failing to start processing FLISR events the same as on 1.12x

Testing FLISR application on 2.3 NMS and experiencing issue not observed on 1.12 version .

It looks like NMS does not see (process) lockout signal on second device (CB) open and as a consequence setting new 60 second momentary timer which cause FLISR to abort processing.
  FLISR report message is  stating that "1010:Lockout indicator not set"

It takes approx. 60 seconds to operate (open) Device on Lockout stage . My understanding is that receiving lockout signal DMS is meant to disregard60 seconds timer and create outage which will trigger FLISR processing .

I have tested the same scenario on current 1.12 version and DMS is processing outage correct and starting FLISR event as expected .

 

Changes

 Upgraded testing system from 1.12.0.3.x to 2.3.0.2.x

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.