Versions Compared

Old Version 8

changes.mady.by.user Sumeet Tribhuvan (Unlicensed)

Saved on

compared with

New Version 9

changes.mady.by.user Rashmi Likhite

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Celoxis JDBC Probe is a java program that helps understanding of connection to understand connection issues with your database server. 

Download

Click here to download the jdbc-probe.zip file. 

Info
iconfalse

Status
colourRed
titleImportant

This test needs to be run from on the server where Celoxis will be is installed; NOT on the database server.

...

You will receive a success message if the connection was successful. If the connection fails, the message returned by the driver is printed. This error message will give you a clue about the possible causes as explained later in this document.
 

Options:

productone of the following:
oracle (for Oracle), pgsql (for Postgresql 9.0), mssql (for SQL Server 2008, 2012, 2014)
nameThe name of your database
user/passwordThe username and Password to be used to connect to the database.
NOTE:  In case of SQL server, the login and database must be configured to use the SQL Authentication mode (or Mixed mode), not Windows authentication mode only.
hostThe machine name of the server where the database is running
portThe port of the database server. This is an optional field and when unspecified the default port will be used. 

You will receive a success message if the connection was successful.  If the connection fails, the message returned by the driver is printed. If you don't understand the output simply send us the output.

Understanding the Error Messages

Common errors for Oracle

ERROR MESSAGEPOSSIBLE CAUSES
The Network Adapter could not establish the connection
  • The host name cannot be resolved by the DNS server.
  • Database server is not running on the host.
  • The database port on the database server is inaccessible because of a firewall 
Invalid username/password; logon deniedUsername or password is incorrect
Connection refused(DESCRIPTION=(TMP=) (VSNNUM=153092352)(ERR=12505) (ERROR_STACK=(ERROR=(CODE=12505)(EMFI=4))))
  • The database name is incorrect
  • The user doesn't have privileges to logon to the database


Common errors for MSSQL

ERROR MESSAGEPOSSIBLE CAUSES
Error establishing socket.
  • The host name cannot be resolved by the DNS server.
  • Database server is not running on the host. 
  • The database port on the database server is inaccessible because of a firewall
Login failed for userUsername or password is incorrect.
Cannot open database requested in login
  • The database name is incorrect.
  • The user doesn't have privileges to logon to the database
Not Associated with a trusted SQL Server ConnectionThis occurs typically when Microsoft Sql Server installation is configured to use only Windows authentication and not SQL Server authentication. To solve the problem: Change the Authentication change the authentication mode to sql server authentication. 
The TCP/IP port is disabled or not accepting connections
  • Go to Microsoft SQL Server 2008, 2012, 2014> Configuration Tools > SQL Server Configuration Manager
  • In the SQL Server Configuration Manager select the node SQL Server Network Configuration > Protocols for MSSQLSERVER
  • Right-click on the TCP/IP node and select Enable
  • Restart the SQL Server (SQLEXPRESS) service (In Control Panel > Adminstrative Tools > Services, right-click on the SQL Server (SQLEXPRESS) service and select Restart)

Also, check that the firewall is not blocking the connection.


Common errors for Postgresql

ERROR MESSAGEPOSSIBLE CAUSES
The connection attempt failed
  • The host name cannot be resolved by the DNS server.
  • Database server is not running on the host.
  • The database port on the database server is inaccessible because of a firewall 
Connection rejected: FATAL: password authentication failed for userUsername or password is incorrect
Backend start-up failed: FATAL: database "celoxis" does not exist
  • The database name (abc) is incorrect.
  • The user doesn't have privileges to logon to the database