Bug #53488 | Jar file installation in oracle database | ||
---|---|---|---|
Submitted: | 7 May 2010 13:25 | Modified: | 11 May 2010 12:47 |
Reporter: | sharmila k | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | Connector / J | Severity: | S2 (Serious) |
Version: | mysql-connector-java-5.1.12-bin.jar | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[7 May 2010 13:25]
sharmila k
[7 May 2010 13:30]
Tonci Grgin
Hi Sharmila and thanks for your report. I do not get it at all... You are trying MySQL connector/J to connect to Oracle server? If so, that is simply not possible.
[7 May 2010 13:37]
Tonci Grgin
Ah well, I got what you're trying to do... Explanation: Our driver is not broken. You will have to figure out how to turn the class verifier off, or remove those classes from the .jar if Oracle's not going to use them. Most likely this is a configuration error on your part. However, we might consider making a package that only includes the driver and no JDBC-4.0 or integration stuff. But when, I can't tell.
[7 May 2010 13:40]
Tonci Grgin
Sharmila, if you know anything in the oracle docs that will disable classloader verification we'll be interested to hear. As for your problem, I opened a separate bug report, Bug#53489.
[11 May 2010 12:47]
sharmila k
Invalid objects created at the time of loading jar file to database. we removed all those invalid objects from the database. Thanks.