| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Overview
The JDBC driver for the Oracle Snap Pack is upgraded from OJDBC6 JAR (v11.2.0.4) to OJDBC10 JAR (v19.20.0.0) in the latest distribution in October 2023 and will be deployed 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.
FAQ for the Oracle JDBC Driver Upgrade
What is happening?
The Oracle JDBC Driver is upgraded from OJDBC6 JAR (11.2.0.4 version) to the OJDBC10 JAR (19.20.0.0 version). The OJDBC10 JAR is bundled with the Oracle Snap Pack as the default driver.
Why are we upgrading the Oracle driver?
The decision to upgrade the Oracle JDBC driver from version 11.2.0.4 to 19.20.0.0 is made to improve security, performance, stability, and reliability. Oracle Database 19c offers significant enhancements, bug fixes, and new features unavailable in the 11g version. Upgrading to 19.20.0.0 ensures continued support and compatibility with modern systems and provides a more efficient and secure database environment.
What is the timeline for this upgrade?
This upgrade is available as a stable upgrade on November 8, 2023.
Will I be impacted?
Yes, if you use the default version, you will be impacted. The impact might be minimal if you use the latest driver or a higher version than 19c.
To check the version of the current JAR file that you are using, refer to https://www.oracle.com/database/technologies/appdev/jdbc-drivers-archive.html.
To know the JAR file that is in use, follow these steps:
Open the JAR file using a ZIP utility or a JAR viewer tool.
Look for the
META-INF/MANIFEST.MFfile in the JAR and check the version.
Do I need to reconfigure my accounts?
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 want to revert to the previous version behavior, we recommend you use the OJDBC6 JAR.
How do you override the behavior changes?
Use the OJDBC6 JAR from the 11.2.0.4 version to maintain the same behavior as before the driver upgrade:
...
Behavior Changes
This driver upgrade has resulted in specific behavior changes within in the Snap Pack. These changes pertain to are for status codes and success and failure messages. This table lists these changes:
Oracle Snaps | Scenario | Error/Output from the Old (OJDBC6 JAR—11.2.0.4 version) JDBC Driver | Error/Output from the new (OJDBC10 JAR —19.20.0.0 version) JDBC Driver |
jOOQ upgrade change: When you use a stored procedure. | Output message:
| Output message:
| |
When the insert and merge operations are successful. | Output message:
| Output message:
| |
When the delete and update operations are successful. | Output message:
| Output message:
| |
When you enter a string value instead of an integer in a numeric column for the insert operation. | Error message: Reason: Resolution: | Error Message: Reason: Resolution: | |
| When we you insert null values into the not null column type. | Error message:
Reason: The reason is repeated twice with the ‘ | Reason: |
| Batch operation when the Auto commit checkbox is Selected. | Error message: 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 message: In the new version, when there is if an error occurs in the batch operation, the records before the problematic one are inserted into the database, while and the records after it are routed to the error view. Records are inserted into the table because the Auto-commit checkbox is selected. |
Batch operation when the Auto Commit checkbox isDeselected. | Error message: 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 message: 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 and the records after it are routed to the error view. Records are not inserted into the table because the Auto-commit checkbox is deselected. | |
When you select a second output view for metadata. | Displays the data type as | Displays data type as | |
Insert operation when you pass a spl character ( ' ): | Reason: Resolution: | Error code: Reason: Resolution: | |
Delete condition contains special characters. | Reason: | Error code: Reason: |
FAQ for Upgrading from Oracle JDBC 11.2.0.4 Driver to 19.20.0.0 Driver
What is happening?
The Oracle JDBC Driver is upgraded from OJDBC6 JAR (11.2.0.4 version) to the OJDBC10 JAR (19.20.0.0 version). The OJDBC10 JAR is bundled with the Oracle Snap Pack as the default driver.
Why are we upgrading the Oracle driver?
The decision to upgrade the Oracle JDBC driver from version 11.2.0.4 to 19.20.0.0 is made to improve security, performance, stability, and reliability. Oracle Database 19c offers significant enhancements, bug fixes, and new features unavailable in the 11g version. Upgrading to 19.20.0.0 ensures continued support and compatibility with modern systems and provides a more efficient and secure database environment.
What is the timeline for this upgrade?
This upgrade will be available as a stable upgrade on November 8, 2023, while you can have an early preview available shortly after the October 2023 release.
Will I be impacted?
If you are using the default version, you will be impacted. The impact may be minimal if you utilize the latest driver or a higher version than 19c.
To check the version of the current JAR file that you are using, refer to https://www.oracle.com/database/technologies/appdev/jdbc-drivers-archive.html.
To know the JAR file that is in use, follow these steps:
Open the JAR file using a ZIP utility or a JAR viewer tool.
Look for the
META-INF/MANIFEST.MFfile within the JAR and check the version.
Do I need to reconfigure my accounts?
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 use the OJDBC6 JAR.
How do you override the behavior changes?
Use the OJDBC6 JAR from the 11.2.0.4 version to maintain the same behavior as before the driver upgrade.
...