My Oracle Support Banner

Cannot Force ces_build_maps.ces To Skip Comparison of Current Import File to Previous Import File (Doc ID 2663157.1)

Last updated on AUGUST 31, 2020

Applies to:

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

Symptoms

On : 2.3.0.2.0 version, Data Model

In 2.3.0.2.15, Bug 30986645 added a check to ces_build_maps.ces so it would compare the current version of any import files getting built (~/data/patches/) against the previous version built (in ~/data/patches/done).

If the files are identical, then no changes are being made to the system, and the script does not send the import file to MBService.
Instead the script simply skips calling "Patch -diff [import file name]" and then just moves the previous version into ~/data/patches/done/old, and the current version into ~/data/patches/done.

This potentially causes two problems.

1. The graphical map ( ~/data/*.mad and ~/data/*.mac ) does not get touched.
If the project version of xx_maps_to_build.ces uses timestamp comparisons of ~/data/mp/*.mp files and ~/data/*.mad or *.mac files,
this could result in the Model Management tool showing the file as still needing to be built.

2. As the import file is not processed by MBService, no notification for an updated map gets sent.

There are situations where a customer might need the map updated notifications to be sent.

There is no means to do that.

 

 

Changes

 

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
 Workaround
References


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