SQL exception with ojdbc8 Jar

[Abhishek Rath]

Hi

  When I change the POM to use ojdbc8 Jar then I am getting the below error

2017-08.18 04:42:02.647-0700: ERROR: Failed to create status log entry: org.springframework.jdbc.UncategorizedSQLException: PreparedStatementCallback; uncategorized SQLException for SQL [INSERT INTO table name (s_id, f_id, p_id, t_type, d_addr, st, desc, f_size) VALUES (88568, ?, ?, ?, ?, ?, ?, ?)]; SQL state [99999]; error code [17068]; Invalid argument(s) in call; nested exception is java.sql.SQLException: Invalid argument(s) in call
2017-08.18 04:42:02.647-0700: CAUSE: org.springframework.jdbc.UncategorizedSQLException: PreparedStatementCallback; uncategorized SQLException for SQL [INSERT INTO table name (s_id, f_id, p_id, t_type, d_addr, st, desc, f_size) VALUES (88568, ?, ?, ?, ?, ?, ?, ?)]; SQL state [99999]; error code [17068]; Invalid argument(s) in call; nested exception is java.sql.SQLException: Invalid argument(s) in call
org.springframework.jdbc.UncategorizedSQLException: PreparedStatementCallback; uncategorized SQLException for SQL [INSERT INTO QA_DF_OWNER.df_statuslog (stl_id, feed_id, partner_id, trans_type, dest_addr, status, description, file_size) VALUES (88568, ?, ?, ?, ?, ?, ?, ?)]; SQL state [99999]; error code [17068]; Invalid argument(s) in call; nested exception is java.sql.SQLException: Invalid argument(s) in call
       at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:83)
       at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:80)
       at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:603)
       at org.springframework.jdbc.core.JdbcTemplate.update(JdbcTemplate.java:843)
       at org.springframework.jdbc.object.SqlUpdate.update(SqlUpdate.java:188)

Caused by: java.sql.SQLException: Invalid argument(s) in call
       at oracle.jdbc.driver.AutoKeyInfo.getNewSql(AutoKeyInfo.java:187)
       at oracle.jdbc.driver.PhysicalConnection.prepareStatement(PhysicalConnection.java:4342)
       at org.apache.commons.dbcp2.DelegatingConnection.prepareStatement(DelegatingConnection.java:807)
       at org.apache.commons.dbcp2.DelegatingConnection.prepareStatement(DelegatingConnection.java:807)

Any clue  what could be the reason?

Regards
Abhishek

   

[Dave Tolls]

What Oracle version are you talking to?

I'm wondering if you have a mismatch between your JDBC driver and your Oracle db.

[Abhishek Rath]

The Oracle DB version is 12.1.0.2.0 SELECT version FROM V$INSTANCE

The Spring Version used here is 3.1.1 .

[Brian Tkatch]

What are the query values, and have you tried running the query directly? With a type mismatch, both the input and output should be looked at.

[Dave Tolls]

This isn't the query.
The error is coming from the prepareStatement call.
(Had a whole reply based on it being from the execution!)

Where did you get the ojdbc8 jar from?
If I go to the Oracle 12 driver download page the driver is 7 (or 6 if you're on an earlier JDK).

[Brian Tkatch]

Dave Tolls wrote:This isn't the query.
The error is coming from the prepareStatement call.
(Had a whole reply based on it being from the execution!)

Good catch, Dave! I need to read those traces more carefully.

[Abhishek Rath]

In the POM file we have it defined

         <dependency>
<groupId>com.oracle</groupId>
<artifactId>ojdbc8</artifactId>
<version>12.2.0.1</version>
</dependency>

The earlier version was

<groupId>com.oracle</groupId>
        <artifactId>ojdbc7</artifactId>
        <version>12.1.0.2</version>
     </dependency>

The JDK is 1.8.

So for this version of Oracle and JDL , do we need to use ojdbc7 not ojdbc8?

[Dave Tolls]

Well, if you look at the link I gave to the Oracle 12 JDBC page that shows you the versions they recommend.

[Abhishek Rath]

Thanks a lot.

[John Doge]

What is your database encoding? Something different than UTF?
Have you seen this https://support.oracle.com/knowledge/Middleware/2278611_1.html ?

PrepareStatement(string, String[]) Failing Due To Upgrade From Ojdbc7 To Ojdbc8 With "java.sql.SQLException: Invalid argument(s) in call" Error

On : 12.2.0.1.0 version, Thin JDBC driver

When using the Oracle JDBC driver to issue a prepared statement that returns auto-generated keys, this operation fails when the NLS_CHARACTERSET on the targeted database is WE8ISO8859P15