Bug ID 2567693: BIG-IP DNS Oracle monitor intermittently reports DOWN

Last Modified: Oct 20, 2026

Affected Product(s):
BIG-IP TMOS(all modules)

Known Affected Versions:
17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1, 17.1.2.2, 17.1.3, 17.1.3.1, 17.1.3.2, 17.1.3.4, 17.1.3.5, 17.1.3.6, 17.5.0, 17.5.1, 17.5.1.2, 17.5.1.3, 17.5.1.4, 17.5.1.5, 17.5.1.6, 17.5.1.8, 17.5.1.9, 17.5.1.10, 21.0.0, 21.0.0.1, 21.0.0.2, 21.0.0.3, 21.1.0, 21.1.0.1, 21.1.0.2, 21.1.0.3

Opened: Oct 09, 2026

Severity: 3-Major

Symptoms

An Oracle database monitor may intermittently report DOWN even when the database is available. The DBDaemon may terminate while processing a new probe, resulting in no database query being sent.

Impact

The monitored resource may be incorrectly marked DOWN, causing temporary GTM availability issues or false member-down events.

Conditions

Occurs with BIG-IP DNS Oracle monitors using the Java DBDaemon when a probe arrives near the approximately 59.5-second idle timeout.

Workaround

Set the Oracle monitor to an interval such as 23 seconds, to avoid overlap with the DBDaemon idle timer.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips