we will migrate one application from Oracle 10g to Oracle 11g.
We will not migrate the application Server(WebLogic 10), i would like to know if i need to change the JDBC Version or I can still use the JDBC-Driver from Oracle 10g.
Best Regards
Edney
Related
We are working on the RDBMS Adapter (i.e., to connect to Oracle, MySQL, MSSQL, PostgreSQL, etc) creation. During connecting to Oracle DB we're facing JDBC driver issue for connecting different versions of Oracle Database.
Isn't there any generic driver to connect to what ever the version of Oracle Database it may be?
Like for connecting,
MySQL -> mysql-connector-java
Oracle -> ?
Technology Stack:
Spring Boot
Java 8+ (Planning to go further also)
Angular JS
No, you are supposed to use the right driver for Oracle DB version and Java version. There is no generic driver that fits all combinations e.g. ojdbc6.jar driver does not implement methods introduced in JDBC 4.1+ (Java 7+).
See What are the Oracle JDBC releases versus JDBC specifications? and What are the Oracle JDBC releases versus JDK versions? docs to understand which OJBDC driver you should use.
According to some research about Lagom and Cassandra, I found that:
Lagom uses DataStax Java Driver for Cassandra, and
DataStax Java Driver only supports Cassandra 3.0.x (link)
So, if I want to use Cassandra 3.11 and Lagom, what should I do:
Should I configure Lagom with another Cassandra driver like Achilles, PlayORM, ... (link). Is that possible?
is DataStax support Cassandra 3.11 in the enterprise edition?
Any help, please?
DataStax Java Driver 3.2.0 that is used by Lagom should work with Cassandra 3.11 out of the box (just checked it myself using simple queries).
Even if it won't work out of the box, you can explicitly override driver version in Maven or other build system.
I used quartz 1.6 scheduler with Java application built in 10g technology from Oracle using Jdeveloper 10g as IDE.
The application is working fine with the mentioned technology. But, After migrating the application to 11g technology the quartz scheduler is not working any more. The Weblogic server used to deploy this migrated technology is Weblogic 10.3
----------------Update--------------------
The application works fine from Jdeveloper but when I deploy it on the external weblogic server I the scheduler is simply not working
I have an application deployed on Websphere 8.5.5 using an Oracle 12c db connection and I am not able to login to the application. The error I get is:
java.sql.SQLException: Could not commit with auto-commit set on
at oracle.jdbc.driver.PhysicalConnection.commit(PhysicalConnection.java:4439)
at oracle.jdbc.driver.PhysicalConnection.commit(PhysicalConnection.java:4486)
at oracle.jdbc.OracleConnectionWrapper.commit(OracleConnectionWrapper.java:140)
at com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.commit(WSJdbcConnection.java:1144)
at
Is there a way in Websphere to set this property to false? So far I have tried creating a custom property for the datasources autoCommit = false , type=boolean.
Any ideas? Cheers
There is IBM support page that describe your problem, I hope this help.
IBM support page.
It seems that there is a problem with Oracle 12c drivers.
I was having the same problem here on Websphere Liberty Profile using ojdbc7.jar driver. I've download 11.2.0.3's ojdbc6.jar driver from here, and suddenly, it started working.
I am new to Hibernate.
We are migrating one of our existing web application which uses Hibernate 3 and SQL 2000 server to SQL 2005 server.
Can I get help about which version of Hibernate to use with SQL 2005 as I could not find any dialect for SQL 2005 in Hibernate 3.0.5?
Thanks in advance.
I don't believe that the dialect recognizes the difference between SQL Server years; it's all just Microsoft SQL Server.
Which JDBC driver are you using? Microsoft's or jTDS? You only get the features that the driver supports.
And you shouldn't be using database specific features. Your code isn't portable that way.
I am using the standard SQLServer dialect (org.hibernate.dialect.SQLServerDialect) for SQLServer 2005 and I got no issues so far.
I'm using the JTDS JDBC Driver.
I'm also using the Schema Generator, no problems so far.