Bug ID 467931: Command for diagnosing status of SQL monitors

Last Modified: Mar 12, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(all modules)

Known Affected Versions:
11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9

Fixed In:
11.6.0

Opened: Jun 19, 2014
Severity: 2-Critical
Related AskF5 Article:
K17471

Symptoms

There are no SQL monitor commands to check the status of outstanding pings and cached connections.

Impact

Cannot use the SQL monitor to check the status of outstanding pings and cached connections. This can make it difficult to debug issues with intermittent hangs of connections.

Conditions

This occurs with monitors that access SQL databases, such as Oracle monitors.

Workaround

None.

Fix Information

A new command has been added to help diagnose the state of the SQL monitors: /usr/share/monitors/DB_monitor cmd status [RD] [debug] RD: optional, the route domain for the desired Java daemon (each route domain gets a separate daemon) debug: optional, do debug logging Examples: /usr/share/monitors/DB_monitor cmd status /usr/share/monitors/DB_monitor cmd status 0 /usr/share/monitors/DB_monitor cmd status 17 /usr/share/monitors/DB_monitor cmd status 9 debug

Behavior Change