Oracle 12c 32-bit client and direct GOT relocation R_386_GOT32 against `lxecerr’

When trying to install Oracle 12c 32-bit Client (12.1 or 12.2) on Oracle Linux 7.3 or 7.5, it throws error during linking static libraries:


Not very specific, I found only one reference in Oracle KM Doc ID 2246237.1.

Rootcause and resolution in there was:


SLES 12 SP2 ships with binutils 2.26 which breaks compatibility for certain shared library links.

01) Update binutils package to version binutils-2.26.1-9.15.1 or later.

But in fact, I do have in my server  binutils-2.27-27.base.el7.x86_64 .

Workaround is to downgrade the binutils:

After this, the libs can be compiled and linked:

I do believe that after finishing the installation, binutils can be upgraded again to the latest version (but not forget about this problem in case of installing the RSU).

PS: I’ve raised SR 3-17356002141 : Error when installing Oracle 32-bit client (direct GOT relocation R_386_GOT32 against `ipp_zcalloc’)

Oracle 12c 32-bit client and direct GOT relocation R_386_GOT32 against `lxecerr’
Tagged on:     

5 thoughts on “Oracle 12c 32-bit client and direct GOT relocation R_386_GOT32 against `lxecerr’

  • 2018-04-25 at 17:17

    Hit the exact same problem today. This solution worked for me.

    Awesome! Thanks for posting.

    • 2018-04-25 at 20:58

      I’m glad I could help 🙂 I’ve spent almost two days trying to figure it out so I thought it could help somebody else…

  • 2018-05-08 at 15:22

    I just ran into this issue two days ago. Apparently the update to binutils was in a recent set of patches for RHEL. I found the following Doc ID 2389953.1 on MOS, which has your solution in it, but I wasn’t sure if it also applied to regular database installations as the doc is about EBS applications, but has a single line saying that the downgrade has to be done on all tiers of EBS.

    Thanks for posting this. I’ll have to have all my other database servers downgraded as well.

    • 2018-05-08 at 19:51

      Apparently more people are complaining for this issue. Even the KM article you’ve mentioned was published on the 3rd of May…

      Thanks for this comment!

  • 2018-08-09 at 11:38

    Thank You, you have saved a lot of time for people like me.
    This Solution worked for me.


Leave a Reply

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