This week's book giveaway is in the Agile and Other Processes forum. We're giving away four copies of Darcy DeClute's Scrum Master Certification Guide: The Definitive Resource for Passing the CSM and PSM Exams and have Darcy DeClute on-line! See this thread for details.
Hello. If anybody has a minute, I am converting a server based Domino agent which performs SQL against legacy SQL Server (using jtds.jar) to interfacing with Oracle (thin, ojdbc5.jar). I worked out an issue a few days ago which I posted at javaranch.
I went ahead and completed all the recoding locally, added ojdbc6.jar to the agent and the local jvm/lib/ext and it works ok. Now when I try to move it and run this on the server, adding ojdbc6.jar to jvm/lib/ext on the server, I get...
Error while registering Oracle JDBC Diagnosability MBean...java.security.AccessControlException: access Denied (javax.management.MBeanServerPermissioncreateMBeanServer)
The legacy "parallel" agent with the SQL Server driver (jtds.jar) is running fine and has been for years. The agent has security level set to 2 and signer has permissions in the Server document. The policy file looks good with All Permissions and pointing to jvm/lib/ext. Would anybody know what I am missing here and why the server is ok with jtds.jar and not ojdbc6.jar. As I said, I did all development on my local Lotus Notes and it was fine running there.
I've read where there might have been some kind of patches for ojdbc5.jar and ojdbc6.jar but my ojdbc6.jar, when I run java -jar on it says...
Oracle 188.8.131.52.0-Production JDBC 4.0 compiled with JDK6
I think this version is after all that patching stuff, and it works ok and interfaces with Oracle with none of this access issue when I run on local Lotus Notes.
I don't think your Oracle JDBC driver is the latest version since Oracle 11.1 refers to Oracle 11g Release 1 and Oracle 11g Release 2 has been available for a long time now.
Indeed the latest Oracle database is 12c.
The Oracle Web site has a JDBC FAQ page which shows a compatibility matrix between Oracle database version, Oracle JDBC driver version and java version.
Make sure that in your enviornment everything matches.
In other words you need to find out which Oracle database you are using and which java version you are using and then get the suitable JDBC driver.
Weeds: because mother nature refuses to be your personal bitch. But this tiny ad is willing:
a bit of art, as a gift, the permaculture playing cards