Applying PSU 12.1.0.2.160719 (Jul2016) for GI and DB Oracle RAC

I was installing the latest Oracle PSU 12.1.0.2.160719 (Jul2016) on 3 node cluster and happen to run into below issues. Do refer the readme file before executing the PSU.


If you need further in details do refer to Apply the latest PSU5 for 12.1.0.2 RAC Database
(http://sajidkhadarabad.blogspot.com/2015/08/apply-latest-psu5-for-12102-rac-database.html) (Scroll down) in my blog .

##############
Issue 1
##############

1. Permission Issue

Applying patch(es) to "/usr/12c/grid" ...
Command "/usr/12c/grid/OPatch/opatch napply -phBaseFile /tmp/OraGI12Home1_grid_patchList -local  -invPtrLoc /usr/12c/grid/oraInst.loc -oh /usr/12c/grid -silent -ocmrf /usr/12c/grid/OPatch/ocm/bin/ocm.rsp" execution failed:
UtilSession failed:
Prerequisite check "CheckApplicable" failed.

Log file Location for the failed command: /usr/12c/grid/cfgtoollogs/opatch/opatch.log

For more details, please refer to the log file "/usr/12c/grid/cfgtoollogs/opatchauto/23273629/opatch.debug.log".

Apply Summary:
Following patch(es) are successfully installed:
DB Home: /usr/oracle/product/12c:

opatchauto ran into some warnings during patch installation (Please see log file for details):
DB Home: /usr/oracle/product/12c: 23054246,23054327

Following patch(es) failed to be installed:
GI Home: /usr/12c/grid: 21436941,23054246,23054327,23054341
Command failure exception

opatchauto failed with error code 2.


Looked in to the log specifications and edited the permission for dropdb.pl from oracle:oinstall to grid:oinstall and run the opatchauto resume.

[root@SajidServer OPatch]# ./opatchauto resume

Have a cup of coffee, till that time it will be completed.

OPatch Automation Tool
Copyright (c)2014, Oracle Corporation. All rights reserved.

OPatchauto Version : 12.1.
OUI Version        : 12.1.
Running from       : /usr/grid

OPatchauto will attempt to resume the last run session. This might take several minutes...

opatchauto log file: /usr/grid/cfgtoollogs/opatchauto/23273629/opatch.deploy.log

Executing command:
/usr/grid/OPatch/opatch napply -phBaseFile /tmp/OraGI12Home1_grid -local  -invPtrLoc /usr/grid/oraInst.loc -oh /usr/grid -silent -ocmrf /usr/grid/OPatch/ocm/bin/ocm.rsp
 as owner "grid"
... above command successful.

Executing command:
/usr/grid/rdbms/install/rootadd_rdbms.sh
 as owner "root"
... above command successful.


OPatchauto was able to resume from the previous patching session and complete successfully.

opatchauto succeeded.

#############
Issue 2
#############

2. Once Patching is completed Listener status will be down in OEM, even if you try to start them manually on the server it will fail with below error.

lsnrctl start listener

LSNRCTL for Linux: Version 12.1.0.2.0 - Production on 28-SEP-2016 02:15:55

Copyright (c) 1991, 2014, Oracle. All rights reserved.

Starting /usr/grid/bin/tnslsnr: please wait...

TNS-12537: TNS:connection closed
TNS-12560: TNS:protocol adapter error
TNS-00507: Connection closed
Linux Error: 29: Illegal seek <<<< here


Update your listener.ora file across all the nodes and bounce the listener on which you are facing the issue.

CRS_NOTIFICATION_LISTENER=OFF
CRS_NOTIFICATION_LISTENER_SCAN1=OFF
CRS_NOTIFICATION_LISTENER_SCAN2=OFF
CRS_NOTIFICATION_LISTENER_SCAN3=OFF

lsnrctl start listener from Grid home.

This has been fixed in Oct2016 12.1.0.2.161018 patch. Please follow Oracle Doc ID (2171506.1).