Scenario in Oracle Snaps

Error from the Old Oracle Driver

Error after the Oracle Driver and JOOQ upgrade

Oracle - Insert: For the insert operation, when you enter a string value instead of an integer in a numeric column.

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.>

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, insert, 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-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 in older drivers.

Oracle - Execute and Oracle - Insert: Batch operation when 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 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: Auto Commit checkbox is Deselected.

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

Displays data type as DECIMAL for numeric columns.

New driver 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')"

"reason=error occurred during batching: ORA-00917: missing comma"

Oracle - Delete

Delete_Condition contains special characters:

"{reason=Syntax error at or near one of single-quotes}"

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