CODEWITHSUNDEEP
javaoracle12c
ankur singhal
ankur singhal

Reputation: 61

Driver update to ojdbc7.jar gives error for oracle/security/pki/OraclePKIProvider

I have been using ojdbc14.jar earlier and now want to upgrade it to ojdbc7.jar for supporting oracle12c.

But while connecting server gives error for "oracle/security/pki/OraclePKIProvider".

If I add oraclepki.jar to the classpath server starts up properly without any error.

I am trying to figure out what special got added in ojdbc7.jar that its asking me to add oraclepki.jar, As with ojdbc14.jar it never asked me to add oraclepki into my classpath.

Does anyone know what changes with ojdbc7 that's causing this error and what can be done to avoid adding oraclepki on classpath?

Upvotes: 6

Views: 8878

Answers (2)

kc2001
kc2001

Reputation: 5247

This is an issue recorded in the Oracle Support Database. If you have Oracle Support, you can find out more there. If not...

As Joseph Carroll states, removing the -XX:-UseSplitVerifier from your command line Java arguments might solve your problem. The UseSplitVerifier argument basically tells Java to use an earlier, less stringent, byte code verifier (which was sometimes used to get older byte code instrumentation tools to work when upgrading from Java 6 to Java 7). Unfortunately, it caused some problems when upgrading certain tools from Java 7 to Java 8. Other things you might do include (per Oracle):

  1. Upgrade to a java 7 compatible bytecode instrumentation tool.
  2. Or, as a workaround, include oraclepki_121020.jar in the classpath. This is a valid workaround in case upgrading to a java 7 compatible bytecode instrumentation tool is not possible.

This article talks about why -XX:-UseSplitVerifier was added for using Java 7 with Oracle. This article talks about using the –noverify flag with Java 8 instead of -XX:-UseSplitVerifier.

Upvotes: 0

Joseph
Joseph

Reputation: 539

Check your classpath and make sure you remove the following: (if it exists)

-XX:-UseSplitVerifier

Upvotes: 3

Related Questions