Comments on: Configuring a (Oracle) datasource on Glassfish

By: Leonardo Derks

Leonardo Derks — Mon, 05 Dec 2011 23:31:32 +0000

tank u man, exactly what i needed

By: Michele A Smith

Michele A Smith — Fri, 19 Nov 2010 14:50:45 +0000

Hi I found your article extremely helpful, and I am so grateful for it,Â however, as a newby I needed more information on the .jar files.Â Â The following would be my revisions. For instance, http://www-01.ibm.com/support/docview.wss?uid=swg21330098Â discusses the differences between the driver you mention in your article ending in 14.jar and the newer drivers for folks using the newer updates of JDK (Java Developers Kit) and also for Oracle, whether they are using 10g or 11 g. Also one of the Glassfish links is broken on the blog you created now. The best advice I can give anyone trying to adapt their solution to your great and wonderful and prosaic knowledge is to realize that your driver has to be the same JDK as what you have installed, meaning if you installed JDK 1.6, you have to stay with 1.6, if you installed 1.5 you have to stay with 1.5 and if you installed 1.4 you have to stay with 1.4, and also when they go to the Oracle JDBC drivers download page located here: http://www.oracle.com/technetwork/indexes/downloads/index.html They need to realize that when they download the .jar file associated with the right Oracle and the right JDK version they are running, that you DO NOT EXTRACT the file!Â Just put the file in the target directory. AGAIN DO NOT EXTRACT!!!! One other issue in the article that I feel should be addressed is that there is aÂ CLASSPATH variable that has to be set, you can call it CLASSPATH_WHATEVER or JAVA_CLASSPATH, but it has to point to the jarÂ file. Â

By: saket jha

saket jha — Wed, 06 Jan 2010 19:17:29 +0000

Helped, Thanks.

By: Bertan

Bertan — Fri, 05 Jun 2009 14:18:38 +0000

I did the same configuration as you mention above. But I dont know why when I ping I get the error “ORA-00604: error occurred at recursive SQL level 1 ORA-12705: Cannot access NLS data files or invalid environment specified”…

Enviroment is
Oracle Database 10g Express Edition Release 10.2.0.1.0 – Product
PL/SQL Release 10.2.0.1.0 – Production
CORE 10.2.0.1.0 Production
TNS for 32-bit Windows: Version 10.2.0.1.0 – Production
NLSRTL Version 10.2.0.1.0 – Production
Win Xp Sp3

And The Locale is tr_TR.

thanks

By: Aryan

Aryan — Wed, 23 Jul 2008 07:38:18 +0000

Thanks, It helped me.
Aryan

By: Khaled Mahmoud

Khaled Mahmoud — Fri, 19 Oct 2007 22:52:15 +0000

Very useful article. Thanks a lot.

By: E Pitt

E Pitt — Fri, 17 Aug 2007 04:34:30 +0000

Love your work

By: Alfred Huang

Alfred Huang — Mon, 09 Jul 2007 23:30:13 +0000

Good posting. I really followed your description and solved my problem.

By: Craig Cruden

Craig Cruden — Fri, 01 Jun 2007 06:58:00 +0000

Followup, I copied the newest driver back, and did a ping. Came back with the same error related to ConnectionCachingEnabled. I compared the properties between work and home, and noticed it is not a property at work (old driver). I deleted the "ConnectionCachingEnabled" which was "false". It then came up with another error related to FastConnectionFailoverEnabled. I then deleted "FastConnectionFailoverEnabled" which also was false, and tried ping again. Ping succeeded.

By: Craig Cruden

Craig Cruden — Fri, 01 Jun 2007 06:09:44 +0000

James, I was getting the same problem. I think it has something to do with the new Oracle JDBC driver and glassfish (or at least the configuration). I had setup glassfish at work and it pinged correctly. At home I copied a local (newer version) of ojdbc14.jar and was getting that error. I then copied a newer version down from Oracle — and that one failed (both over 1,500,000 in size – or close to it). I could not see any difference in configuration – so I copied the ojdbc14.jar from my work computer (size 1,200,046), and it worked (the ping). I suspect that the older driver is probably going to kick me later, but it was the only one that I got working. I am wondering if some of the EJB3 updates that they added — does not allow a certain attribute to be updated (for whatever reason).