Client Certification for Oracle Database

I’ve received a question about client certification for Oracle Database the other day.
And this reminded me on this very helpful MOS Note:

It spans the client interoperability back to the Oracle 9.2 days and is a very helpful resource.

Client Certification Oracle Database

And don’t forget that sometimes client software may need a patch as well. A customer I exchange emails with on a regular basis just upgraded the Database server to Oracle Database and saw several strange errors with the JDBC client despite the fact that they were already using the most recent JDBC client.

ORA-904, ORA-923 and ORA-920 were signaled together with:

It turned out that the JDBC client need some patch treatment with merge patch 21623553
on top of the client. It got combined together with some other useful fixes into merge patch 24012252 for the JDBC client:

JDBC Patch for Bug# 24012252 for Generic Platform

Afterwards the errors were gone. For further JDBC client patch recommendations please see:

Furthermore don’t forget that there’s the Instant Client as well which is easy to deploy and downloadable from OTN:

Oracle Instant Client Download OTN


Share this:

4 thoughts on “Client Certification for Oracle Database

  1. And this bug with client on Windows:

    The parameter StrLen_or_IndPtr of the API SQLBindParameter() returns length in characters instead of in bytes. As per specification, it should return length in bytes. This is described in the Bug 21616079

    See: Oracle ODBC Driver Truncates The Data Length of Output Parameter When Data Type is

  2. Actually, when I look up the certification for Oracle Client 12.2 against database versions, this is the list I find on MOS:
    Oracle Database
    Oracle Database
    Oracle Database
    Oracle Database
    Oracle Database
    Oracle Database
    Oracle Database
    Oracle Database
    Oracle Database
    So from this, it seems that Oracle Client 12.2 is still certified with database 11.1 (of course, this db version is in Sustaining Support mode) which contradicts your screenshot (which you also got from MOS, I suppose).
    So looks like MOS made some mistake? or did I interpret it wrong?

    • Benny,

      the MOS note is correct. We SUPPORT only combinations which are supported. At the point when the client got released (I’d guess sometime early 2017) Oracle was already out of bug fixing support. Not sure why CERTIFY shows that an client is certified for use with databases. I can’t answer this.

      See the MOS Note:
      General Policy

      Oracle’s general policy is to test and support each new Oracle release for compatibility with older releases thus:

      Test the NEW client to each OLDER server release where the OLDER release is still covered by Premier Support (formerly Primary Error Correction support) at the time that the NEW version is released.


      Tests between the NEW version and other OLDER releases may be added where Oracle deems it sensible to support interoperability between those releases.

      If you have further doubts, may I please ask to open an SR?


Leave a Reply

Your email address will not be published. Required fields are marked *

* Checkbox to comply with GDPR is required


I agree

This site uses Akismet to reduce spam. Learn how your comment data is processed.