Our application is using JDK7, websphere and is hosted on AIX box.
Recently we upgraded to oracle 19c from 12c. After this, application server does not start.
We do not see any error in startup logs. All application modules do not load, hence server does not come up.
We tried commenting all unnecessary modules in ILSStartupDef.xml, but same issue.
JDBC jar that we are using is ojdbc7-12.1.0.2.0-p0.jar.
Can someone please help ? Any config changes that we may be missing ? We dont want to upgrade to java8 unless its absolutely necessary.
Can you confirm that the database connexion test on the console is working properly ?
Note : Upgrading to Java 8 can be challenging, but Java 7 is no more supported.
Based on this document from IBM :
https://www.ibm.com/support/pages/websphere-application-server-support-policy-jdbc-databases-and-drivers
That being said, yes we do support Oracle 18C and 19C in WebSphere Application Server 8.5.5.X and V9.0.x but you must aware of this following.
We dont test WebSphere Application Server with each and every release of Oracle database. Please make sure you do the test before moving to production.
I believe the oracle 18C or later driver supports java 8 or later release only, if so please make sure WAS java level is also java 8. Java 8 is supported in 8.5.5.9 or later release.
If you ever see this issue, please consider upgrading WAS and do the test again. This issue is fixed in 8.5.5.13 or later release.
Good Luck
From Oracle perspective, please check this post :
Oracle 19c compatibility with jdk7
According to the Oracle JDBC FAQ (Question "What are the Oracle JDBC releases Vs JDK versions?"), only the Java versions you listed (Java 8 to 11) are supported for Oracle 19c.
I would advise to do the assessment for migrating to Java 8, using Transformation Advisor.
Good Luck
If you have upgraded the database server version to 19c then, it is recommended to upgrade the JDBC driver to the same version. So, you should use 19c JDBC driver.
19c JDBC driver requires JDK8 or JDK11. So, it is time to upgrade the JDK version as well as the JDBC driver as well.
Related
There is any chance to connect to an oracle DB 19c with java 6?
I see that the connector is only compatible with jdk8
Whats happens if i use ojdbc6 for connect to a oracle DB 19c?
Thanks
Use Oracle 18 ojdc6.jar. Oracle Database JDBC is compatible with multiple previous and later versions of the database. In particular the 18 version of JDBC is compatible and fully supported with the 19 database.
Based on the Oracle JDBC FAQ the release 19c can be used with
ojdbc10.jar with JDK10, JDK11
or
ojdbc8.jar with JDK8, JDK9, JDK11
What happens if you use a lower JDK version?
Simple try, I assume you will see an exception while trying to connect Exception: Connection refused ...
otherwise (source is same as above) If it is not listed in the above table then please check with your support channel to check if you are still on the support contract for the older versions.
We are running Grails 2.3.11 on JRE 1.8_211. We have Hibernate version - 3.6.10.6.
When we were working with Oracle 11, it was working fine but when I upgrade to 12.2C, we get following error:-
org.codehaus.groovy.grails.orm.hibernate.exceptions.CouldNotDetermineHibernateDialectException: Could not determine Hibernate dialect for database name [Oracle]!
On reverting back to Oracle 11, the issue gets resolved.
Can anyone please suggest a solution for migrating my application to Oracle 12.2C.
We had not specified the hibernate dialect in one of the datasources in datasource.groovy.
It seems that in oracle 12C, it is mandatory to specify the dialect for each data source even though it is not mandatory for Oracle 11g.
Hence, during migrating from Oracle 11g to Oracle 12C, please add verifying that dialects are explicitly specified in your checklist.
Hope this helps others.
We are migrating applications from Websphere 8.5.5.2 to 8.5.5.11 with JDK 8.
We connecting 3 different databases Oracle,DB2,Sybase and currently using following drivers for the same.
DB2: db2jcc.jar,db2jcc_license_cu.jar,db2jcc_license_cisuz.jar
Oracle: ojdbc14.jar
Sybase:jconn4.jar
Dose this drivers will support JDK 8 or do we need to use different version of jars. We are bale to connect DB with this jars in WAS-8.5.5.11 but does this cause any connection issues when load was high.
To support Java-8 with Db2 jdbc , it is best to use a recent version of the Db2-driver files, at least higher than V10.5-fixpack7 or higher.
To learn which jdbc-driver-version gets supplied with which Db2-client version, check here. You can download latest drivers from that page (IBM registration required).
Looking at various Oracle doc (cited below) it looks like you should plan to move up to a newer version of the Oracle JDBC driver for Java 8.
Regarding ojdbc14.jar which you were using, Oracle documentation states that it is for JDK 1.4 and JDK 1.5
On the Oracle JDBC faq, under the section titled "What are the Oracle JDBC releases versus JDK versions?" it indicates to use ojdbc6, ojdbc7, or ojdbc8 with Java 8 depending on which Oracle database version you have.
I am trying to connect the Oracle Express Edition 11g through Grails 3.1.8. I tried all possible solutions:
Downloaded the jar file(ojdbc14.jar)
Adding a pom.xml to my sample application.
Searched the entire web for solution.
I was not able to achieve the connectivity between Grails3.1.8 and Oracle.
The only error I see is:
https://repo.grails.org/grails/core/com/oracle/ojdbc14/10.2.0.4.0/ojdbc14-10.2.0.4.0.jar (Use --stacktrace to see the full trace
Always use the latest JDBC driver in your application. JDBC driver is backward compatible with lower versions of the database. You can download the latest drivers from this path.
We are facing one scenario where our application is hosted on the shared JBOSS server where other application are using oracle 11g and require to use 'ojdbc14.jar'
Where in our application DB is upgraded to 12c and we need to use 'ojdbc5.jar'.
Now issue is it conflicting and we need a solution to have both the jars and still not impact other application.
For now DBA helped us with sqlnet.ora but they are still recommending to upgrade the drivers.