FOR CRS_HOME:

=============

export PATH=$PATH:$ORACLE_HOME/OPatch:$PATH

1. Verify that the Oracle Inventory is properly configured.

--> opatch lsinventory -detail -oh <CRS_HOME>

2. Unzip the PSE container file

unzip p9348863_11201_AIX.PPC64.zip

As root:

stop crs

/opt/app/oracle/product/11.2.0/grid/bin$sudo ./crsctl stop cluster -n sinupn06

stop has

crsctl stop has

ps -ef|grep d.bin

/opt/app/oracle/product/11.2.0/grid/bin$sudo
/opt/app/oracle/product/11.2.0/grid/crs/install/rootcrs.pl -unlock
#/usr/sbin/slibclean

As the Oracle Clusterware (CRS) software owner, from the directory where the
patch was unzipped;

--> opatch napply -local -oh /opt/app/oracle/product/11.2.0/grid -id 9348863

As root User---

sudo /opt/app/oracle/product/11.2.0/grid/crs/install/rootcrs.pl -patch

opatch lsinventory -detail -oh /opt/app/oracle/product/11.2.0/grid

FOR RDBMS_HOME:
==============

export PATH=$PATH:$ORACLE_HOME/OPatch:$PATH
opatch lsinventory -detail -oh /opt/app/oracle/product/rdbms/sinop01/11.2.0

custom/server/9348863/custom/scripts/prepatch.sh -dbhome
/opt/app/oracle/product/rdbms/sinop01/11.2.0

opatch napply custom/server/ -local -oh

/opt/app/oracle/product/rdbms/sinop01/11.2.0 -id 9348863

custom/server/9348863/custom/scripts/postpatch.sh -dbhome
/opt/app/oracle/product/rdbms/sinop01/11.2.0

opatch lsinventory -detail -oh /opt/app/oracle/product/rdbms/sinop01/11.2.0

# 1. Verify that the Oracle Inventory is properly configured.

#
# % opatch lsinventory -detail -oh <CRS_HOME>
# % opatch lsinventory -detail -oh <RDBMS_HOME>

# 2. Unzip the PSE container file

#
# % unzip p9348863_11201_AIX.PPC64.zip

3.2.1 Stop the CRS managed resources running from DB homes using
#
# % <RDBMS_HOME>/bin/srvctl stop home -o <RDBMS_HOME> -s <status file
# location> -n <node_name>#
# note the status file is created by the process

4. Prior to applying this part of the fix, you must invoke this script
# as root to unlock protected files.
#
# # <CRS_HOME>/crs/install/rootcrs.pl -unlock
#
# Note: In configuration A, invoke this only on one node.

% custom/server/9348863/custom/scripts/prepatch.sh -dbhome <RDBMS_HOME>

#
 % opatch napply -local -oh <CRS_HOME> -id 9348863

# 5. Save the RDBMS home configuration settings

#
# ( Please review section 6.2 first ) As the RDBMS software owner;
# % custom/server/9348863/custom/scripts/prepatch.sh -dbhome <RDBMS_HOME>

# % custom/server/9348863/custom/scripts/postpatch.sh -dbhome <RDBMS_HOME>

#
# Note: In configuration A, invoke this only on one node.

# % opatch napply custom/server/ -local -oh <RDBMS_HOME> -id 9348863

# 8. Now security settings need to be restored on the CRS Home. This script
# will also restart the CRS daemons. Invoke this script as root.
#
# # <CRS_HOME>/crs/install/rootcrs.pl -patch

# % opatch lsinventory -detail -oh <CRS_HOME>

# % opatch lsinventory -detail -oh <RDBMS_HOME>

# % opatch rollback -id 9348863 -local -oh <CRS_HOME>

#
# % opatch rollback -id 9348863 -local -oh <RDBMS_HOME>

Password123

/bin/srvctl stop home -o /opt/app/oracle/product/rdbms/sinop01/11.2.0 -s

/opt/app/oracle/product/rdbms/sinop01/11.2.0/status_040710 -n sinupn05

sudo /opt/app/oracle/product/11.2.0/grid/crs/install/rootcrs.pl -unlock

custom/server/9348863/custom/scripts/prepatch.sh -dbhome
/opt/app/oracle/product/rdbms/sinop01/11.2.0

opatch napply -local -oh /opt/app/oracle/product/11.2.0/grid -id 9348863