Glassfish with Oracle DS - oracle

I am using glassfish 3.1 and configure Oracle Datasource. However, I tried to Ping from glassfish admin console, but hitting an error with oracle.jdbc.pool.OracleDataSource not found. What could be the Issue?

As per http://docs.oracle.com/cd/E18930_01/html/821-2432/gkyan.html - you need to insert Oracle jdbc driver manually as it does not come bundled with Glassfish 3.1 installation. Just put the required jar into domain/lib directory.
Driver jar is downloadable from http://www.oracle.com/technetwork/database/features/jdbc/index-091264.html

Related

ojdbc jar version & DataStoreHelper class in websphere application server 7.x for Oracle 12c

I am working with JDK 7 and Oracle 12c.
In Websphere application server 7.x version,
JDBC provider configurations:
Which version of ojdbc jar i can keep in classpath to support oracle 12c?
DataSource configurations:
Whcih Oracle DataStorehelper class can be kept?
According to the following oracle documentation, you should be using ojdbc7.jar for Oracle 12c
Regarding data store helpers, the latest available one ought to work based on forward compatibility, which is:
com.ibm.websphere.rsadapter.Oracle11gDataStoreHelper

Home Interfaces list not populating when importing client jar in EJB transport OSB 12c Jdeveloper

Until now whenever client jar is imported in OSB Jdeveloper for EJB transport, list of home and remote interfaces is populated.
However working with this client jar EJB 2.1, interface list is not
populated. I have checked the jar, it is valid and contains
interfaces. Also working fine with java code. I am getting:
Invalid Ref instance error in JDeveloper
In Eclipse OEPE, no error message. Not working here also.
What could be the issue?
This is how it looks in JDeveloper, getting Invalid Ref instance error
There seems to be some issue with the EJB Cient jar you are using.
To confirm try with some other client jar, I hope you will not get any issue with that.
Which version of Jdeveloper 12c are you using?
Thanks & Regards,
Tarun

Oracle 12 c RAC connection issue in jboss 4.2.3 through datasource

We were using oracle 11g, in jboss 4.2.3 using datasource xml file .It was working fine.Now we moved to oracle 12 c rac version. we changed the url in datasource xml file but it is giving [org.jboss.resource.connectionmanager.JBossManagedConnectionPool]Throwable while attempting to get a new connection: null
but using same url in jdbc connection using Class. forName(....), It is working proper.
Please help me out , why we are not able to connect through datasource xml file.
our configuration :
jboss 4.2.3
oracle 12c rac
jdk 1.6
ojdbc6.jar
Try adding a new datasource(12c one) from the JBOSS console, rather than doing this manually.

Enable OJDBC Logging on JBoss

I'm facing database connection issue when using ojdbc6.jar. Therefore, I would like to enable logging by using ojdbc6_g.jar.
I am using JBoss AS 7.1.
How to add these Java options:
-Doracle.jdbc.Trace=true
-Djava.util.logging.config.file
Do I have to add to Eclipse or JBoss or Oracle database ? My guess would be Eclipse.
Please help.
the JDBC driver has to be in the classpath of the JBOSS server otherwise JBOSS could not be able to find the oracle Server
this could also be a network issue
also you mix several concept in once line ; weird
so we need more details about your problem, for example errors ; logs etc.

How to override TOMCAT Oracle ojdbc14 driver in the application?

The TOMCAT server is using an Oracle 9G ojdbc14 driver to its jndi connections in the /common/lib folder.
My web application uses Maven + Spring and I'm getting the dataSource using Spring jndi features.
I'm trying to bypass TOMCAT old ojdbc14 driver with a newer one (ojdbc14 10.2.0.4.0).
I've tried putting the jars in the WEB-INF/lib folder as a project dependency, but it doesn't work the application keeps using the old oracle driver that is in the TOMCAT folder.
I'm trying to bypass the TOMCAT oracle driver because I cannot update it to the newest version because there are lots of other projects using it.
Does anyone have a clue?
This won't work, Tomcat won't use the JDBC driver of your webapp to create a connection pool. In other words, you'll have to either replace the version in common/lib or to use a standalone connection pool at the application level.

Resources