1.

Dowload latest optch and unzip ORACLE_HOME of grid and database

https://updates.oracle.com/Orion/PatchDetails/handle_rel_change?
release=80112000&plat_lang=46P&patch_file=&file_id=&password_required=&password_required_rea
dme=&merged_trans=&aru=22568865&patch_num=6880880&patch_num_id=1699749&default_releas
e=80112000&default_plat_lang=46P&default_compatible_with=&patch_password=&orderby=&directio
n=&no_header=0&sortcolpressed=&tab_number=

2. Ocm response file

$ORACLE_HOME/OPatch/ocm/bin/emocmrsp  -no_banner -output
<specify_the_location>/file.rsp

To apply the patch, it must be accessible from all nodes in the Oracle cluster. Download
the patch and unzip it to a shared location, this is called
the <UNZIPPED_PATCH_LOCATION>. This directory must be empty and not be /tmp.
Additionally, the directory should have read permission for the ORA_INSTALL group.
$ cd <UNZIPPED_PATCH_LOCATION>

Check that the directory is empty.

$ ls

Unzip the patch as grid home owner.

$ unzip p20996944_112030_<platform>.zip

Here we have kept at /u02 location and unzipped it.

3. .oraenv

Orcl1

4.
Now we will path oracle home
Do same steps for node 2

[root@rac2 ~]# export ORACLE_HOME=/u01/app/11.2.0/grid

[root@rac2 ~]# HISTORY

bash: HISTORY: command not found

[root@rac2 ~]# export PATH=$PATH:$ORACLE_HOME/bin:$ORACLE_HOME/OPatch

[root@rac2 ~]# crsctl check crs

CRS-4638: Oracle High Availability Services is online

CRS-4537: Cluster Ready Services is online

CRS-4529: Cluster Synchronization Services is online

CRS-4533: Event Manager is online

[root@rac2 ~]# ps -ef|grep pmon

grid 5241 1 0 13:40 ? 00:00:00 asm_pmon_+ASM2

root 6468 6299 0 13:49 pts/1 00:00:00 grep pmon

[root@rac2 ~]# srvctl status database -d orcl

Instance orcl1 is not running on node rac1

Instance orcl2 is not running on node rac2

[root@rac2 ~]#

[root@rac2 ~]# df -h

Filesystem Size Used Avail Use% Mounted on

/dev/sda3 7.6G 4.2G 3.1G 58% /

/dev/sda2 15G 6.3G 7.2G 47% /u02

/dev/sdb1 20G 8.1G 11G 44% /u01

/dev/sda1 99M 25M 69M 27% /boot

tmpfs 2.0G 460M 1.6G 23% /dev/shm

/dev/hdc 4.2G 4.2G 0 100% /media/OL-7.5 Server.x86_64

[root@rac2 ~]#

[root@rac2 ~]# cd $ORACLE_HOME/OPatch/ocm/bin/

[root@rac2 bin]# pwd

/u01/app/11.2.0/grid/OPatch/ocm/bin

[root@rac2 bin]# ls em*

emocmrsp

[root@rac2 bin]# ./emocmrsp -no_banner -output /u02/ocmgrid.rsp

Provide your email address to be informed of security issues, install and

initiate Oracle Configuration Manager. Easier for you if you use your My

Oracle Support Email address/User Name.

Visit http://www.oracle.com/support/policies.html for details.

Email address/User Name:

You have not provided an email address for notification of security issues.

Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]: n

Email address/User Name:

You have not provided an email address for notification of security issues.

Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]: n

Email address/User Name: y

Invalid email address.

Email address/User Name:

You have not provided an email address for notification of security issues.

Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]: y

The OCM configuration response file (/u02/ocmgrid.rsp) was successfully created.

[root@rac2 bin]# chmod 775 /u02/ocmgrid.rsp

[root@rac2 bin]#

Then do the post-insalltion steps

Loading Modified SQL Files into the Database

The following steps load modified SQL files into the database. For an Oracle RAC
environment, perform these steps on only one node.

1. For each database instance running on the Oracle home being patched, connect
to the database using SQL*Plus. Connect as SYSDBA and run
the catbundle.sql script as follows:

2. cd $ORACLE_HOME/rdbms/admin
3. sqlplus /nolog
4. SQL> CONNECT / AS SYSDBA
5. SQL> STARTUP
6. SQL> @catbundle.sql psu apply
7. SQL> QUIT

The catbundle.sql execution is reflected in
the dba_registry_history view by a row associated with bundle series PSU.

For information about the catbundle.sql script, see My Oracle Support

Document 605795.1 Introduction to Oracle Database catbundle.sql.

8. If the OJVM PSU was applied for a previous GI PSU patch, you may see invalid
Java classes after execution of the catbundle.sql script in the previous step.
If this is the case, run utlrp.sql to re-validate these Java classes.

9. cd $ORACLE_HOME/rdbms/admin
10. sqlplus /nolog
11. SQL> CONNECT / AS SYSDBA
12. SQL> @utlrp.sql

13. Check the following log files in $ORACLE_BASE/cfgtoollogs/catbundle for

any errors:

14. catbundle_PSU_<database SID>_APPLY_<TIMESTAMP>.log

15. catbundle_PSU_<database SID>_GENERATE_<TIMESTAMP>.log

where TIMESTAMP is of the form YYYYMMMDD_HH_MM_SS. If there are

errors, see Section 3, "Known Issues".

2.5.3 Upgrade Oracle Recovery Manager Catalog

If you are using the Oracle Recovery Manager, the catalog needs to be upgraded. Enter
the following command to upgrade it:

$ rman catalog username/password@alias

RMAN> UPGRADE CATALOG;