Mar 27, 2026 - For details about updated CVE-2025-53521 (BIG-IP APM vulnerability), refer to K000156741.

Forum Discussion

ST_Wong's avatar
ST_Wong
Icon for Cirrus rankCirrus
Feb 10, 2020

Oracle monitor SQL encryption

Hi,   We're running BIG-IP 14.1.0.5. We tried to monitor a Oracle 18c database but keeps getting following error:   2020-02-11 05:27:33,972 [DBPinger-50] - Attempting DB connection, attemp...
application delivery
big-ip
LTM
operations
FF's avatar
FF
Icon for Employee rankEmployee
Mar 24, 2020

Based on the error message and the version of Oracle database that you are attempting to connect, the more likely cause could be the lack of support for later versions of Oracle database. For more information, you may want to refer to K40226145: BIG-IP Oracle health monitor fails for Oracle DB version 12.2 or higher.

 

The recommended workaround is to use an alternative health monitor like TCP.

 

An alternative is to remove the profile parameter SQLNET.ALLOWED_LOGON_VERSION = 12 from the affected Oracle database. This would allow older legacy clients to connect to the database however it would also mean potential exposure to vulnerabilities such as CVE-2012-3137.

 

  • ST_Wong's avatar
    ST_Wong
    Icon for Cirrus rankCirrus
    Mar 24, 2020

    Thanks, though we're unable to update the affected Oracle database settings.

    We keep using TCP health monitor instead.

     

    Thanks and rgds