Hi,
We have the same issue. It is related to to the fact that there are two different oracle drivers in the package. CA already raised a bug for this. We managed to do the installation by copying the right driver. Also look to the setting for case sensitive in the database. We also had success by setting this to true, which is the default.
Here an extract from our case:
Next to that we also found 2 different versions of the jar file that
contains the java class that is responsible for the connection to the
database. The one in the checkinstall utility differs from the one in the
installation itself.
File with Oracle driver is c-oracle.jar on the following locations:
%install-dir%/tools/lib
2152668 Sep 19 10:06 c-oracle.jar
%install-dir%/checkinstall/tools/lib
2071808 Aug 28 15:30 c-oracle.jar
The internal dates of the two files are 21-01-2014 and 25-10-2012
%install-dir% is the directory where you unpacked the install.jar file from
the installation DVD and where the install.sh file is located to start the
actual upgrade process.
Just as a test we copied the c-oracle.jar file from %install-dir%/tools/lib
to %install-dir%/checkinstall/tools/lib and ran the checkinstall utility
again. The checkinstall utility now also fails at the first check on the
database connection. This demonstrates the issue that I face since the
beginning but it seems that we found the cullprit that is responsible for
the different behaviour.