Home > RAC > Apply PSU patch – 11.2.0.3 Grid Infrastructure

Apply PSU patch – 11.2.0.3 Grid Infrastructure


The GI PSU patch includes updates for both the Clusterware home and Database home that can be applied in a rolling fashion.

Pre-requisites before applying the patch:

1. OPatch Utility Information

You must use the OPatch utility version 11.2.0.3.0 or later to apply this patch, which is available for download from My Oracle Support patch 6880880

 

2. OCM Configuration

The OPatch utility will prompt for your OCM (Oracle Configuration Manager) response file when it is run. You should enter a complete path of OCM response file if you already have created this in your environment. OCM response file is required and is not optional.

If you do not have the OCM response file (ocm.rsp)

Option-1 : Create the response file in current directory with filename ocm.rsp

$ORACLE_HOME/OPatch/ocm/bin/emocmrsp -no_banner

Option -2 : Creates a response file with the location and name specified

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

 

3. Validation of Oracle Inventory

Before beginning patch application, check the consistency of inventory information for GI home and each database home to be patched. Run the following command as respective Oracle home owner to check the consistency.

$ <ORACLE_HOME>/OPatch/opatch lsinventory -detail -oh <ORACLE_HOME>

 

4. Download and Unzip the Patch

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 p14727347_112030_<platform>.zip

 

5. Stop EM Agent Processes Prior to Patching and Prior to Rolling Back the Patch

You must stop the EM agent processes running from the database home, prior to patching the Oracle RAC database or GI Home and prior to rolling back the patch from Oracle RAC database or GI Home. Execute the following command on the node to be patched or the node where the patch is to be rolled back.

As the Oracle RAC database home owner execute:

$ <ORACLE_HOME>/bin/emctl stop dbconsole

OPatch auto for GI

The Opatch utility has automated the patch application for the Oracle Grid Infrastructure (GI) home and the Oracle RAC database homes when run with root privileges. It must be executed on each node in the cluster if the GI home or Oracle RAC database home is in non-shared storage. The utility should not be run in parallel on the cluster nodes.

Patch Installation

The patch instructions will differ based on the configuration of the Grid infrastructure and the Oracle RAC database homes. Patching instructions for Oracle RAC Database Homes and GI together are listed below.

The most common configurations are listed as follows:

• Case 1: GI Home and the Database Homes that are not shared and ACFS file system is not configured.

• Case 2: GI Home is not shared, Database Home is shared, ACFS may be used.

For other configurations listed below, see My Oracle Support Document 1494646.1:

• GI Home is not shared, the Database Home is not shared, ACFS may be used.

• Patching Oracle RAC Database Homes.

• Patching GI Home alone.

• Patching Oracle Restart Home.

• Patching a software only GI Home installation or before the GI Home is configured.

 

My existing RAC setup falls under Case1. Run the below command to patch both clusterware and rdbms binaries

As root user, execute the following command on each node of the cluster:
# opatch auto <UNZIPPED_PATCH_LOCATION> -ocmrf <ocm response file>

This will automatically stop the database and clusterware on each node, patches them and brings them up automatically

 

Patch Post-Installation Instructions

Load 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.

8. Check the following log files in $ORACLE_BASE/cfgtoollogs/catbundle for any errors:

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

10. 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”.

This completes the patching of 11.2.0.3 GI

Advertisements
Categories: RAC Tags: ,
  1. Rb
    June 11, 2013 at 5:44 AM

    “The utility should not be run in parallel on the cluster nodes.” – Any reason why this is not possible?

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Oracle database internals by Riyaj

Discussions about Oracle performance tuning, RAC, Oracle internal & E-business suite.

StartupForce

Where all the Action Is !!!!

Pavan DBA's Blog

The DBA Knowledge Store

ORACLE-BASE - Latest Articles

Where all the Action Is !!!!

%d bloggers like this: