Yup, we've faced the same issue. It's caused by wrong/corrupted c-oracle.jar file in the installer directory.
It's interesting why CA didn't replace this file (fixed the installer) yet, as it's available for few months already and this issue is a well known one...
Here is the solution provided for my case when I was playing with the upgrade. It worked for the first installation, and i'm now planning another run this week.
Workaround for 14.2 upgrade
1.
Extract the install.jar in a temp directory
- Take the library "c-oracle.jar" inside ...temp\checkinstall\tools\lib and
copy it inside the folder ..temp\tools\lib replacing the existing one.
- Take the file "upgrade-repack.14.1.0.431tpexcludes.jar" contained in ..temp\install-packages\14.1.0
and unjar it /unzip it (renamed it as upgrade-repack.14.1.0.431tpexcludes.zip to unzip) it in my temp2
directory.
- Take the file "package.jar" contained in above upgrade-repack.14.1.0.431tpexcludes.zip and unzip/unjar the package.jar
and replace the c-oracle.jar in package.zip and rebuild the package.jar and again package as upgrade-repack.14.1.0.431tpexcludes.jar
2.
Take the file "package.jar" contained in ..temp\install-packages\14.2.0
and unjar/unzip (renamed it as package.zip to unzip and extracted) it in another temp2
directory.
- Take the library "c-oracle.jar" inside ...temp\checkinstall\tools\lib and
copy it inside the folder ..temp2\lib replacing the existing one.
- rebuild the package.jar modified and run the install
Have fun