Troubleshooting Database
Celoxis uses standard JDBC connections to connect to your database. If there are issues connecting to your database, it is most likely the result of a misconfiguration. We have provided you with the JDBC Probe program to identify the problem.
About JDBC Probe
Celoxis JDBC Probe is a simple java program that connects to your celoxis database. This helps to identify and fix connection issues with your database server.
Download JDBC Probe
Download jdbc-probe.zip from here
Using JDBC Probe
- Unzip the jdbc-probe.zip file. It should create a folder with the file JDBCProbe.class in it.
- Open a command prompt and cd to the folder that contains the JDBCProbe.class file.
- Run the program as shown below substituting values according to your setup.
java -cp .;drivers/* JDBCProbe product=oracle name=celoxis user=tim password=fox host=localhostjava -cp '.:drivers/*' JDBCProbe product=oracle name=celoxis user=tim password=fox host=localhost - 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.
Program Options
| product | One of oracle, pgsql (for PostgreSQL), or mssql (for MicrosoftSQL Server) |
| name | The name of the celoxis database instance. |
| user/password | The username and password to be used to connect to the database. In case of Microsoft SQL server, the login and database must be configured to use the SQL Authentication mode (or Mixed mode), not Windows authentication mode. |
| host | The dns hostname of the server where the database is running. |
| port | The port of the database server. This is an optional field and when unspecified the default port will be used. |
Error Messages and Possible 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 user
- Username or password is incorrect
Backend start-up failed: FATAL: database "celoxis_db" does not exist
- The database name (celoxis_db) is incorrect.
- The user doesn't have privileges to logon to the database
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 user
- Username 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 Connection
- This 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
- Firewall is blocking the connection.
- SQL Server not not been configured to listen on TCP/IP ports. To fix:
- Go to Microsoft SQL Server > 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)
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 denied
- Username 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
FAILURE: Listener refused the connection with the following error: ORA-12505, TNS:listener does not currently know of SID given in connect descriptor. [java.sql.SQLException]
- One of the parameter you are passing is incorrect
- The database does not exist on the connection properties you are specifying.