Dear Readers,

Trust you are doing well.

Today, I will discuss key considerations if you’re planning to apply the Oracle Database 19c Release Update (DBRU 19.24). If you use products with third-party JDBC drivers, you may experience connection errors after applying this update. However, this issue does not occur with Oracle-provided JDBC drivers.

Common Errors includes:

• ORA-28040: No matching authentication protocol error
• TNS-12637: Packet receive failed
• [Oracle JDBC Driver]Array index out of range: -1
• TNS-12699: Native service internal error

As per MOS note: Non-Oracle JDBC Drivers encounter connection errors after applying the 19.24 DBRU (Doc ID 3044094.1)

After applying the 19.24 database release update, several third-party products using third-party JDBC drivers, including IBM Change Data Capture (CDC) and Informatica, experienced connectivity issues. Both IBM and Informatica have released patches to address the compatibility issue. Customers experiencing this issue should contact the vendor directly for assistance and any needed patches.

Oracle made several updates in the recent release update 24 of Oracle Database. Oracle’s normal quality testing activities include validating that these updates would not adversely impact the Oracle-provided JDBC drivers.

However, Oracle does not have the ability to test, certify, or support third-party JDBC drivers or products that use non-Oracle drivers.

We recommend that you either contact the third-party vendor themselves and determine whether they can provide a fix for their third-party driver that would enable continued compatibility with current versions of Oracle Database, or encourage those vendors to leverage the Oracle-provided JDBC drivers.

To prevent these issues, I strongly recommend replacing any third-party JDBC drivers, such as CDC or DataDirect, with Oracle JDBC drivers. After making this change and thoroughly testing in lower environments, you can safely apply the Oracle Database 19c Release Update (DBRU 19.24) from July 2024.

Let me know for any questions and any further information in comments or LinkedIn.

Regards
Adityanath.