If you must enter a JDBC URL manually, make sure that you replace possible placeholders enclosed with '' in a template you have copied, such as, and look for other syntax errors. In both cases, we recommend using the Server Info settings format instead of the Database URL format for the connection, and let DbVisualizer build a valid JDBC URL for you.

': Io exception: Invalid number format for port number Io exception: Invalid number format for port number'.

The error also occurs when trying to connect to a database with the wrong driver. The most common reason for this error is that the database URL contains a syntax error preventing the driver from accepting it.

'The selected Driver cannot handle the specified Database URL.

JDBC syntax errors typically result in one of two error messages: If this test fails, please ask your system or database administrator for help. You can use the Ping Server button to make sure that the a TCP/IP network connection can be established to the specified server and port. The first three problems usually results in a somewhat cryptic message about I/O errors or a time-out.

Native libraries for a JDBC driver are not found.

The user account is not authorized to connect from the client where you run DbVisualizer,.

A syntax error in a manually entered JDBC URL,.

A firewall between the client and the database server blocks connections to the database port,.

TCP/IP access is not enabled in the database server,.

Incorrect values for the Database Server or Database Port fields in the Object View tab for the connection,.

Run a query in Vertica to verify the version. Here is a simple query you can run that will tell you what client version you are running.There may be many reasons for why you cannot connect to a database, but some of the most common are:.

DBVisualizer and many other developer tools do this. This is usually the easiest and most reliable since they tools use the Vertica API to obtain the version.

Most 3 rd party tools show you what the version of the client driver is in their properties panel.

I have also seen some 3 rd party tools rename a more recent 7.1 driver to 6.3 because their GUI’s have not been updated to support more recent versions of Vertica. Usually the file name contains the version but this is not always reliable since some 3 rd party vendors rename the file to something like vertica.jdbc.Our internal group had the old Vertica 6.1.3 driver which did not have the capability to enable load balancing. There are a few methods to find out what Version of the client driver you are using for JDBC. In our organization we obtain our client tools and drivers from an internal site instead of the Vertica site. Otherwise, check with your DBA to enable server side load balancing. If enabled, the result will either be roundrobin or random. SELECT LOAD_BALANCE_POLICY FROM V_CATALOG.DATABASES

Dbvisualizer vertica