All geek questions in one place

Updating the driver to ojdbc7.jar gives an error for oracle / security / pki / OraclePKIProvider

I used to use ojdbc14.jar and now I want to upgrade it to ojdbc7.jar to support oracle12c.

But when connecting the server, an error appears for "oracle / security / pki / OraclePKIProvider".

If I add oraclepki.jar to the class server, it starts correctly without any errors.

I am trying to find out what is added to ojdbc7.jar, that his request to add oraclepki.jar, as with ojdbc14.jar, he never asked me to add oraclepki to my class path.

Does anyone know what changes with ojdbc7 cause this error and what can be done to not add oraclepki to the classpath?

+6
source share
2 answers

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

-XX:-UseSplitVerifier

+3
source

This is a problem recorded in the Oracle Support database. If you have Oracle support, you can learn more. If not...

As Joseph Carroll claims, removing -XX:-UseSplitVerifier from your command line. Java arguments may solve your problem. The UseSplitVerifier argument basically says that Java uses an earlier, less strict byte code verifier (which was sometimes used to get older byte code toolkits to work when upgrading from Java 6 to Java 7). Unfortunately, this caused some problems when upgrading some tools from Java 7 to Java 8. Other things you can do include (for Oracle):

  • Go to the java 7 compatible bytecode toolkit.
  • Or, as a workaround, include oraclepki_121020.jar in the classpath. This is a valid workaround when switching to a java 7 compatible bytecode toolkit is not possible.

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

0
source

Source: https://habr.com/ru/post/987475/

More articles:


All Articles