Unexpected Behavior Seen in NMS Scripts

(Doc ID 2328689.1)

Last updated on NOVEMBER 15, 2017

Applies to:

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

Symptoms

The script ces_build_maps.ces was moving import files into the ~/data/patches/done directory even though the patch failed.
The script, as it exists in $CES_HOME/bin, simply cannot behave this way - there are checks for errors that prevent this observed behavior.

 

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

echo "FOO" > ~/bin/ces_build_maps.ces
chmod 755 ~/bin/ces_build_maps.ces

Attempt to do a model build.
Watch as it fails.

Changes

At some point, the ces_build_maps.ces script from product was copied and modified.  This was saved to the $NMS_HOME directory and forgotten.

 

The system should warn about custom scripts.



Run this command to get the warning --

ls $NMS_HOME/bin | xargs -i{} ls $CES_HOME/bin/{} 2>&1 | grep -v "No such file" | xargs -i{} echo "WARNING! NON-PRODUCT version of '{}' found in $NMS_HOME/bin"

Remove bad version of script.

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