ces_build_maps.ces Should Check if Import File Has Changed Before Sending it To MBService
(Doc ID 2656952.1)
Last updated on APRIL 08, 2020
Applies to:Oracle Utilities Network Management System - Version 188.8.131.52.0 to 184.108.40.206.0 [Release 2.3 to 2.4]
Oracle Network Management for Utilities - DMS - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 2.3 to 2.4]
Information in this document applies to any platform.
On : 22.214.171.124.0 version, Web Workspace
MBService seems to spend a large amount of time processing maps that don't actually make any changes to the system.
When MBService is started with the "-report" option (or reporting is enabled via the Model Management GUI), it creates a Patch####.report file for each patch it processes, listing any changes it introduced as part of that model build.
For one particular customer, a large number of reports ended with this line:
Total number of modified objects = 0
This meant that those patches, which were still processed, did not make any changes to the model.
As a result of each patch, each service had to spend a small amount of time processing any potential change.
This is rather wasteful.
The build process should not process maps when they make no changes.
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