Question about Oracle - DBO Usability Connect Availability rule (4295432)

What test is being run that causes DBO Usability Connect Availability to fire. Is it connecting and running a simple query, or just connecting and disconnecting?

The Usability Connect Availability rule is raised if the database is running, but the connection is not possible for any reason. The reason can be also listener related, the appropriate message saying the connection is not available because of the listener will be displayed.

The DBO - Usability Connection Availability rule raises an alarm when the connection to the database instance has failed.

One of the Java classes uses the Oracle Thin JDBC driver to check connectivity. The rule only monitors connecting and disconnecting action.

Oracle's JDBC Thin driver uses Java sockets to connect directly to Oracle. It provides its own TCP/IP version of Oracle's SQL*Net protocol. Because it is 100% Java, this driver is platform independent and can also run from a Web Browser (applets).

There are 2 URL syntax, old syntax which will only work with SID and the new one with Oracle service name.

The commands are: jdbc:oracle:thin:@{0}:{1}:{2} and jdbc:oracle:thin:@//{0}:{1}/{3}
where 0 is the hostname, 1 is the port, 2 is the SID, and 3 is the port.

There is no SQL running here.