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.
Related
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.
I have created a Service running on Tibco, containing a JDBC-enabled process within it, and tested it successfully. The database server is MySQL, and is hosted remotely. When connecting to the remote DB from the service hosted on my machine, the SQL is executed well, but after building the Tibco EAR file and deploying to another external machine, then trying to access the same remote DB server using the same credentials, the external machine returns the below error upon returning:
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'OPTION SQL_SELECT_LIMIT=DEFAULT' at line 1
So, a few questions:
What could be the cause of the above error, given the DB being accessed is the exact same one, using same SQL query, but from different machines?
Is the JDBC driver used for development compiled as part of the packaged EAR file?
Does the JDBC driver being used in a Tibco Process depend on the Tibco service installed or on the packaged EAR file?
Am asking from a learner PoV as am currently picking up Tibco
It looks like jdbc driver issue. You may have different mysql driver version in tibco designer and BusinessWorks.
You don't need to add jdbc driver to your ear package.
Please note that you can specify mysql driver in your package classpath. In tibco Administrator PackageName->Configuration->ServerSettings->Prepend to ClassPath or Append to Class path.
You can also try to copy the driver from your tibco designer(in BW5 it's in \tibco\bw\5.11\lib\
) to the BusinessWorks classpath
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.
This link explains the new things about WildFly. Under the Migrating The Database Connection -> JDBC Driver the article explains about two ways of using jdbc drivers for the applications. I tried with installing it as a module and it works fine. The problem is which way is better and when it is better, whether deploy it as any other application package or install it as a module?
(I noted that install it as a module is necessary for clustered environment. I am looking for, are there any other reasons?)
I think the correct link to the article you are referencing is this one : http://wildfly.org/news/2014/02/06/GlassFish-to-WildFly-migration/
(The other one does not seem to point to the article you are mentioning)
Below is the interesting part from "Migrating The Database Connection" section you are referencing:
On WildFly, you have two ways of installing the JDBC driver: whether
you deploy it as any other application package or you install it as a
module. You can always choose to deploy the driver, but it’s specially
recommend when you have a cluster environment, since the deployments
are automatically propagated in the server groups.
You may have issues with the deployment if the driver is not
JDBC4-compliant. In this case, installing the driver as a module
solves those issues. The advantage of the JDBC driver as a module is
the possibility of creating a custom WildFly bundle for your
organization. This way, you can repeat exactly the same installation
throughout several machines, preserving the same configuration. This
is perfect for the development environment.
So in this section, the author describes the following advantage:
You may have issues with the deployment if the driver is not JDBC4-compliant. In this case, installing the driver as a module solves those issues.
The following Wildfly documentation describes this also:
Any JDBC 4-compliant driver will automatically be recognized and installed into the system by name and version. A JDBC JAR is identified using the Java service provider mechanism. Such JARs will contain a text a file named META-INF/services/java.sql.Driver, which contains the name of the class(es) of the Drivers which exist in that JAR. If your JDBC driver JAR is not JDBC 4-compliant, it can be made deployable in one of a few ways. (...)
Thus, deploying your driver as a module is easier than deploying it as any other application package in case it is not JDBC-4 compliant. (Because you would have to modify and rebuild your JDBC-4 not compliant jar to deploy it as any other application package)
We have here an application developed using Java EE 5 stack (using JSF, RichFaces, EJB, JPA, Hibernate, JAAS) that runs inside Glassfish 3.1! The thing is we are in need to run it as an installable deploy (actually many deploys =]).
My question is: What can we do to have the smallest footprint for the system?
I've already studied about:
uninstalling thing through upgrade tool (e.g. the admin parts),
run the application using embedded glassfish (but using the already existent domain),
configuring domain.xml to erase features (but at a trial and error way),
found some work on how to configure glassfish for production environment.
But as the system will be used by one user at a time, I would like to listen from you about options in this environment.