Some Migrations Seem To Only Get Flagged When Running nms-setup With -clean -reset Options
(Doc ID 2789256.1)
Last updated on JULY 02, 2021
Applies to:Oracle Utilities Network Management System - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 2.5]
Oracle Network Management for Utilities - DMS - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 2.5]
Information in this document applies to any platform.
Some migrations are only getting flagged when running nms-setup with -clean -reset options
You ran into an issue when you tried to do a clean build in one of the environments. The following 2 migrations were flagged as needing configuration.
The odd thing is that these seem to only get flagged when you run a setup using the -clean -reset options before building the model from scratch.
Ran nms-setup and was not flagged for the 2 migrations. Ran nms-setup -clean -reset and was flagged for the 2 migrations.
Migration 32021524 25.0.0
Migration 32590701 25.0.0
These have jconfig changes that seem like they would be needed whether this was a clean setup or not.
Since these are jconfig migrations they seem like they should be flagged in either case.
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