I had manager who inspired confidence by asking, “If you don’t have confidence in yourself, then who will?”
At the same time, overconfidence precedes carelessness and the mistake humbles us.
So there I was, applying patch 14351543 for Oracle Solaris on x86-64 (64-bit) and patching completed successfully.
Verifying the update... Patch 14351543 successfully applied Log file location: /u01/app/oracle/product/11.2.0.3/dbhome_1/cfgtoollogs/opatch/14351543_Sep_05_2012_08_44_45/apply2012-09-05_08-44-44AM_1.log OPatch succeeded.
Starting the listener error. Uh Oh!
> lsnrctl start ld.so.1: lsnrctl: fatal: libclntsh.so.11.1: open failed: No such file or directory Killed
It’s a good thing Oracle has a rollback feature, but completed with warning.
RollbackSession removing interim patch '14351543' from inventory -------------------------------------------------------------------------------- The following warnings have occurred during OPatch execution: 1) OUI-67200:Make failed to invoke "/usr/ccs/bin/make -f ins_rdbms.mk irenamedg ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/dbhome_1"... .'ld: fatal: library -lclntsh: not found ld: fatal: File processing errors. No output written to /u01/app/oracle/product/11.2.0.3/dbhome_1/rdbms/lib/renamedg make: Fatal error: Command failed for target `/u01/app/oracle/product/11.2.0.3/dbhome_1/rdbms/lib/renamedg' ' 2) OUI-67124:Re-link fails on target "irenamedg". -------------------------------------------------------------------------------- OPatch Session completed with warnings. Log file location: /u01/app/oracle/product/11.2.0.3/dbhome_1/cfgtoollogs/opatch/14351543_Sep_05_2012_08_54_03/rollback2012-09-05_08-54-03 AM_1.log OPatch completed with warnings.
Listener and database started up okay. In addition, Oracle support provided instructions to relink all, reviewed the log file and found to be okay.
In the future, to prevent single point of failure, clone Oracle home.
My notes for cloning Oracle home thanks to references from FRITS HOOGLAND WEBLOG: http://bit.ly/RLmeCo
