A connection profile to an Oracle database was created using the following connection values:
Database URL: jdbc:oracle:thin:@(description=(address=(protocol=tcp)(host=<database hostname>)(Port=<port>))(connect_data=(service_name=<database name>)))
User: <user name>
Password:: <valid password for the specified user>
The probe fails to connect and/or continuously restarts.
jdbc_response: all versions
The jdbc_response probe does not support extended properties and only supports connection strings as follows:
jdbc:oracle:thin:@IP address:Port Number:Database Name
jdbc:oracle:thin:@database server name:Port Number:Database Name
Therefore it is not possible to connect using additional properties (such as alternate protocols, etc). TCP protocol is used by default, TCPS and others are not supported.
Valid Database URL values are documented on the probe's AC and IM Wiki pages:
https://docops.ca.com/ca-unified-infrastructure-management-probes/ga/en/alphabetical-probe-articles/jdbc_response-java-database-connectivity-sql-queries-response-monitoring/jdbc_response-ac-configuration
https://docops.ca.com/ca-unified-infrastructure-management-probes/ga/en/alphabetical-probe-articles/jdbc_response-java-database-connectivity-sql-queries-response-monitoring/jdbc_response-im-configuration#jdbc_responseIMConfiguration-CreateaConnection
It may be more desirable to use the oracle probe for monitoring Oracle databases.