Hsqldb version issue: Client driver version greater than . is required - hsqldb

I am getting following error in my hsqldb server.
[Server#85ede7b]: [Thread[HSQLDB Connection #17bf2dab,5,HSQLDB Connections #85ede7b]]: 0:Failed to connect client. Stack trace follows.
org.hsqldb.HsqlException: Client driver version greater than '-268.-50.-11.-82' is required. HSQLDB server version is '2.3.2'
at org.hsqldb.error.Error.error(Unknown Source)
at org.hsqldb.server.ServerConnection.init(Unknown Source)
at org.hsqldb.server.ServerConnection.run(Unknown Source)
at java.lang.Thread.run(Thread.java:745)
please suggest

You are attempting to connect to a HSQLDB server but you are not using the HSQLDB version 2.3.2 jar on the client side. Check the jar is the same. Your connection url should also start with jdbc:hsqldb:hsql:.
The error also happens when you connect to HSQLDB server from software programs that are not related to HSQLDB, for example a web browser.

Related

Database connection test failed in web-logic server

I am getting below error while creating data-source to a database in weblogic server 12.
Error Cannot load driver: com.microsoft.sqlserver.jdbc.SQLServerDriver
Weblogic comes with it's own driver for sql server, weblogic.jdbc.sqlserver.SQLServerDriver which is available in the classpath. An example jdbc url for connecting using that driver is jdbc:weblogic:sqlserver://SBNSWDV63\\SSQLDV03:1433;allowPortWithNamedInstance=true
If you want to use the microsoft driver, you have to make sure the jar file containing that driver is copied to your <domain_home>/lib folder, so it's visible to weblogic.

Having connection issue while connecting to MariaDb Galera cluster using mariadb jdbc connector plugin

Error: org.springframework.jdbc.CannotGetJdbcConnectionException: Failed to obtain JDBC Connection; nested exception is java.sql.SQLNonTransientConnectionException: (conn=6037539) Client does not support authentication protocol requested by server; consider upgrading MySQL client
Mariadb Client I am using:
<dependency>
<groupId>org.mariadb.jdbc</groupId>
<artifactId>mariadb-java-client</artifactId>
<version>3.1.0</version>
</dependency>
Connection String:
jdbc:mariadb://myremoteserverhost:3306/MY_DATABASE
driver-class-name: org.mariadb.jdbc.Driver
I am using a spring boot application using maven as a build tool.
Can anyone help me solve this why the spring boot application using the mentioned jdbc client cannot make a connection to the database.
I am expecting a successfull connection made to the database

How/Can I specify the version of the SQL Server Native Client OLE DB (SQLNCLI) in the connection string

I know that using the OLEDB Driver (MSOLEDBSQL) I can specify this with the Driver keyword as documented here.
Can this be done with the SQLNCLI driver?
MY ISSUE:
I see on the target machine that both version 10 and 11 are installed and we are getting the following error, that I suspect is due an disabling of tls1.1.
System.Data.SqlClient.SqlException: A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)
It looks like you can't.
I had the v10 version of the SQLNCLI driver uninstalled and everything seems to be working.

DAL01013: Cannot connect to server

I'm trying to connect to DB2 db but getting the error:
DAL01013. Cannot create connection to server 'Unknown server' due to the following: [jcc][t4][2034][11148][3.69.24] Execution failed due to a distribution protocol error that caused deallocation of the conversation.
A DRDA Data Stream Syntax Error was detected. Reason: 0x3. ERRORCODE=-4499, SQLSTATE=58009
Assume it's something with my system. I cannot connect neither via DataStudio nor via QMF. Other users from other system can. I use same jdbc drivers. My system is Windows 7.
Is there anything else I need to adjust on my system?
Personal repository needs to be created first:
https://developer.ibm.com/answers/questions/470013/error-when-trying-to-connect-to-db2-vis-qmf/
Generally you get the reason 0x3 from error -4499 out of the IBM JDBC driver when you are connecting to a SSL port, but you have not specified sslConnection=true on your JDBC connection string. You can also get the error if your database name is incorrect (i.e. does not exist on the server), or your JDBC dirver is too old (DB2 JDBC Driver Versions and Downloads Download Fix Packs by version for IBM Data Server Client Packages)
If connecting to Db2 on Cloud, Db2 Warehouse or Db2 Warehouse on Cloud, all you should need is the sslConnection=true as the CA certificate used in these products is part of the Db2 driver package (for recent drivers anyway)
If connecting to Db2 on premise, you can specify your certificate location via the JDBC properties sslCertLocation or sslTrustStoreLocation and sslTrustStorePassword
Common IBM Data Server Driver for JDBC and SQLJ properties for all supported database products
sslCertLocation
Specifies that an application can configure the location of a trusted certificate file. For applications that have the database server certificate, sslCertLocation is the only property that is needed to be configured to instruct IBM Data Server Driver for JDBC and SQLJ to trust the certificate for SSL connections.
This property removes the need to import the certificate into a Java truststore database and related driver configurations.
Error codes issued by the IBM Data Server Driver for JDBC and SQLJ
error codes in the ranges -4200 to -4299, and -4450 to -4499 are reserved for the IBM® Data Server Driver for JDBC and SQLJ.

IBM Mobilefirst 8 with Websphere application server using oob derby database

Installed IBM Mobilefirst 8 server with WAS 8.5.5.12 using Apache derby database.
Facing below error while checking connection of datasource which are created for mobilefirst server :
java.lang.Exception: DSRA8101E: DataSource class cannot be used as one-phase: ClassCastException: org.apache.derby.jdbc.AutoloadedDriver40 incompatible with org.apache.derby.jdbc.InternalDriver
Working fine with mysql database.
While this message would normally indicate that a data source implementation class was specified that does not implement javax.sql.ConnectionPoolDataSource, I don't believe that is the case here based on the classes identified in the exception message. Another possible cause is that multiple copies of the Derby JDBC driver are on the classpath at the same time. It should be noted that WebSphere Application Server traditional ships a copy of the Derby JDBC driver. If you do have two copies, is it possible to switch to only using the one that is shipped with the application server? If that is not possible, you might be able to work around this by selecting the option to isolate your JDBC provider.
For use with MFP 8.0 standalone server with Websphere Application Server 8.5.5.5, use DB2,MySQL or Oracle