RTDBAdapter Does Not Process Condition Actions When Subsequent Conditions are of a Different Class
(Doc ID 2795313.1)
Last updated on JULY 28, 2021
Applies to:
Oracle Utilities Network Management System - Version 2.5.0.1.0 to 2.5.0.1.0 [Release 2.5] Oracle Network Management for Utilities - DMS - Version 2.5.0.1.0 to 2.5.0.1.0 [Release 2.5] Information in this document applies to any platform.
Symptoms
On : 2.5.0.1.0 version, Adapters
RTDBAdapter skips conditions transactions (add/remove) when the condition class changes.
If you add a condition of one class (such as a "tag"), and then attempt to add a condition of a different class (such as a "note"), the RTDBAdapter will not process the second condition. The RTDBAdapter should always process conditions, regardless of class.
The issue can be reproduced at will with the following steps:
Start NMS with RTAdapter in RDBMS processing mode (-dir RDBMS)
Inject a condition of one class - something like:
Validate the note condition is also added as desired.
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!