Skip Headers

Oracle® Database

Patch 13696251 - 11.2.0.3.2 GI Patch Set Update (Includes Database PSU 11.2.0.3.2)

 

Released: April 17, 2012

This document is accurate at the time of release. For any changes and additional information regarding GI PSU 11.2.0.3.2, see these related documents that are available at My Oracle Support (http://support.oracle.com/):

This document includes the following sections:

1 Patch Information

Grid Infrastructure (GI) Patch Set Update (PSU) patches are cumulative, and include the DB PSU (and associated CPUs).

Table 1 lists the various configurations and the applicable PSU that should be used to patch that configuration.

Table 1 Configuration and PSU Mapping

Configuration GI Version Database Versions PSU Patch OPatch Command Comments

GI Home in conjunction with RAC, RACOne, or Single Instance home

11.2.0.3

11.2.0.3

GI PSU

OPatch auto

GI Home and all the Database Homes will be patched

GI Home in conjunction with RAC, RACOne, or Single Instance home

11.2.0.3

11.2.0.3 and other versions

GI PSU

OPatch auto

GI Home and Database Home at 11.2.0.3 version will be patched.

For Database home with version other than 11.2.0.3, apply the appropriate Database PSU for that version. For example, apply 11.1.0.7.x PSU to Database version 11.1.0.7.0.

GI Home in conjunction with RAC, RACOne, or Single Instance home

11.2.0.3

Other than 11.2.0.3

GI PSU

OPatch auto

GI Home alone is patched.

For Database home, apply the appropriate Database PSU for that version. For example, apply 11.1.0.7.x PSU to Database version 11.1.0.7.0.

Oracle Restart Home

11.2.0.3

11.2.0.3

GI PSU

OPatch auto

None

Database Single Instance home

NA

11.2.0.3

Database PSU

OPatch apply

None

Database Client home

NA

11.2.0.3

Database PSU

OPatch apply

None

Table 2 describes installation types and security content. For each installation type, it indicates the most recent patches, which includes new security fixes that are pertinent to that installation type. If there are no security fixes to be applied to an installation type, then "None" is indicated. If a specific patch is listed, then apply that or any later patch to be current with security fixes.

Table 2 Installation Types and Security Content

Installation Type Latest PSU with Security Fixes

Server homes

11.2.0.3.2 GI PSU

Grid Infrastructure home

11.2.0.3.2 GI PSU

Client-Only Installations

None

Instant Client Installations

None

(The Instant Client installation is not the same as the client-only Installation. For additional information about Instant Client installations, see Oracle Database Concepts.)

2 Patch Installation and Deinstallation

This section includes the following sections:

2.1 Patch Installation Prerequisites

You must satisfy the conditions in the following sections before applying the patch:

2.1.1 OPatch Utility Information

You must use the OPatch utility version 11.2.0.3.0 or later to apply this patch. Oracle recommends that you use the latest released OPatch for 11.2 releases, which is available for download from My Oracle Support patch 6880880 by selecting ARU link for the 11.2.0.0.0 release. It is recommended that you download the Opatch utility and the patch in a shared location to be able to access them from any node in the cluster for the patch application on each node.


Note:

When patching the GI Home, a shared location on ACFS only needs to be unmounted on the node where the GI Home is being patched.

The new opatch utility should be updated in all the Oracle RAC database homes and the GI home that are being patched. To update Opatch, use the following instructions.

  1. Download the OPatch utility to a temporary directory.

  2. For each Oracle RAC database home and the GI home that are being patched, run the following commands as the home owner to extract the OPatch utility.

    $ unzip <OPATCH-ZIP> -d <ORACLE_HOME>
$ <ORACLE_HOME>/OPatch/opatch version

The version output of the previous command should be 11.2.0.3.0 or later.

For information about OPatch documentation, including any known issues, see My Oracle Support Note 293369.1 OPatch documentation list.

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

If you do not have the OCM response file (ocm.rsp), then you should run the following command to create it.

As the Grid home owner execute:

$ <ORACLE_HOME>/OPatch/ocm/bin/emocmrsp

You can also invoke opatch auto with the -ocmrf <OCM response file path> option to run opatch auto in silent mode.

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

If this command succeeds, it lists the Oracle components that are installed in the home. Save the output so you have the status prior to the patch apply.

If this command fails, contact Oracle Support Services for assistance.

2.1.4 Unzipping the Patch

The patch application requires explicit user actions to run 'opatch auto' command on each node of Oracle clusterware. So, it is recommended that you download and unzip the patch in a shared location to be able to access it from any node in the cluster and then as the Grid home owner execute the unzip command. To prevent installation failures, this location should be an empty directory.


Note:

Do not unzip the patch in the top level /tmp directory.

The unzipped patch location should have read permission for ORA_INSTALL group in order to patch Oracle homes owned by different owners. The ORA_INSTALL group is the primary group of the user who owns the GI home or the group owner of the Oracle central inventory.

(In this readme, the downloaded patch location directory is referred as <UNZIPPED_PATCH_LOCATION>.)

$ cd <UNZIPPED_PATCH_LOCATION>

Unzip the patch as grid home owner in a shared location. As the Grid home owner execute:

$ unzip p13696251_112030_<platform>.zip

For example, if <UNZIPPED_PATCH_LOCATION> in your environment is /u01/oracle/patches, enter the following command:

$ cd /u01/oracle/patches

Unzip the patch as grid home owner in a shared location. As the Grid home owner execute:

$ unzip p13696251_112030_<platform>.zip

2.2 One-off Patch Conflict Detection and Resolution

For an introduction to the PSU one-off patch concepts, see "Patch Set Updates Patch Conflict Resolution" in My Oracle Support Note 854428.1 Patch Set Updates for Oracle Products.

The fastest and easiest way to determine whether you have one-off patches in the Oracle home that conflict with the patch, and to get the necessary conflict resolution patches, is to use the Patch Recommendations and Patch Plans features on the Patches & Updates tab in My Oracle Support. These features work in conjunction with the My Oracle Support Configuration Manager. Recorded training sessions on these features can be found in Note 603505.1.

However, if you are not using My Oracle Support Patch Plans, follow these steps.

Determine whether any currently installed one-off patches conflict with the PSU patch as follows:

  1. In the unzipped directory as in Section 2.1.4.

    $ opatch prereq CheckConflictAgainstOHWithDetail -ph <UNZIPPED_PATCH_LOCATION>/13696216 –oh $GRID_HOME
$ opatch prereq CheckConflictAgainstOHWithDetail -ph <UNZIPPED_PATCH_LOCATION>/13696216 –oh $DB_HOME
$ opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir <UNZIPPED_PATCH_LOCATION>/13696251 –oh $GRID_HOME
$ opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir <UNZIPPED_PATCH_LOCATION>/13696251/custom/server/13696251 –oh $DB_HOME

  2. Note that Oracle proactively provides PSU one-off patches for common conflicts.

  3. Use My Oracle Support Note 1061295.1 Patch Set Updates - One-off Patch Conflict Resolution to determine, for each conflicting patch, whether a conflict resolution patch is already available, and if you need to request a new conflict resolution patch or if the conflict may be ignored.

  4. When all the one-off patches that you have requested are available at My Oracle Support, proceed with Section 2.4, "Patch Installation".

2.3 OPatch Automation for GI

The Opatch utility has automated the patch application for the Oracle Grid Infrastructure (GI) home and the Oracle RAC database homes. It operates by querying existing configurations and automating the steps required for patching each Oracle RAC database home of same version and the GI home.

The utility must be executed by an operating system (OS) user with root privileges (usually the user root), and 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.

Depending on command line options specified, one invocation of Opatch can patch the GI home, one or more Oracle RAC database homes, or both GI and Oracle RAC database homes of the same Oracle release version. You can also roll back the patch with the same selectivity.

Add the directory containing the opatch to the $PATH environment variable. For example:

$ export PATH=$PATH:<GI_HOME>/OPatch

To patch GI home and all Oracle RAC database homes of the same version:

# opatch auto <UNZIPPED_PATCH_LOCATION> -ocmrf <ocm response file>

To patch only the GI home:

# opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME> -ocmrf <ocm response file>

To patch one or more Oracle RAC database homes:

# opatch auto <UNZIPPED_PATCH_LOCATION> -oh <oracle_home1_path>, <oracle_home2_path> -ocmrf <ocm response file>

To roll back the patch from the GI home and each Oracle RAC database home:

# opatch auto <UNZIPPED_PATCH_LOCATION> -rollback -ocmrf <ocm response file>

To roll back the patch from the GI home:

# opatch auto <UNZIPPED_PATCH_LOCATION> -oh <path to GI home> -rollback -ocmrf <ocm response file>

To roll back the patch from the Oracle RAC database home:

# opatch auto <UNZIPPED_PATCH_LOCATION> -oh <path to RAC database home> -rollback -ocmrf <ocm response file>

For more information about opatch auto, see My Oracle Support Note 293369.1 OPatch documentation list.

For detailed patch installation instructions, see Section 2.4, "Patch Installation".

2.4 Patch Installation

This section will guide you through the steps required to apply this patch to Oracle RAC database homes, the Grid home, or all relevant homes on the cluster.

The patch instructions will differ based on the configuration of the Grid infrastructure and the Oracle RAC database homes.

The patch installations will also differ based on following aspects of your existing configuration:

  • GI home is shared or non-shared

  • The Oracle RAC database home is shared or non-shared

  • The Oracle RAC database home software is on ACFS or non-ACFS file systems.

  • Patch all the Oracle RAC database and the GI homes together, or patch each home individually

You must choose the most appropriate case that is suitable based on the existing configurations and your patch intention.


Note:

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

As the Oracle RAC database home owner execute:

$ <ORACLE_HOME>/bin/emctl stop dbconsole

Case 1: Patching Oracle RAC Database Homes and the GI Home Together

Follow the instructions in this section if you would like to patch all the Oracle RAC database homes of release version 11.2.0.3 and the 11.2.0.3 GI home.

Case 1.1: GI Home Is Not Shared

Case 1.1.1: ACFS File System Is Not Configured and Database Homes Are Not Shared

Follow these instructions in this section if the GI home is not shared and none of the Oracle database homes is shared.

As root user execute the following command on each node of the cluster:

# opatch auto <UNZIPPED_PATCH_LOCATION> -ocmrf <ocm response file>

Case 1.1.2A: Patching the GI Home and Database Home Together, the GI Home Is Not Shared, the Database Home Is Shared, ACFS May Be Used

  1. From the Oracle database home, make sure to stop the Oracle RAC databases running on all nodes.

    As the database home owner execute:

    $ <ORACLE_HOME>/bin/srvctl stop database –d <db-unique-name>

  2. On the 1st node, unmount the ACFS file systems. Use instructions in Section 2.8 for unmounting ACFS file systems.

  3. On the 1st node, apply the patch to the GI Home using the opatch auto command.

    As root user, execute the following command:

    # opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME> -ocmrf <ocm response file>

  4. If the message, "A system reboot is recommended before using ACFS” is shown, then a reboot must be issued before continuing. Failure to do so will result in running with an unpatched ACFS\ADVM\OKS driver.

  5. On the 1st node, remount ACFS file systems. See Section 2.9 for instructions.

  6. On the 1st node, apply the patch to the Database home using the opatch auto command. Since the Database home is shared, this operation will patch the Database home across the cluster. Note that a USM only patch cannot be applied to a database home.

    As root user, execute the following command:

    # opatch auto <UNZIPPED_PATCH_LOCATION> -oh <DATABASE_HOME> -ocmrf <ocm response file>

  7. On the 1st node only, restart the Oracle instance which you have previously stopped in Step 1.

    As the database home owner execute:

    $ <ORACLE_HOME>/bin/srvctl start instance –d <db-unique-name> -n <nodename>

  8. On the 2nd (next) node, unmount the ACFS file systems. Use instructions in Section 2.8 for unmounting ACFS file systems.

  9. On the 2nd node, apply the patch to GI Home using the opatch auto command.

    As root user, execute the following command:

    # opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME> -ocmrf <ocm response file>

  10. If the message, "A system reboot is recommended before using ACFS” is shown, then a reboot must be issued before continuing. Failure to do so will result in running with an unpatched ACFS\ADVM\OKS driver.

  11. On the 2nd node, running the opatch auto command in Step 9 will restart the stack.

  12. On the 2nd node, remount ACFS file systems. See Section 2.9 for instructions.

  13. On the 2nd node only, restart the Oracle instance which you have previously stopped in Step 1.

    As the database home owner execute:

    $ <ORACLE_HOME>/bin/srvctl start instance –d <db-unique-name> -n <nodename>

  14. Repeat Steps 8 through 13 for all remaining nodes of the cluster.

Case 1.1.2B: Patching the GI Home and the Database Home Together, the GI Home Is Not Shared, the Database Home Is Not Shared, ACFS May Be Used

For each node, perform the following steps:

  1. On the local node, unmount the ACFS file systems. Use instructions in Section 2.8 for unmounting ACFS file systems.

  2. On the local node, apply the patch to the GI home and to the Database home.

    As root user, execute the following command:

    # opatch auto <UNZIPPED_PATCH_LOCATION> -ocmrf <ocm response file>

    This operation will patch both the CRS home and the Database home.

  3. If the message, "A system reboot is recommended before using ACFS” is shown, then a reboot must be issued before continuing. Failure to do so will result in running with an unpatched ACFS\ADVM\OKS driver.

  4. The opatch auto command will restart the stack on the local node and restart the Databases on the local node.

  5. Repeat Steps 1 through 3 for all remaining nodes of the cluster.

Case 1.2: GI Home Is Shared

Follow these instructions in this section if the GI home is shared.


Note:

Patching a shared GI home requires shutdown of Oracle GI stack on all the remote nodes in the cluster. This also means you need to stop all Oracle RAC databases which depend on GI stack, ASM for data files, or an ACFS file system.

  1. From the Oracle database home, make sure to stop the Oracle RAC databases running on all nodes.

    As Oracle database home owner:

    $ <ORACLE_HOME>/bin/srvctl stop database –d <db-unique-name>

    ORACLE_HOME: Complete path of the Oracle database home.

  2. Make sure the ACFS file systems are unmounted on all the nodes. Use instructions in Section 2.8 for unmounting ACFS file systems.

  3. As root user, execute the following on all the remote nodes to stop the CRS stack:

    # <GI_HOME>/bin/crsctl stop crs

  4. Patch the GI home.

    On local node, as root user, execute the following command:

    # opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME> -ocmrf <ocm response file>

  5. If the message, "A system reboot is recommended before using ACFS” is shown, then a reboot must be issued before continuing. Failure to do so will result in running with an unpatched ACFS\ADVM\OKS driver.

  6. On each remote node:

    1. As root user, run:

      # <GI_HOME>/crs/install/rootcrs.pl -patch

    2. If the message, "A system reboot is recommended before using ACFS” is shown, then a reboot must be issued before continuing. Failure to do so will result in running with an unpatched ACFS\ADVM\OKS driver.

    3. Restart the stack on each remote node.

      As root user execute:

      # <GI_HOME>/bin/crsctl start crs

  7. Mount ACFS file systems. See Section 2.9.

  8. For each Oracle RAC database home, execute the following command on each node if the database home software is not shared. Note that a USM only patch cannot be applied to a Database home.

    For each database home execute the following as root user:

    # opatch auto <UNZIPPED_PATCH_LOCATION> -oh <ORACLE_HOME> -ocmrf <ocm response file>

    ORACLE_HOME: Complete path of Oracle database home.


    Note:

    The previous command should be executed only once on any one node if the database home is shared.

  9. Restart the Oracle databases that you have previously stopped in step 1.

    As the database home owner execute:

    $ <ORACLE_HOME>/bin/srvctl start database –d <db-unique-name>

Case 2: Patching Oracle RAC Database Homes

You should use the following instructions if you prefer to patch Oracle RAC databases alone with this patch. Note that a USM only patch cannot be applied to a Database Home.

Case 2.1: Non-Shared Oracle RAC Database Homes

  1. Execute the following command on each node of the cluster.

    As root user execute:

    # opatch auto <UNZIPPED_PATCH_LOCATION> -oh <Comma separated Oracle home paths> -ocmrf <ocm response file>

Case 2.2: Shared Oracle RAC Database Homes

  1. Make sure to stop the databases running from the Oracle RAC database homes that you would like to patch. Execute the following command to stop each database.

    As Oracle database home owner execute:

    $ <ORACLE_HOME>/bin/srvctl stop database -d <db_unique_name>

  2. As root user execute only on the local node.

    # opatch auto <UNZIPPED_PATCH_LOCATION> -oh <Comma separated Oracle home paths> -ocmrf <ocm response file>

  3. Restart the Oracle databases that were previously stopped in Step 1. Execute the following command for each database.

    As Oracle database home owner execute:

    $ <ORACLE_HOME>/bin/srvctl start database -d <db_unique_name>

Case 3: Patching GI Home Alone

You should use the following instructions if you prefer to patch Oracle GI (Grid Infrastructure) home alone with this patch.

Case 3.1: Non-Shared GI Home

If the GI home is not shared then use the following instructions to patch the home.

Case 3.1.1: ACFS File System Is Not Configured

Follow these instructions in this section if the GI home is not shared and none of the Oracle database homes use ACFS file system for its software files.

Execute the following on each node of the cluster.

As root user execute:

# opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME> -ocmrf <ocm response file>

Case 3.1.2: ACFS File System Is Configured

Repeat Steps 1 through 6 for each node in the cluster:

  1. From the Oracle database home, stop the Oracle RAC database running on that node.

    As the database home owner execute:

    $ <ORACLE_HOME>/bin/srvctl stop instance –d <db-unique-name> -n <node_name>

  2. Unmount all ACFS file systems on this node using instructions in Section 2.8.

  3. Apply the patch to the GI home on that node using the opatch auto command.

    Execute the following command on that node in the cluster.

    As root user execute:

    # opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME> -ocmrf <ocm response file>

  4. If the message, "A system reboot is recommended before using ACFS” is shown, then a reboot must be issued before continuing. Failure to do so will result in running with an unpatched ACFS\ADVM\OKS driver.

  5. Remount ACFS file systems on that node. See Section 2.9 for instructions.

  6. Restart the Oracle database on that node that you have previously stopped in Step 1.

    As the database home owner execute:

    $ <ORACLE_HOME>/bin/srvctl start database –d <db-unique-name> -n <nodename>

Case 3.2: Shared GI Home

Follow these instructions in this section if the GI home is shared.


Note:

Patching a shared GI home requires shutdown of Oracle GI stack on all the remote nodes in the cluster. This also means you need to stop all Oracle RAC databases that depend on the GI stack, ASM for data file, or ACFS file system for database software.

  1. Make sure to stop the Oracle databases running from the Oracle RAC or Oracle RAC One Node database homes.

    As Oracle database home owner:

    $ <ORACLE_HOME>/bin/srvctl stop database –d <db-unique-name>

  2. Make sure the ACFS file systems are unmounted on all the nodes. Use instructions in Section 2.8 for unmounting ACFS file systems.

  3. As root user, execute the following on all the remote nodes to stop the CRS stack:

    # <GI_HOME>/bin/crsctl stop crs

  4. Execute the following command on the local node

    As root user execute:

    # opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME> -ocmrf <ocm response file>

  5. If the message, "A system reboot is recommended before using ACFS” is shown, then a reboot must be issued before continuing. Failure to do so will result in running with an unpatched ACFS\ADVM\OKS driver.

  6. On each remote node:

    1. As root user, run:

      # <GI_HOME>/crs/install/rootcrs.pl -patch

    2. If the message, "A system reboot is recommended before using ACFS” is shown, then a reboot must be issued before continuing. Failure to do so will result in running with an unpatched ACFS\ADVM\OKS driver.

    3. Start the Oracle GI stack on all the remote nodes.

      As root user execute:

      # <GI_HOME>/bin/crsctl start crs

  7. Mount ACFS file systems. See Section 2.9.

  8. Restart the Oracle databases that you have previously stopped in Step 1.

    As the database home owner execute:

    $ <ORACLE_HOME>/bin/srvctl start database –d <db-unique-name>

Case 4: Patching Oracle Restart Home

You must keep the Oracle Restart stack up and running when you are patching. Use the following instructions to patch Oracle Restart home.

As root user execute:

# opatch auto <UNZIPPED_PATCH_LOCATION> -ocmrf <ocm response file>

To patch the ACFS software in an Oracle Restart environment:

  1. Unmount all ACFS file systems. Use instructions in Section 2.8 for unmounting ACFS file systems.

  2. Run <GridHome>/bin/acfsroot install.

  3. If the message, "A system reboot is recommended before using ACFS” is shown, then a reboot must be issued before continuing. Failure to do so will result in running with an unpatched ACFS\ADVM\OKS driver.

  4. Remount ACFS file systems. See Section 2.9 for instructions.

Case 5: Patching a Software Only GI Home Installation or Before the GI Home Is Configured

  1. Apply the CRS patch using.

    As the GI home owner execute:

    $ <GI_HOME>/OPatch/opatch napply -oh <GI_HOME> -local <UNZIPPED_PATCH_LOCATION>/13696251

    As the GI home owner execute:

    $ <GI_HOME>/OPatch/opatch apply -oh <GI_HOME> -local <UNZIPPED_PATCH_LOCATION>/13696216

2.5 Patch Post-Installation Instructions

After installing the patch, perform the following actions:

  1. Apply conflict resolution patches as explained in Section 2.5.1.

  2. If applying a PSU, load modified SQL files into the database, as explained in Section 2.5.2.

  3. Upgrade Oracle Recovery Manager catalog, as explained in Section 2.5.3.

  4. Remount ACFS file systems. See Section 2.9 for instructions.

2.5.1 Applying Conflict Resolution Patches

Apply the patch conflict resolution one-off patches that were determined to be needed when you performed the steps in Section 2.2, "One-off Patch Conflict Detection and Resolution".

2.5.2 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:

    cd $ORACLE_HOME/rdbms/admin
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> STARTUP
SQL> @catbundle.sql psu apply
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 Note 605795.1 Introduction to Oracle Database catbundle.sql.

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

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

    where TIMESTAMP is of the form YYYYMMMDD_HH_MM_SS. If there are errors, refer to 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;

2.6 Patch Post-Installation Instructions for Databases Created or Upgraded after Installation of Patch in the Oracle Home

These instructions are for a database that is created or upgraded after the installation of the patch.

You must execute the steps in Section 2.5.2, "Loading Modified SQL Files into the Database" for any new database only if it was created by any of the following methods:

  • Using DBCA (Database Configuration Assistant) to select a sample database (General, Data Warehouse, Transaction Processing)

  • Using a script that was created by DBCA that creates a database from a sample database

There are no actions required for databases that have been upgraded.

2.7 Patch Deinstallation

You can use the following steps to roll back patches. Choose the instructions that apply to your needs.


Note:

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

As the Oracle RAC or Oracle RAC One Node database home owner execute:

<ORACLE_HOME>/bin/emctl stop dbconsole

Case D1: Rolling Back the Oracle RAC Database Homes and GI Homes Together

Follow the instructions in this section if you would like to rollback the patch from all the Oracle RAC database homes of release version 11.2.0.3 and the 11.2.0.3 GI home.

Case D1.1: GI Home Is Not Shared

Case D1.1.1: ACFS File System Is Not Configured and Database Homes Are Not Shared

Follow these instructions in this section if the GI home is not shared and none of the Oracle database homes is shared.

As root user, execute the following command on each node of the cluster.

# opatch auto <UNZIPPED_PATCH_LOCATION> -rollback -ocmrf <ocm response file>

If the message, "A system reboot is recommended before using ACFS” is shown, then a reboot must be issued before continuing. Failure to do so will result in running with an unpatched ACFS\ADVM\OKS driver.

Case D1.1.2A: GI Home and Database Home Together, the GI Home Is Not Shared, the Database Home Is Shared

  1. From the Oracle database home, make sure to stop the Oracle RAC databases running on all nodes.

    As the database home owner execute:

    $ <ORACLE_HOME>/bin/srvctl stop database –d <db-unique-name>

  2. On the 1st node, unmount the ACFS file systems. Use instructions in Section 2.8 for unmounting ACFS file systems.

  3. On the 1st node, to roll back the patch from the GI Home using the opatch auto command.

    As root user, execute the following command:

    # opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME> -rollback -ocmrf <ocm response file>

  4. If the message, "A system reboot is recommended before using ACFS” is shown, then a reboot must be issued before continuing. Failure to do so will result in running with an unpatched ACFS\ADVM\OKS driver.

  5. On the 1st node, remount ACFS file systems. See Section 2.9 for instructions.

  6. On the 1st node, roll back the patch to the Database home using the opatch auto command. This operation will rollback the patch to the Database home across the cluster given that it is a shared ACFS home. Note that a USM only patch cannot be applied to a Database home.

    As root user, execute the following command:

    # opatch auto <UNZIPPED_PATCH_LOCATION> -oh <DATABASE_HOME> -rollback -ocmrf <ocm response file>

  7. On the 1st node only, restart the Oracle instance which you have previously stopped in Step 1.

    As the database home owner execute:

    $ <ORACLE_HOME>/bin/srvctl start instance –d <db-unique-name> -n <nodename>

  8. On the 2nd (next) node, unmount the ACFS file systems. Use instructions in Section 2.8 for unmounting ACFS file systems.

  9. On the 2nd node, roll back the patch to GI Home using the opatch auto command.

    As root user, execute the following command:

    # opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME> -rollback -ocmrf <ocm response file>

  10. If the message, "A system reboot is recommended before using ACFS” is shown, then a reboot must be issued before continuing. Failure to do so will result in running with an unpatched ACFS\ADVM\OKS driver.

  11. On the 2nd node, running the opatch auto command in Step 9 will restart the stack.

  12. On the 2nd node, remount ACFS file systems. See Section 2.9 for instructions.

  13. On the 2nd node only, restart the Oracle instance which you have previously stopped in Step 1.

    As the database home owner execute:

    $ <ORACLE_HOME>/bin/srvctl start instance –d <db-unique-name> -n <nodename>

  14. Repeat Steps 7 through 13 for all remaining nodes of the cluster.

Case D1.1.2B: GI Home and the Database Home Together, the GI Home Is Not Shared, the Database Home Is Not Shared

For each node, perform the following steps:

  1. On the local node, unmount the ACFS file systems. Use instructions in Section 2.8 for unmounting ACFS file systems.

  2. On the local node, roll back the patch to the GI home and to the Database home.

    As root user, execute the following command:

    # opatch auto <UNZIPPED_PATCH_LOCATION> -rollback -ocmrf <ocm response file>

    This operation will patch both the CRS home and the Database home.

  3. If the message, "A system reboot is recommended before using ACFS” is shown, then a reboot must be issued before continuing. Failure to do so will result in running with an unpatched ACFS\ADVM\OKS driver.

  4. The opatch auto command will restart the stack on the local node and restarts the Database on the local node.

  5. Repeat Steps 1 through 3 for all remaining nodes of the cluster.

Case D1.2 GI Home Is Shared

Follow these instructions in this section if the GI home is shared.


Note:

An operation on a shared GI home requires shutdown of the Oracle GI stack on all the remote nodes in the cluster. This also means you need to stop all Oracle RAC databases that depend on the GI stack, ASM for data file, or ACFS file system.

  1. Make sure to stop the Oracle databases running from the Oracle RAC database homes.

    As Oracle database home owner:

    $ <ORACLE_HOME>/bin/srvctl stop database -d <db-unique-name>

    ORACLE_HOME: Complete path of the Oracle database home.

  2. Make sure the ACFS file systems are unmounted on all the nodes. Use instructions in Section 2.8 for un-mounting ACFS file systems.

  3. As root user, execute the following on all the remote nodes to stop the CRS stack:

    # <GI_HOME>/bin/crsctl stop crs

  4. Roll back the patch from the GI home.

    On local node, as root user, execute the following command:

    # opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME> -rollback -ocmrf <ocm response file>

  5. If the message, "A system reboot is recommended before using ACFS” is shown, then a reboot must be issued before continuing. Failure to do so will result in running with an unpatched ACFS\ADVM\OKS driver.

  6. Start the Oracle GI stack on all the remote nodes.

    As root user execute:

    # <GI_HOME>/bin/crsctl start crs

  7. Mount ACFS file systems. See Section 2.9.

  8. For each Oracle RAC database home, execute the following command on each node if the database home software is not shared. Note that a USM only patch cannot be applied to a Database home.

    For each database home, execute the following as root user:

    # opatch auto <UNZIPPED_PATCH_LOCATION> -oh <ORACLE_HOME> -rollback -ocmrf <ocm response file>

    ORACLE_HOME: Complete path of Oracle database home.


    Note:

    The previous command should be executed only once on any one node if the database home is shared.

  9. Restart the Oracle databases that you have previously stopped in Step 1.

    As the database home owner execute:

    $ <ORACLE_HOME>/bin/srvctl start database -d <db-unique-name>

Case D2: Rolling Back from the Oracle RAC Database Homes

You should use the following instructions if you prefer to roll back the patch from Oracle RAC databases homes alone.

Case D2.1: Non-Shared Oracle RAC Database Homes

Note that a USM only patch cannot be applied to a Database home.

Execute the following command on each node of the cluster.

As root user execute:

# opatch auto <UNZIPPED_PATCH_LOCATION> -oh <Comma separated Oracle home paths> -rollback -ocmrf <ocm response file>

Case D2.2: Shared Oracle RAC Database Homes

Note that a USM only patch cannot be applied to a Database home.

  1. Make sure to stop the databases running from the Oracle RAC database homes from which you would like to roll back the patch. Execute the following command to stop each database.

    As Oracle database home owner execute:

    $ <ORACLE_HOME>/bin/srvctl stop database -d <db_unique_name>

  2. As root user execute only on the local node.

    # opatch auto <UNZIPPED_PATCH_LOCATION> -oh <Comma separated Oracle home paths> -rollback -ocmrf <ocm response file>

  3. Restart the Oracle databases that were previously stopped in Step 1. Execute the following command for each database.

    As Oracle database home owner execute:

    $ <ORACLE_HOME>/bin/srvctl start database -d <db_unique_name>

Case D3: Rolling Back from the GI Home Alone

You should use the following instructions if you prefer to roll back the patch from the Oracle GI (Grid Infrastructure) home alone.

Case D3.1 Shared GI Home

Follow these instructions in this section if the GI home is shared.


Note:

An operation in a shared GI home requires shutdown of Oracle GI stack on all the remote nodes in the cluster. This also means you need to stop all Oracle RAC databases that depend on the GI stack, ASM for data file, or ACFS file system for database software.

  1. Make sure to stop the Oracle databases running from the Oracle RAC database homes.

    As Oracle database home owner:

    $ <ORACLE_HOME>/bin/srvctl stop database -d <db-unique-name>

  2. Make sure the ACFS file systems are unmounted on all the nodes. Use instructions in Section 2.8 for unmounting ACFS file systems.

  3. As root user, execute the following on all the remote nodes to stop the CRS stack:

    # <GI_HOME>/bin/crsctl stop crs

  4. Execute the following command on the local node.

    As root user execute:

    # opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME> -rollback -ocmrf <ocm response file>

  5. If the message, "A system reboot is recommended before using ACFS” is shown, then a reboot must be issued before continuing. Failure to do so will result in running with an unpatched ACFS\ADVM\OKS driver.

  6. Start the Oracle GI stack on all the remote nodes.

    As root user execute:

    # <GI_HOME>/bin/crsctl start crs

  7. Mount ACFS file systems. See Section 2.9.

  8. Restart the Oracle databases that you have previously stopped in Step 1.

    As the database home owner execute:

    $ <ORACLE_HOME>/bin/srvctl start database -d <db-unique-name>

Case D3.2: Non-Shared GI Home

If the GI home is not shared, then use the following instructions to roll back the patch from the GI home.

Case D3.2.1: ACFS File System Is Not Configured

Follow these instructions in this section if the GI home is not shared and none of the Oracle database homes is shared.

Execute the following on each node of the cluster.

As root user execute:

# opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME> -rollback -ocmrf <ocm response file>

If the message, "A system reboot is recommended before using ACFS” is shown, then a reboot must be issued before continuing. Failure to do so will result in running with an unpatched ACFS\ADVM\OKS driver.

Case D3.2.2: ACFS File System Is Configured

Repeat Steps 1 through 6 for each node in the cluster:

  1. From the Oracle database home, stop the Oracle RAC database running on that node.

    As the database home owner execute:

    $ <ORACLE_HOME>/bin/srvctl stop instance -d <db-unique-name> -n <node_name>

  2. Make sure the ACFS file systems are unmounted on that node. Use instructions in Section 2.8 for unmounting ACFS file systems.

  3. Roll back the patch to the GI home on that node using the opatch auto command.

    Execute the following command on each node in the cluster.

    As root user execute:

    # opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME> -rollback -ocmrf <ocm response file>

  4. If the message, "A system reboot is recommended before using ACFS” is shown, then a reboot must be issued before continuing. Failure to do so will result in running with an unpatched ACFS\ADVM\OKS driver.

  5. Remount ACFS file systems on that node. See Section 2.9 for instructions.

  6. Restart the Oracle database on that node that you have previously stopped in Step 1.

    As the database home owner execute:

    $ <ORACLE_HOME>/bin/srvctl start instance -d <db-unique-name> -n <node_name>

Case D4: Rolling Back the Patch from Oracle Restart Home

You must keep the Oracle Restart stack up and running when you are rolling back the patch from the Oracle Restart home. Use the following instructions to roll back the patch from the Oracle Restart home.

  1. As root user execute:

    # opatch auto <UNZIPPED_PATCH_LOCATION> -oh <Oracle-Restart-home> -rollback -ocmrf <ocm response file>

  2. If the message, "A system reboot is recommended before using ACFS” is shown, then a reboot must be issued before continuing. Failure to do so will result in running with an unpatched ACFS\ADVM\OKS driver.

To update ACFS software in an Oracle Restart configuration:

  1. Unmount all ACFS file systems. Use instructions in Section 2.8 for unmounting ACFS file systems.

  2. Update ACFS: <Oracle-Restart-home>/bin/acfsroot install

  3. Remount ACFS file systems. See Section 2.9 for instructions.

Case D5: Rolling Back the Patch from a Software Only GI Home Installation or Before the GI Home is Configured

  1. Roll back the CRS patch.

    As the GI home owner execute:

    $ <GI_HOME>/OPatch/opatch rollback -local -id 13696251 -oh <GI_HOME> 
$ <GI_HOME>/OPatch/opatch rollback -local -id 13696216 -oh <GI_HOME>

2.8 Unmounting ACFS File Systems

ACFS file systems can be used by Oracle RAC for hosting software files for the database. It can also be used as a general purpose file system for non-database files. The ACFS file system is managed and administered by the Oracle GRID Infrastructure. So ACFS file systems will be impacted when shutting down the GI stack for patching GI homes.

Shut down the processes using the software files on ACFS and then unmount the ACFS file system.


Note:

Make sure to stop the non-Oracle processes that use ACFS file systems.

If the ACFS file system is used by Oracle database software, then perform Steps 1 and 2.

  1. Execute the following command to find the names of the CRS managed ACFS file system resource.

    # crsctl stat res -w "TYPE = ora.acfs.type" -p | grep VOLUME

  2. Execute the following command to stop the CRS managed ACFS file system resource with the resource name found from Step 1.

    As root user execute:

    # srvctl stop filesystem -d <volume device path> -n <node to stop file system on>

If the ACFS file system is not used for Oracle Database software and is registered in the ACFS registry, perform the following steps.

  1. Execute the following command to find all ACFS file system mount points.

    As the root user execute:

    # /sbin/acfsutil registry

  2. Unmount ACFS file systems found in Step 1.

    As the root user execute:

    # /bin/umount <mount-point>

    Note:

    On Solaris operating system use: /sbin/umount.

    On AIX operating system, use: /etc/umount.

  3. Verify that the ACFS file systems are unmounted. Execute the following command to verify.

    As the root user execute:

    # /sbin/acfsutil info fs

    The previous command should return the following message if there is no ACFS file systems mounted.

    "acfsutil info fs: ACFS-03036: no mounted ACFS file systems"

2.9 Mounting ACFS File Systems

If the ACFS file system is used by Oracle database software, then perform Steps 1 and 2.

  1. Execute the following command to find the names of the CRS managed ACFS file system resource.

    As root user execute:

    # crsctl stat res -w "TYPE = ora.acfs.type" -p | grep VOLUME

  2. Execute the following command to start and mount the CRS managed ACFS file system resource with the resource name found from Step 1.

    As root user execute:

    # srvctl start filesystem -d <volume device path> -n <node to start file system on>

If the ACFS file system is not used for Oracle Database software and is registered in the ACFS registry, these file systems should get automatically mounted when the CRS stack comes up. Perform Steps 1 and 2 if it is not already mounted.

  1. Execute the following command to find all ACFS file system mount points.

    As the root user execute:

    # /sbin/acfsutil registry

  2. Mount ACFS file systems found in Step 1.

    As the root user execute:

    # /bin/mount <mount-point>

    Note:

    On Solaris operating system use: /sbin/mount.

    On AIX operating system, use: /etc/mount.

2.10 Patch Post-Deinstallation Instructions for an Oracle RAC Environment

Follow these steps only on the node for which the steps in Section 2.5.2, "Loading Modified SQL Files into the Database" were executed during the patch application.:

  1. Start all database instances running from the Oracle home. (For more information, see Oracle Database Administrator's Guide.)

  2. For each database instance running out of the ORACLE_HOME, connect to the database using SQL*Plus as SYSDBA and run the rollback script as follows:

    cd $ORACLE_HOME/rdbms/admin
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> STARTUP
SQL> @catbundle_PSU_<database SID PREFIX>_ROLLBACK.sql
SQL> QUIT

    In an Oracle RAC environment, the name of the rollback script will have the format catbundle_PSU_<database SID PREFIX>_ROLLBACK.sql.

  3. Check the log file for any errors. The log file is found in $ORACLE_BASE/cfgtoollogs/catbundle and is named catbundle_PSU_<database SID>_ROLLBACK_<TIMESTAMP>.log where TIMESTAMP is of the form YYYYMMMDD_HH_MM_SS. If there are errors, refer to Section 3, "Known Issues".

  4. Ensure that you verify the Oracle Inventory and compare the output with the one you ran in Section 2.1.3, "Validation of Oracle Inventory" and re-apply any patches that were rolled back as part of this patch apply. To verify the inventory, run the following command:

    $ opatch lsinventory

All other instances can be started and accessed as usual while you are executing the deinstallation steps.

3 Known Issues

For information about OPatch issues, see My Oracle Support Note 293369.1 OPatch documentation list.

For issues documented after the release of this PSUs, see My Oracle Support Note 1399142.1 11.2.0.3.X Grid Infrastructure Bundle/PSU Known Issues.

4 References

The following documents are references for this patch.

Note 293369.1 OPatch documentation list

Note 360870.1 Impact of Java Security Vulnerabilities on Oracle Products

Note 468959.1 Enterprise Manager Grid Control Known Issues

Note 1339140.1 Opatch/Patch Questions/Issues for Oracle Clusterware (Grid Infrastructure or CRS) and RAC Environments

5 Manual Steps for Apply/Rollback Patch

Steps for Applying the Patch


Note:

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

As the Oracle RAC database home owner execute:

$ <ORACLE_HOME>/bin/emctl stop dbconsole

Execute the following on each node of the cluster in non-shared CRS and DB home environment to apply the patch.

  1. Stop the CRS managed resources running from DB homes.

    If this is a GI Home environment, as the database home owner execute:

    $ <ORACLE_HOME>/bin/srvctl stop home -o <ORACLE_HOME> -s <status file location> -n <node name>

    If this is an Oracle Restart Home environment, as the database home owner execute:

    $ <ORACLE_HOME>/bin/srvctl stop home -o <ORACLE_HOME> -s <status file location>

    Note:

    You need to make sure that the Oracle ACFS file systems are unmounted (see Section 2.8) and all other Oracle processes are shutdown before you proceed.

  2. Run the pre root script.

    If this is a GI Home, as the root user execute:

    # <GI_HOME>/crs/install/rootcrs.pl -unlock

    If this is an Oracle Restart Home, as the root user execute:

    # <GI_HOME>/crs/install/roothas.pl -unlock

  3. Apply the CRS patch using.

    As the GI home owner execute:

    $ <GI_HOME>/OPatch/opatch napply -oh <GI_HOME> -local <UNZIPPED_PATCH_LOCATION>/13696251

    As the GI home owner execute:

    $ <GI_HOME>/OPatch/opatch apply -oh <GI_HOME> -local <UNZIPPED_PATCH_LOCATION>/13696216

  4. Run the pre script for DB component of the patch.

    As the database home owner execute:

    $ <UNZIPPED_PATCH_LOCATION>/13696251/custom/server/13696251/custom/scripts/prepatch.sh -dbhome <ORACLE_HOME>

  5. Apply the DB patch.

    As the database home owner execute:

    $ <ORACLE_HOME>/OPatch/opatch napply -oh <ORACLE_HOME> -local <UNZIPPED_PATCH_LOCATION>/13696251/custom/server/13696251
$ <ORACLE_HOME>/OPatch/opatch apply -oh <ORACLE_HOME> -local <UNZIPPED_PATCH_LOCATION>/13696216

  6. Run the post script for DB component of the patch.

    As the database home owner execute:

    $ <UNZIPPED_PATCH_LOCATION>/13696251/custom/server/13696251/custom/scripts/postpatch.sh -dbhome <ORACLE_HOME>

  7. Run the post script.

    As the root user execute:

    # <GI_HOME>/rdbms/install/rootadd_rdbms.sh

    If this is a GI Home, as the root user execute:

    # <GI_HOME>/crs/install/rootcrs.pl -patch

    If this is an Oracle Restart Home, as the root user execute:

    # <GI_HOME>/crs/install/roothas.pl -patch

  8. If the message, "A system reboot is recommended before using ACFS” is shown, then a reboot must be issued before continuing. Failure to do so will result in running with an unpatched ACFS\ADVM\OKS driver.

  9. Start the CRS managed resources that were earlier running from DB homes.

    If this is a GI Home environment, as the database home owner execute:

    $ <ORACLE_HOME>/bin/srvctl start home -o <ORACLE_HOME> -s <status file location> -n <node name>

    If this is an Oracle Restart Home environment, as the database home owner execute:

    $ <ORACLE_HOME>/bin/srvctl start home -o <ORACLE_HOME> -s <status file location>

Steps for Rolling Back the Patch From a GI Home

Execute the following on each node of the cluster in non-shared CRS and DB home environment to rollback the patch.

  1. Stop the CRS managed resources running from DB homes.

    If this is a GI Home environment, as the database home owner execute:

    $ <ORACLE_HOME>/bin/srvctl stop home -o <ORACLE_HOME> -s <status file location> -n <node name>

    If this is an Oracle Restart Home environment, as the database home owner execute:

    $ <ORACLE_HOME>/bin/srvctl stop home -o <ORACLE_HOME> -s <status file location>

    Note:

    You need to make sure that the Oracle ACFS file systems are unmounted (see Section 2.8) and all other Oracle processes are shut down before you proceed.

  2. Run the pre root script.

    If this is a GI Home, as the root user execute:

    # <GI_HOME>/crs/install/rootcrs.pl -unlock

    If this is an Oracle Restart Home, as the root user execute:

    # <GI_HOME>/crs/install/roothas.pl -unlock

  3. Roll back the CRS patch.

    As the GI home owner execute:

    $ <GI_HOME>/OPatch/opatch rollback -local -id 13696251 -oh <GI_HOME> 
$ <GI_HOME>/OPatch/opatch rollback -local -id 13696216 -oh <GI_HOME>

  4. Run the pre script for DB component of the patch.

    As the database home owner execute:

    $ <UNZIPPED_PATCH_LOCATION>/13696251/custom/server/13696251/custom/scripts/prepatch.sh -dbhome <ORACLE_HOME>

  5. Roll back the DB patch from the database home.

    As the database home owner execute:

    $ <ORACLE_HOME>/OPatch/opatch rollback -local -id 13696251 -oh <ORACLE_HOME> 
$ <ORACLE_HOME>/OPatch/opatch rollback -local -id 13696216 -oh <ORACLE_HOME>

  6. Run the post script for DB component of the patch.

    As the database home owner execute:

    $ <UNZIPPED_PATCH_LOCATION>/13696251/custom/server/13696251/custom/scripts/postpatch.sh -dbhome <ORACLE_HOME>

  7. Run the post script.

    As the root user execute:

    # <GI_HOME>/rdbms/install/rootadd_rdbms.sh

    If this is a GI Home, as the root user execute:

    # <GI_HOME>/crs/install/rootcrs.pl -patch

    If this is an Oracle Restart Home, as the root user execute:

    # <GI_HOME>/crs/install/roothas.pl -patch

  8. If the message, "A system reboot is recommended before using ACFS” is shown, then a reboot must be issued before continuing. Failure to do so will result in running with an unpatched ACFS\ADVM\OKS driver.

  9. Start the CRS managed resources that were earlier running from DB homes.

    If this is a GI Home environment, as the database home owner execute:

    $ <ORACLE_HOME>/bin/srvctl start home -o <ORACLE_HOME> -s <status file location> -n <node name>

    If this is an Oracle Restart Home environment, as the database home owner execute:

    $ <ORACLE_HOME>/bin/srvctl start home -o <ORACLE_HOME> -s <status file location>

Patching an Oracle RAC Home Installation Manually

Note that USM only patches cannot be applied to a Database home.

  1. Run the pre script for DB component of the patch.

    As the database home owner execute:

    $ <UNZIPPED_PATCH_LOCATION>/13696251/custom/server/13696251/custom/scripts/prepatch.sh -dbhome <ORACLE_HOME>

  2. Apply the DB patch.

    As the database home owner execute:

    $ <ORACLE_HOME>/OPatch/opatch napply -oh <ORACLE_HOME> -local <UNZIPPED_PATCH_LOCATION>/13696251/custom/server/13696251
$ <ORACLE_HOME>/OPatch/opatch apply -oh <ORACLE_HOME> -local <UNZIPPED_PATCH_LOCATION>/13696216

  3. Run the post script for DB component of the patch.

    As the database home owner execute:

    $ <UNZIPPED_PATCH_LOCATION>/13696251/custom/server/13696251/custom/scripts/postpatch.sh -dbhome <ORACLE_HOME>

Rolling Back the Patch from an Oracle RAC Home Installation Manually

  1. Run the pre script for DB component of the patch.

    As the database home owner execute:

    $ <UNZIPPED_PATCH_LOCATION>/13696251/custom/server/13696251/custom/scripts/prepatch.sh -dbhome <ORACLE_HOME>

  2. Roll back the DB patch from the database home.

    As the database home owner execute:

    $ <ORACLE_HOME>/OPatch/opatch rollback -local -id 13696251 -oh <ORACLE_HOME>
$ <ORACLE_HOME>/OPatch/opatch rollback -local -id 13696216 -oh <ORACLE_HOME>

  3. Run the post script for DB component of the patch.

    As the database home owner execute:

    $ <UNZIPPED_PATCH_LOCATION>/13696251/custom/server/13696251/custom/scripts/postpatch.sh -dbhome <ORACLE_HOME>

6 Bugs Fixed by This Patch

This patch includes the following bug fixes:

6.1 CPU Molecules

CPU molecules in GI PSU 11.2.0.3.2:

GI PSU 11.2.0.3.2 contains all molecules previously released in GI PSU 11.2.0.3.1 and the following new GI PSU 11.2.0.3.2 molecules:

13742464 - DB-11.2.0.3-MOLECULE-003-CPUAPR2012

13742433 - DB-11.2.0.3-MOLECULE-004-CPUAPR2012

13742434 - DB-11.2.0.3-MOLECULE-005-CPUAPR2012

13742435 - DB-11.2.0.3-MOLECULE-006-CPUAPR2012

13742436 - DB-11.2.0.3-MOLECULE-007-CPUAPR2012

13742437 - DB-11.2.0.3-MOLECULE-008-CPUAPR2012

13742438 - DB-11.2.0.3-MOLECULE-009-CPUAPR2012

13772618 - DB-11.2.0.3-MOLECULE-010-CPUAPR2012

6.2 Bugs Fixed in GI PSU 11.2.0.3.2

GI PSU 11.2.0.3.2 contains the following new fixes:

Buffer Cache Management

12748240 - FIX FOR BUG 12748240

12780098 - FIX FOR BUG 12780098

12919564 - ENCOUNTERED ORA-600 [KTBESC_PLUGGED] WHILE RUNNING APPS RTS

13503598 - FIX FOR BUG 13503598

Generic

10350832 - FINISH_REDEF_TABLE HAS SLIM CHANGE IN GETTING X DML LOCK

11063191 - ORA-4031 WITH HINT /*+ CURSOR_SHARING_EXACT */ - EXCESSIVE "KKSSP^NN" MEMORY

11877623 - ORA-600 [17273]

12612118 - ORA-07445 [QSMQBTSS_BUILD_TABLE_INLINEVIEW_SUBORDSETS()+272] ALTER MVIEW COMPIL

12764337 - XSTRM : ORA-7445 [KGLDTIN()+150] DURING IMPORT/VIEW CREATION DDL

12780983 - UNABLE TO ACTUALIZE OBJECTS INTO CHILD EDITION - ORA-00955

12845115 - THE MATERIALIZED OBJECT EXISTS EVEN AFTER DROPPING THE MATERIALIZED VIEWS.

12849688 - FLAG VALUE IN MLOG$ IS INCORRECT AFTER UPGRADE TO 11GR2

12960925 - ORA-932 ON OCISTMTEXECUTE AFTER ONLINE REDEFINITION OF LONG TO CLOB COLUMN

13070939 - 11.2.0.3.0 NOT COMPILING THE QUERY , GIVING ERROR ORA-01790

13332439 - UTL_RECOMP.RECOMP_PARALLEL CAN DEADLOCK IN AN EDITIONED ENVIRONMENT

High Availability

12829021 - SWITCHOVER FAILS WITH ORA-1093

12894807 - SELECT FOR UPDATE WITH DBLINK RECEIVES ORA-16000 ON STANDBY OF ACTIVE DATA GUARD

13554409 - FIX FOR BUG 13554409

Oracle Portable ClusterWare

11772838 - DB AGENT OVERWRITE POLICY ON LOCAL_LISTENER

12349553 - VIP ON FORMER PRIMARY NIC CAN NOT BE CLEARD WHEN GLS NIC FAIL OVER HAPPENS

12398492 - SIHA DOES NOT SET ULIMIT FOR MEMLOCK

12594616 - AN ERROR OCCUR WHEN CHOOSE ACFS TO STORE THE DATAFILES DURING DBCA

12639013 - POTENTIAL SPLIT AT STARTUP - LRG PROBLEM ID 5567361

12659561 - INSTANCE DOES NOT REGISTER SERVICES WHEN SCAN FAILOVERED

12709476 - 11202_GIBTHREE_HPI:CRSD ORAAGENT MEMORY LEAK AT 1.5M/1.2H ON NON-PE NODES

12730342 - CAN'T FOUND LOGICAL CORRUPTION OF VOTEDISK ON 11.2.0.2

13036424 - CHMOS HAS AN ERROR IN CALCULATING THE TOTAL NUMBER OF OPEN FDS ON A SYSTEM

13037709 - INTERMITTENT FREE IP DETERMINATION ISSUE IN SRGSRV

13058611 - ROOTCRS.PL DECONFIG KEEPDG DOES NOT KEEP DISKGROUP IN UPGRADED ENVIRONMENT

13251796 - LNX64-12.1-EVM: ORAAGENT DUMPS CORE IN INSTCONNECTION::DISCONNECT AT CLSNINSTCON

13371153 - SCAN VIPS FAIL PING AFTER RELOCATE EVEN WITH NEW ARP DRIVER (PATCH 10124639)

13425727 - ROOTCRS.PL DOES NOT UNLOCK THE 11.2.0.3 CLONED HOME PROPERLY

13430715 - FUJITSU-GLS-11203:ORAROOTAGENT DOESN'T RECOGNIZE GLS ON SOLARIS SPARC

13440962 - DIFFERENT SUBNET FAILED TO CONNECT TO VIP AFTER RESTART VIP

13531373 - 11.2.0.3.1GIPSU:CVU CHECK FAIL FOR NETWORK PARAMETERS EVEN THEY ARE SATISFIED

13569812 - 11.2.0.3.1GIPSU:CVU FAIL TO DETERMINE IF ORACLE HOME (ON ACFS) IS SHARED

13652088 - EMGC OUT OF PLACE PATCHING NOT ADJUSTING INIT.OHASD TO POINT TO NEW GI HOME

Oracle Security

12923168 - CANNOT USE QUOTED FUNCTION NAME FOR VPD POLICY FUNCTION

13036331 - ORA-01031 INSUFFICIENT PRIVILEGES WHEN GRANTING EXECUTE ON DBMS PACKAGES

Oracle Space Management

12582664 - DEDUPLICATION WITH SECUREFILES NOT WORKING AS EXPECTED

12588744 - SECUREFILE WASTE STORAGE WHEN SPECIFY INITIAL EXTENT

12656535 - ORA-1555 DURING DIRECT PATH READ OF SECUREFILE LOB

12662040 - SECUREFILE LOB SEGMENT KEEPS GROWING IN CASE OF PLENTY OF FREE SPACE

Oracle Virtual Operating System Services

13354082 - 11203_ACFS: REPLICATION FAIL TO RESUME AFTER ASM INST RESTART ON STANDBY

13420224 - SYMC - DB CRASHES IN RUN/STARTUP WHEN DISK IN MIRROR BECOMES UNAVAILABLE

Universal Storage Management

13025879 - UNABLE TO CREATE ACFS VOLUME DUE TO INCORRECT GROUP ON ACFS CONTROL FILES.

13146560 - UEK -300 SUPPORT FOR ACFS

13243172 - LNX64-12.1-ADVM:OPEN VOLUME HUNG,VOLUME WAS CREATED ON MULTIPATH DISK

13247273 - W2K8_11203_ACFS: FAIL TO STOP REPLICATION BACKGROUND PROCESSES

13258062 - ACFS FAILS, BRINGS DOWN ASM AND RDBMS,

13410987 - FSCK NOT ENDING ON ACFS VOLUME

13502441 - ACFS RECOVERY CALLBACK CAN SOMETIMES BE SKIPPED

13637590 - ADVM IO ERROR HANDLING:PBUCKET_HEADER->SPLIT_COUNT < PMASTER_BLOCK->DOUBLE_COUNT

13886023 - GI PSU 11.2.0.3.2 RC FAILS TO INSTALL ON 32-BIT 2.6.32-300 KERNEL DUE TO ACFS

7 Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Patch 13696251 - 11.2.0.3.2 GI Patch Set UpdateRelease 11.2.0.3.2 for Grid Infrastructure

Copyright © 2006, 2012, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Copyright © 2006, 2012, Oracle and/or its affiliates. All rights reserved.