R12 E-Business Suite Autoconfig fails On Windows Database After CPU Apr/Jul/Oct 2016 OJVM Is Applied With Error "java.lang.UnsupportedClassVersionError ... Bad version number in .class file" or "java.lang.NoSuchFieldError: thinJndiLdapConnectTimeout" (Doc ID 2212690.1)

Last updated on JANUARY 03, 2017

Applies to:

Oracle Applications Manager - Version 12.1.3 and later
Oracle Applications Technology Stack - Version 12.1.3 and later
Microsoft Windows x64 (64-bit)

Symptoms

Running Autoconfig on a Windows database fails with either of these 2 errors:

1. If context file s_jretop is set to using JDK 1.5.x delivered with 11gR2 or 12c database under $ORACLE_HOME/jdk/jre, Autoconfig fails with the following error:

Context Value Management will now update the Context file
Exception in thread "main" java.lang.UnsupportedClassVersionError: Bad version number in .class file at java.lang.ClassLoader.defineClass1(Native Method) ...

or

2. If context file s_jretop is set to using JRE 1.6.x or JRE 1.7.x installed under $ORACLE_HOME/appsutil/jre, Autoconfig fails with the following error:

Context Value Management will now update the Context file
Exception in thread "main" java.lang.NoSuchFieldError: thinJndiLdapConnectTimeout at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:1102)

Changes

Either the CPU April 2016 or CPU July 2016 was applied, or the CPU October 2016 on Windows x86-64 database OJVM.

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms