Last Modified: Sep 13, 2023
Known Affected Versions:
10.2.4, 11.0.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.5.1 HF1, 11.6.1 HF1, 11.5.1 HF2, 11.6.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.6.2 HF1, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1
11.6.0, 11.5.1 HF6, 11.4.1 HF9, 10.2.4 HF12
Opened: Nov 06, 2013 Severity: 2-Critical Related Article:
Related Article: K14862
Consider a configuration containing two or more oracle monitors configured to the same ip::port. The pool member statuses can be incorrectly reported for the default time interval setting. The possibility of the incorrect status reporting increases if the monitor interval is reduced from its default value 10.
Incorrect status reporting in oracle monitors. This may lead to data traffic directed to pool members that are down and no data traffic directed to pool members that are available.
Configuration containing database monitors with the same ip::port destination.
Increasing the monitor time interval will alleviate this issue.But it may not solve it entirely.
Pool member status are updated correctly if there are multiple database monitors configured to the same ip::port destination.