Double check that
a) you only have one oracle JDBC driver (I've seen many customers add in sqljdb*.jar and forget to remove their old ojdbc8)
b) that the JDBC driver version matches (or is compatible with) the SQL client version. Again, customers often upgrade their driver and forget to copy the new jar file into cognos.
------------------------------
ROBERT WRIGLEY
------------------------------
Original Message:
Sent: 09/14/26 02:15 AM
From: German Rodriguez
Subject: ORACLE JDBC Errors
Hi Robert,
Thank you for the ideas.
I already have a full Ora Client installed and it works fine with the descriptor used for the JDBC part. I'll works with our DBAs so.
Thank you for your ideas.
Best regards,
German
------------------------------
German Rodriguez
------------------------------
Original Message:
Sent: 09/13/26 10:01 AM
From: ROBERT WRIGLEY
Subject: ORACLE JDBC Errors
OCI means that the JDBC driver will attempt to load client side files from the local client install to facilitate the connection.
Thin means that the JDBC driver will do all the work.
Thin works here because you are providing all the information it needs to connect (hostname and port) as opposed to using something like a tns name (which would require the driver to reference and load the local tnsnamea.ora, etc). But if it fails "occasionally", that means that something about the connection is requiring local driver files for specific calls.
The short solution is to install and configure the oracle client (making sure that all the appropriate environment variables are exposed to the Cognos user session).
the longer solution is to talk to an Oracle admin to understand what information/setting the thin client needs for this connection. Could be security or failover related dependencies based on the server config.
------------------------------
ROBERT WRIGLEY
------------------------------