Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel6
outlinefalse
typelist
printablefalse

...

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

:  

Scenario in Oracle Snaps

Scenario

Error from the Old Oracle Driver

Error after from the latest Oracle Driver and post JOOQ upgrade

Oracle - Insert: For the insert operation, when

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 Please address the reported issue.>Aravind Koonapureddy (Deactivated) - Can you update the resolution for this msg as follows:
<Provide a valid integer value in the input data.>

Oracle - Execute,

Oracle - Insert, and

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 - Insert,

Oracle - Execute, and

Oracle - Update:

When the delete, execute, insert, and update , and execute 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 the insert operation fails.

Case 1:Insert batch records into non-not null column type- one record specified with null value to fail and route to error view.Case 1:The errors are the same in both drivers, but the reason is repeated twice inolder drivers.Oracle - Execute and Oracle - Insert:Batch operation when

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

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

Reason: ORA-01400: cannot insert NULL into (&quot;PRASANNA$#&quot;.&quot;ORACLECHAR_NOTNULL&quot;.&quot;COLUMN1&quot;) , error code: 1400, SQL state: 23000, next exception: ORA-01400: cannot insert NULL into (&quot;PRASANNA$#&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,when an error record 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 when there is an error record 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 and

Oracle - Insert:

Batch operation when the Auto Commit checkbox isDeselected.

Error: 'Batch operation failed'

In the old version,when an error record 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 record 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

Oracle to SQL Server: If you select the Create a table if not present checkbox.The Snap is unable to create a table with correct data types.

Displays data type as DECIMALfor numeric columns.

New driver displays data type as "NUMERIC" instead of "DECIMAL"

Oracle to Oracle Snaps: The Oracle Select snap with a second output view with and without table data.

Oracle to Oracle Snaps: If you select the Create a table if not present checkbox, the Snap is unable to create tables with proper datatypes.

Oracle - Execute:

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

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

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 condition contains special characters:"{reason=.

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

"{reason=Error code: 1740

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

FAQ for Upgrading from Oracle JDBC 11.2.0.4 Driver to 19.20.0.0 Driver

...

What is the timeline for this upgrade?

This upgrade is will be available as a stable upgrade for on November 8, 2023, while you can have an early preview available shortly after the August October 2023 GA release.

Will I be impacted?

...

You do not have to reconfigure your account settings or drivers; the account can remain as-is to work with the latest driver. However, if you currently use the default version and wish to revert to the previous version behavior, we recommend you to use the OJDBC6 JAR.

How do you override the behavior changes?

...