Jul 21

July 2016 PSU fails to make isqora

When applying the latest PSU, I recieved the following errors from my “opatch apply” session:

 

Patching component oracle.odbc.ic, 12.1.0.2.0...
Make failed to invoke "/usr/bin/make -f ins_odbc.mk isqora 
   ORACLE_HOME=/u01/app/oracle/product/12.1.0.2"....'/usr/bin/ld: cannot find -lodbcinst
collect2: error: ld returned 1 exit status
make: *** [/u01/app/oracle/product/12.1.0.2/odbc/lib/libsqora.so.12.1] Error 1

The following make actions have failed :

Re-link fails on target "isqora".
Composite patch 23054246 successfully applied.
OPatch Session completed with warnings.
Log file location: /u01/app/oracle/product/12.1.0.2/cfgtoollogs/opatch/opatch2016-07-20_23-35-27PM_1.log
OPatch completed with warnings.

 

 

The patch was applied successfully, but the relinking did not work correctly. To fix this, I did the following:

cp $ORACLE_HOME/lib/libsqora.so.12.1 $ORACLE_HOME/odbc/lib/.
relink all

That’s all there was to it.

I did the copy and relink steps because I was trying to fix the error from OPatch. A better way to handle this is to do the copy first, then run ‘opatch apply’ and you won’t get any errors at all.

 

I see that Bug 24332805 was posted for this issue, but I’m not privileged enough to see the contents of that bug.

8 comments

Skip to comment form

  1. I discovered the same error, but my opatch failed and I had to call restore.sh and execute make.txt to start my homes again.. good to know that it can be copied..

    1. As I’ve been applying the PSU to more systems this quarter, I’m just copying the file to the other location and then starting the patching process. I haven’t had any issues since then.

    • Nick on July 27, 2016 at 15:41

    Seems one fix is to install unixODBC and unixODBC-devel rpms prior to patching.

  2. Would that fix it? My initial though is it wouldn’t as the rpm’s are outside of $ORACLE_HOME.

    • Vlad Visan on August 3, 2016 at 15:59

    You can check MOS Notes:
    2136770.1
    2163593.1

    1. Yes. Those notes do address the problem. However, they were not available when I created this post in my blog. Note 2163593.1 only has an “update date” of August 3rd so I can’t prove when that one was actually available. Note 2136770.1 notes that Issue 1.1 was added to the document on August 1st, which was 11 days after this blog post.

      Those MOS Notes are the official records that one should follow. But sometimes, those of us in the community beat Oracle to the punch. 🙂

      Thanks,
      Brian

  3. Really helpful. You saved me the time of chasing this.

      • bpeasland on August 11, 2016 at 10:27
        Author

      Then my quick post was worth it! 🙂

Comments have been disabled.