Troubleshooting Oracle SSL Connection Errors

Troubleshooting Oracle SSL Connection Errors

Troubleshooting guide for Oracle Database monitoring in ManageEngine Applications Manager.

Some Oracle connection errors are caused by TLS configuration or listener endpoint settings rather than by an untrusted certificate. Use the sections below to identify these cases before importing certificates.

1. SSL connection failed due to configuration issues.

What it means: The SSL handshake started, but the server closed the connection. The client and server may not share a TLS version or cipher suite. Importing a certificate will not resolve a protocol or cipher mismatch.

Applications Manager runs on Java 17, which does not support TLS 1.0 or TLS 1.1.

What to do:

  1. On the database server, open sqlnet.ora and check SSL_VERSION. If it specifies 1.0 or 1.1, change it to 1.2:
    SSL_VERSION = 1.2
  2. If SSL_CIPHER_SUITES contains a short list of older cipher suites, comment out the setting so the listener offers its default set.
  3. Restart the listener:
    lsnrctl stop
    lsnrctl start
  4. Verify that the wallet used by the listener contains a valid, unexpired certificate:
    orapki wallet display -wallet <wallet_location>

2. Please check if SSL is enabled for given port in Oracle Server.

What it means: The server closed the connection before an SSL exchange. The monitor may be using a plain TCP port while SSL is enabled, or a TCPS port while SSL is disabled.

What to do:

  1. Check the listener endpoints:
    lsnrctl status
    Look for a TCPS endpoint. Use its port when SSL is enabled in the monitor. The TCP endpoint, usually port 1521, is used when SSL is disabled.
  2. If there is no TCPS endpoint, SSL is not configured on this listener. Disable the SSL option in the monitor, or ask the DBA to add a TCPS endpoint in listener.ora and configure WALLET_LOCATION to point to the server wallet.
  3. From the Applications Manager host, test connectivity to the TCPS port:
    telnet <oracle-host> <tcps-port>