ScadaMaxMeasuresRowsFetch Rule not Behaving as Expected.
(Doc ID 2848274.1)
Last updated on JUNE 02, 2024
Applies to:
Oracle Utilities Network Management System - Version 2.4.0.1.0 to 2.5.0.1.0 [Release 2.4 to 2.5]Oracle Network Management for Utilities - DMS - Version 2.4.0.1.0 to 2.5.0.1.0 [Release 2.4 to 2.5]
Information in this document applies to any platform.
Symptoms
On : 2.4.0.1.0 version,
scadaMaxMeasuresRowsFetch rule not behaving as expected.
When setting scadaMaxMeasuresRowsFetch to a value of 25000, the following unexpected behaviour was noticed:
1) JMS not printing out the scadaMaxMeasuresRowsFetch in a dump rules.
2) The customer in question only has a total of approx 20k measurements to load, yet the dialog pops up saying that it could not load all the points with a very message of "The selected filter resulted in too many rows being selected.\n Only the first 0 rows are returned. (See configuration rule scadaMaxMeasuresRowsFetch)"
3) Config assistant and DB confirms SRS rule is set to 25000 (rule_value_2 yet the message above and weblogic log reports that it is set to zero ("scadaMaxMeasuresRowsFetch Value 0")
Note that in the above scenario, the following four rules are set/enabled:
scadaMeasureDigitalUpdates
scadaMeasureAnalogUpdates
scadaUseMeasuresCache
4) But despite the dialog popping up, SCADA Summary still appears to load ALL the scada points.
5) From CT, selecting LOAD device does load all the rows for the given device but again, the dialog pops up with the above message
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 |
| Cause |
| Solution |
| Fix Description |
| Migration |
| Workaround |
| References |