Unable to Target to Devices After Getting "Selected Device Does Not Exist in Any Schematic Diagram" Error (Doc ID 2286765.1)

Last updated on SEPTEMBER 07, 2017

Applies to:

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

Symptoms

If you select a device that exists in multiple maps but is NOT in both one-line and regular schematic maps, pressing the "one line" or "schematic map" target button causes the regular Target button to stop working for that device.

Toggling thru feeder, substation and single line schematic by the hypernode works until the error "Schematic Device Focus" error message is displayed. This breaks the connectivity of the hypernode.  Toggling between feeder, substation and single line schematics no longer works for that hypernode. The ability to target to that specific device is lost for all users when this occurs.


The issue can be reproduced at will on an OPAL environment with the following steps:

  1. Launch Web Workspace and login as a user with "Full Operation"
  2. Subscribe to all zones
  3. Target to device "2411" ( the hypernode ).
  4. Select the FID dot above it.
  5. Press the Target button a couple of times.

    It will cycle between the substation and the geographic maps.
  6. Press the One-Line button.
    You will get the "Not in schematics" error.
  7. Now press the Target button again.
    Nothing happens.
  8. Select the hypernode and press the Target button a couple of times.
    The viewer cycles between the substation and the geographic.
  9. Select the FID again.
  10. Press the Target button a couple of times.
    Nothing happens.
  11. Launch a second environment as a different user.
  12. Target to device "2411" ( the hypernode ).
  13. Select the FID dot above it.
  14. Press the Target button a couple of times.
    Nothing happens.

    (This issue can be reproduced on these two devices as well -- 24SUBT1 and 24SUBT2)

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