Ons.jar (48,492 bytes) - for use by the pure Java client-side Oracle Notification Services (ONS) deamon.ĭemo.tar (604,160 bytes) or demo.zip (529,267 bytes) - contains sample JDBC programs. This jar file replaces the old nls_charset jar/zip files. Ojdbc14dms_g.jar (1,940,478 bytes) - same as ojdbc14dms.jar, except that classes were compiled with "javac -g" and contain some tracing information. Ojdbc14dms.jar (1,548,006 bytes) - same as ojdbc14.jar, except that it contains additional code`to support Oracle Dynamic Monitoring Service. Ojdbc14_g.jar (1,932,834 bytes) - same as ojdbc14.jar, except that classes were compiled with "javac -g" and contain some tracing information. Ojdbc14.jar (1,540,457 bytes) - classes for use with JDK 1.4 and 1.5 Oracle Database 10 g Release 2 (10.2.0.2) JDBC DriversĬlasses12.jar (1,594,191 bytes) - for use with JDK 1.2 and JDK 1.3Ĭlasses12_g.jar (2,038,127 bytes) - same as classes12.jar, except that classes were compiled with "javac -g" and contain some tracing information.Ĭlasses12dms.jar (1,601,843 bytes) - same as classes12.jar, except that it contains additional code`to support Oracle Dynamic Monitoring Service.Ĭlasses12dms_g.jar (2,046,467 bytes) - same as classes12dms.jar except that classes were compiled with "javac -g" and contain some tracing information.
#Oracle jdbc jar download 10g driver#
re-download the driver or patch) and I guess most of us will not spend some time for code digging to know what is the root cause behind the problem.Back to Java in the Database, JDBC and Database Web Services page
As usual, what we have in our mind when facing this kind of issue is to do some research through websites and possible solutions (e.g. I admitted that this is the first time I encountered a workaround which requires code implementation to resolve a problem which related to JDBC driver. I personally feel his workaround is really interesting because the suggested solution is from the code implementation. Besides of mentioning on his detailed investigation to figure out the root and cause of this bug, he even mentioned on his workaround to resolve this bug.
#Oracle jdbc jar download 10g Patch#
You can either download the patch from the Oracle site for the Oracle Database 11g, version 11.1.0.6 or switch it to Oracle 10g.Īnyway, the most important thing that I want to mention here is about a blog that discussed the root and cause on how Oracle 11g Release 1 failed to be implemented with the Tomcat. There are several suggested workarounds that you can try and check whether it works on you. The biggest probability of this problem happens is when you are using Oracle 11g with the Tomcat application server. : Invalid character 'Īt (ObjectName.java:602)Īt .(ObjectName.java:1403)Īt .registerMBeans(OracleDriver.java:303)Īt $1.run(OracleDriver.java:213)Īt (Native Method)Īt .(OracleDriver.java:209)Īt 0(Native Method)Īt (Class.java:169)Īt .(BasicDataSource.java:1130)Īt .(BasicDataSource.java:880) SEVERE: Error while registering Oracle JDBC Diagnosability MBean. How do you know this error is related to Oracle 11g? If you are using the Oracle 11g Release 1 (11.1.0.6.0) JDBC driver (ojdbc6.jar), you will see the following errors in the log file:. It seems there is a well-known bug for Oracle Database 11g release (Oracle 11.1.0.6.0) and it has been discussed in the Oracle forum post: SEVERE: Error while registering Oracle JDBC Diagnosability MBean
0 kommentar(er)
