Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Overview

The JDBC driver for Oracle in the Oracle Snap Pack is will be upgraded from OJDBC6 JAR JAR (11v11.2.0.4 version) to OJDBC10 JAR (19v19.20.0.0 version) in the latest distribution in October 2023 and in the stable distribution in the November 2023 release (after the Snaplex upgrade). As part of this upgrade, the 19.20.0.0 JDBC driver is bundled with the Oracle Snap Pack as the default JDBC driver.

...

This driver upgrade has resulted in specific behavior changes within the Snap Pack. These changes pertain to status codes and success and failure messages. This table lists these changes:

Oracle Snaps

Scenario

Error from the Old (OJDBC6 JAR—11.2.0.4 version) JDBC Driver

Error from the new (OJDBC10 JAR —19.20.0.0 version) JDBC Driver

Oracle - Insert

When you enter a string value instead of an integer in a numeric column for the insert operation.

Error Message: SQL operation failed.

Reason: ORA-01722: invalid number , error code: 1722, Coracle-Insert ? BH D7 A ® 'SQL state: 42000,

Resolution: Please check for valid Snap properties and input data.

Error Message: Invalid integer: <string>

Reason: The string value is not a number.

Resolution: Please address the reported issue.

Oracle - Execute

Oracle - Insert

Oracle - Merge

When the execute, insert, and merge operations are successful.

Status: "-2"

Message: Batch statement executed successfully, but no count of the number of rows it affected is available.

Status: 1

Message: success

Oracle - Delete

Oracle - Execute

Oracle - Update

When the delete, execute, insert, and update operations are successful.

Status: "-2"

Message: Batch statement executed successfully, but no count of the number of rows it affected is available.

Status: "number of rows impacted"

Message: success

Oracle - Insert

 

When we insert null values into the not null column type.

Insert batch records into not null column type- one record specified with null value to fail and route to error view.

Reason: ORA-01400: cannot insert NULL into (&quot;<table name>$#&quot;.&quot;ORACLECHAR_NOTNULL&quot;.&quot;COLUMN1&quot;) , error code: 1400, SQL state: 23000, next exception: ORA-01400: cannot insert NULL into (&quot;<table_name>$#&quot;.&quot;ORACLECHAR_NOTNULL&quot;.&quot;COLUMN1&quot;) },

The reason is repeated twice with the ‘next exception key inolder drivers.

Reason: ORA-01400: cannot insert NULL into (&quot;<table_name>$#&quot;.&quot;ORACLECHAR_NOTNULL&quot;.&quot;COLUMN1&quot;) , error code: 1400, SQL state: 23000, next exception: ORA-01400: cannot insert NULL into (&quot;<table name>$#&quot;.&quot;ORACLECHAR_NOTNULL&quot;.&quot;COLUMN1&quot;) },

Oracle - Execute

Oracle - Insert

 

Batch operation when the Auto commit checkbox is Selected.

Error: Batch operation failed

In the old version,the entire batch fails when an error occurs during a batch operation, and records are redirected to the error view. As a result, no records are inserted into the database.

Error: SQL operation failed

In the new version, when there is an error in the batch operation, the records before the problematic one are inserted into the database, while the records after it are routed to the error view.

Records are inserted into the table because the Auto-commit checkbox is selected.

Oracle - Execute

Oracle - Insert

Batch operation when the Auto Commit checkbox isDeselected.

Error: 'Batch operation failed'

In the old version,when an error occurs during a batch operation, the entire batch fails and records are redirected to the error view. As a result, no records are inserted into the database.

Error: 'SQL operation failed'

In the new version, if there is an error occurs in the batch operation, the records before the problematic one are inserted into the database, while the records after it are routed to the error view.

Records are not inserted into the table because the Auto-commit checkbox is deselected.

Oracle - Select

When you select a second output view for metadata.

Displays data type as DECIMALfor numeric columns.

Displays data type as "NUMERIC" instead of "DECIMAL"

Oracle - Execute

Insert operation when you pass a spl character( ' ):

Reason: Invalid query: Insert into #TABLE_NAME.COLUMN_NAME# values ('windyi'eee')"

Resolution: Please check for valid Snap properties and input data.

Error code: 17081

Reason: error occurred during batching: ORA-00917: missing comma"

Resolution: Please check for valid Snap properties and input data.

Oracle - Delete

Delete condition contains special characters.

Reason: Syntax error at or near one of single-quotes}"

Error code: 1740

Reason: ORA-01740: missing double quote in identifier, SQL state: 42000}"

FAQ for Upgrading from Oracle JDBC 11.2.0.4 Driver to 19.20.0.0 Driver

...