According to Metalink:

* cause: This Problem is caused due to and happens when accessing Oracle 9.0.1 Database with JDBC 8.1.7.0.0. This bug is caused by the mismatch between the 9i server and the 8.1.7 Jdbc-Thin clients. <> OERI:ttcgcshnd-1 using JDBC thin pre-9i to 9i database

fix:

You have two alternatives to solve this issue:

1. This is fixed in the JDBC Thin Driver bundled in Database patchset 8.1.7.2
or higher version. This patchset should be applied into the iAS Oracle Home NOT
database Oracle Home.

2. Upgrading the JDBC drivers into the iAS Oracle Home, following the steps in
the note How to Install JDBC Drivers.