Patch 13696242 - 11.2.0.2.6 GI Patch Set Update (Includes Database PSU 11.2.0.2.6)
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.2.6, see these related documents that are available at My Oracle Support (http://support.oracle.com/):
Note 854428.1 Patch Set Updates for Oracle Products
Note 1272288.1 11.2.0.2.X Grid Infrastructure Bundle/PSU Known Issues
This document includes the following sections:
Grid Infrastructure (GI) Patch Set Update (PSU) patches are cumulative, and include the DB PSU (and associated CPUs).
GI PSU 11.2.0.2.6 includes the fixes listed in Section 6, "Bugs Fixed by This Patch".
GI PSU patches can be installed in an Oracle RAC rolling fashion.
This patch is Data Guard Standby-First Installable. See My Oracle Support Note 1265700.1 Oracle Patch Assurance - Data Guard Standby-First Patch Apply for details on how to remove risk and reduce downtime when applying this patch.
Table 1 describes installation types and security content. For each installation type, it indicates the most recent PSUs, 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 PSUs is listed, then apply that or any later PSUs patch to be current with security fixes.
Table 1 Installation Types and Security Content
| Installation Type | Latest PSU with Security Fixes |
|---|---|
|
Server homes |
11.2.0.2.6 GI PSU |
|
Grid Infrastructure home |
11.2.0.2.6 GI PSU |
|
Client-Only Installations |
PSU 11.2.0.2.2 for certain configurations. See My Oracle Support Note: 1313771.1 TCPS configurations pertaining to the April 2011 CPU and PSU Patches for further information. |
|
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.) |
This section includes the following sections:
You must satisfy the conditions in the following sections before applying the patch:
You must use the OPatch utility version 11.2.0.1.5 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 GI PSU 11.2.0.2.6 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 or Oracle RAC One Node database homes and the GI home that are being patched. To update Opatch, use the following instructions. |
Download the OPatch utility to a temporary directory.
For each Oracle RAC or Oracle RAC One Node 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.1.5 or later.
For information about OPatch documentation, including any known issues, see My Oracle Support Note 293369.1 OPatch documentation list.
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) and you wish to use one during the patch application, 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.
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. The command will fail if the Oracle Inventory is not set up properly. If this happens, contact Oracle Support Services for assistance.
If you have not already done so, download OPatch 11.2.0.1.5 or later, as explained in Section 2.1.1, "OPatch Utility Information".
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 GI PSU 11.2.0.2.6 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. In the absence of a shared location, the patch should be copied to each node and unzipped on each node. It is not necessary to have the patch in same location on each node.
|
Note: Do not unzip the GI PSU 11.2.0.2.6 patch in the top level/tmp directory. |
The unzipped patch location should be empty and 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 GI PSU 11.2.0.2.6 patch as grid home owner in a shared location. As the Grid home owner execute:
$ unzip p13696242_112020_<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 GI PSU 11.2.0.2.6 patch as grid home owner in a shared location. As the Grid home owner execute:
$ unzip p13696242_112020_<platform>.zip
The PSU patch may include multiple patches and you may notice that there are multiple directories created with distinct bug numbers.
The Opatch utility has automated the patch application for the Oracle Grid Infrastructure (GI) home and the Oracle RAC or Oracle RAC One Node database homes. It operates by querying existing configurations and automating the steps required for patching each Oracle RAC or Oracle RAC One Node 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 or Oracle RAC One Node 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 or Oracle RAC One Node database homes, or both GI and Oracle RAC or Oracle RAC One Node 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 or Oracle RAC One Node database homes of the same version:
# opatch auto <UNZIPPED_PATCH_LOCATION>
To patch only the GI home:
# opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME>
To patch one or more Oracle RAC or Oracle RAC One Node database homes:
# opatch auto <UNZIPPED_PATCH_LOCATION> -oh <ORACLE_HOME>, <ORACLE_HOME2>
To roll back the patch from the GI home and each Oracle RAC or Oracle RAC One Node database home:
# opatch auto <UNZIPPED_PATCH_LOCATION> -rollback
To roll back the patch from the GI home:
# opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME> -rollback
To roll back the patch from the Oracle RAC or Oracle RAC One Node database home:
# opatch auto <UNZIPPED_PATCH_LOCATION> -oh <ORACLE_HOME> -rollback
You should use the -ocmrf option in the opatch auto command to install patches in silent mode.
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".
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 PSU, 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:
In the unzipped directory as in Section 2.1.5.
$ opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir ./13696242
The report will indicate the patches that conflict with PSU 13696242 and the patches for which PSU 13696242 is a superset.
Note that Oracle proactively provides GI PSU 11.2.0.2.6 one-off patches for common conflicts.
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.
When all the one-off patches that you have requested are available at My Oracle Support, proceed with Section 2.4, "Patch Installation".
This section will guide you through the steps required to apply this GI PSU 11.2.0.2.6 patch to Oracle RAC or Oracle RAC One Node database homes, the Grid home, or all relevant homes on the cluster.
|
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 patch instructions will differ based on the configuration of the Grid infrastructure and the Oracle RAC or Oracle RAC One Node 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 or Oracle RAC One Node database home is shared or non-shared
The Oracle RAC or Oracle RAC One Node database home software is on ACFS or non-ACFS file systems.
Patch all the Oracle RAC or Oracle RAC One Node 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 or Oracle RAC One Node 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 1: Patching Oracle RAC or Oracle RAC One Node Database Homes and the GI Home Together
Case 2: Patching Oracle RAC or Oracle RAC One Node Database Homes
Case 6: Patching a Software Only Oracle RAC or Oracle RAC One Node Home Installation
Case 1: Patching Oracle RAC or Oracle RAC One Node Database Homes and the GI Home Together
Follow the instructions in this section if you would like to patch all the Oracle RAC or Oracle RAC One Node database homes of release version 11.2.0.2 and the 11.2.0.2 GI home.
Case 1.1: 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 or Oracle RAC One Node databases which depend on GI stack, ASM for data files, or an ACFS file system. |
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>
ORACLE_HOME: Complete path of the Oracle database home.
Make sure the ACFS file systems are unmounted on all the nodes. Use instructions in Section 2.8 for unmounting ACFS file systems.
As root user, execute the following on all the remote nodes to stop the CRS stack:
# <GI_HOME>/bin/crsctl stop crs
Patch the GI home.
On local node, as root user, execute the following command:
# opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME>
On the remote node, as root user, run:
# <GI_HOME>/crs/install/rootcrs.pl -patch
This step must be done after the first node is patched (Step 4), but before the stack is started on the remote nodes (Step 6).
opatch auto does not need to be run again because the GI home is already updated.
Start the Oracle GI stack on all the remote nodes.
As root user execute:
# <GI_HOME>/bin/crsctl start crs
Mount ACFS file systems. See Section 2.9.
For each Oracle RAC or Oracle RAC One Node database home, execute the following command on each node if the database home software is not shared.
For each database home execute the following as root user:
# opatch auto <UNZIPPED_PATCH_LOCATION> -oh <ORACLE_HOME>
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. |
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 1.2: GI Home Is Not Shared
Case 1.2.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>
Case 1.2.2A: Patching the GI Home and Database Home Together, the GI Home Is Not Shared, the Database Home Is Shared on ACFS
From the Oracle database home, make sure to stop the Oracle RAC or Oracle RAC One Node databases running on all nodes.
As the database home owner execute:
$ <ORACLE_HOME>/bin/srvctl stop database –d <db-unique-name>
On the 1st node, unmount the ACFS file systems. Use instructions in Section 2.8 for unmounting ACFS file systems.
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>
On the 1st node, remount ACFS file systems. See Section 2.9 for instructions.
On the 1st node, apply the patch to the Database home using the opatch auto command. This operation will patch the Database home across the cluster given that it is a shared ACFS home.
As root user, execute the following command:
# opatch auto <UNZIPPED_PATCH_LOCATION> -oh <ORACLE_HOME>
On the 1st node only, restart the Oracle database which 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>
On the 2nd (next) node, unmount the ACFS file systems. Use instructions in Section 2.8 for unmounting ACFS file systems.
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>
On the 2nd node, running the opatch auto command in Step 8 will restart the stack.
On the 2nd node, remount ACFS file systems. See Section 2.9 for instructions.
On the 2nd node only, restart the Oracle database which 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>
Repeat Steps 7 through 10 for all remaining nodes of the cluster.
Case 1.2.2B: Patching the 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:
On the local node, unmount the ACFS file systems. Use instructions in Section 2.8 for unmounting ACFS file systems.
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>
This operation will patch both the CRS home and the Database home.
The opatch auto command will restart the stack on the local node and restarts the Database on the local node.
Repeat Steps 1 through 3 for all remaining nodes of the cluster.
Case 2: Patching Oracle RAC or Oracle RAC One Node Database Homes
You should use the following instructions if you prefer to patch Oracle RAC or Oracle RAC One Node databases alone with this GI PSU 11.2.0.2.6 patch.
Case 2.1: Non-Shared Oracle RAC or Oracle RAC One Node Database Homes
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>
The opatch auto command stops the database instance on each node during the Oracle RAC or Oracle RAC One Node database patching. So there is no need to perform an explicit stop on database instances.
Case 2.2: Shared Oracle RAC or Oracle RAC One Node Database Homes
Make sure to stop the databases running from the Oracle RAC or Oracle RAC One Node 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>
As root user execute only on the local node.
# opatch auto <UNZIPPED_PATCH_LOCATION> -oh <Comma separated Oracle home paths>
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 GI PSU 11.2.0.2.6 patch.
Case 3.1: 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 or Oracle RAC One Node databases that depend on the GI stack, ASM for data file, or ACFS file system for database software. |
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>
Make sure the ACFS file systems are unmounted on all the nodes. Use instructions in Section 2.8 for unmounting ACFS file systems.
As root user, execute the following on all the remote nodes to stop the CRS stack:
# <GI_HOME>/bin/crsctl stop crs
Execute the following command on the local node
As root user execute:
# opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME>
On the remote node, as root user, run:
# <GI_HOME>/crs/install/rootcrs.pl -patch
This step must be done after the first node is patched (Step 4), but before the stack is started on the remote nodes (Step 6).
opatch auto does not need to be run again because the GI home is already updated.
Start the Oracle GI stack on all the remote nodes.
As root user execute:
# <GI_HOME>/bin/crsctl start crs
Mount ACFS file systems. See Section 2.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 3.2: Non-Shared GI Home
If the GI home is not shared then use the following instructions to patch the home.
Case 3.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 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>
Case 3.2.2: ACFS File System Is Configured
Repeat Steps 1 through 5 for each node in the cluster:
From the Oracle database home, stop the Oracle RAC or Oracle RAC One Node database running on that node.
As the database home owner execute:
$ <ORACLE_HOME>/bin/srvctl stop instance –d <db-unique-name> -n <node_name>
Unmount all ACFS file systems on this node using instructions in Section 2.8.
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>
Remount ACFS file systems on that node. See Section 2.9 for instructions.
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>
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 the ACFS software in an Oracle Restart home, which is not the case in all installations. This is regardless of whether or not opatch auto is being used to patch the GI home.
For each node, perform the following steps to patch Oracle Restart home:
On the local node, unmount the ACFS file systems. Use instructions in Section 2.8 for unmounting ACFS file systems.
Stop the has stack:
# crsctl stop has
Run <GridHome>/bin/acfsroot install.
As root user execute:
# opatch auto <UNZIPPED_PATCH_LOCATION> -oh <ORACLE_HOME>
Case 5: Patching a Software Only GI Home Installation
Apply the CRS patch using.
As the GI home owner execute:
$ <GI_HOME>/OPatch/opatch napply -oh <GI_HOME> -local <UNZIPPED_PATCH_LOCATION>/13696242
As the GI home owner execute:
$ <GI_HOME>/OPatch/opatch napply -oh <GI_HOME> -local <UNZIPPED_PATCH_LOCATION>/13696224
Case 6: Patching a Software Only Oracle RAC or Oracle RAC One Node Home Installation
Run the pre script for DB component of the patch.
As the database home owner execute:
$ <UNZIPPED_PATCH_LOCATION>/13696242/custom/server/13696242/custom/scripts/prepatch.sh -dbhome <ORACLE_HOME>
Apply the DB patch.
As the database home owner execute:
$ <ORACLE_HOME>/OPatch/opatch napply -oh <ORACLE_HOME> -local <UNZIPPED_PATCH_LOCATION>/13696242/custom/server/13696242 $ <ORACLE_HOME>/OPatch/opatch napply -oh <ORACLE_HOME> -local <UNZIPPED_PATCH_LOCATION>/13696224
Run the post script for DB component of the patch.
As the database home owner execute:
$ <UNZIPPED_PATCH_LOCATION>/13696242/custom/server/13696242/custom/scripts/postpatch.sh -dbhome <ORACLE_HOME>
After installing the patch, perform the following actions:
Apply conflict resolution patches as explained in Section 2.5.1.
Load modified SQL files into the database, as explained in Section 2.5.2.
Upgrade Oracle Recovery Manager catalog, as explained in Section 2.5.3.
Apply the patch conflict resolution one-off patches that were determined to be needed when you performed the steps in Section 2.3, "One-off Patch Conflict Detection and Resolution".
The following steps load modified SQL files into the database. For an Oracle RAC or Oracle RAC One Node environment, perform these steps on only one node.
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.
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".
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;
These instructions are for a database that is created or upgraded after the installation of GI PSU 11.2.0.2.6.
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.
You can use the following steps to roll back GI and GI PSU 11.2.0.2.6 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 or Oracle RAC One Node 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 1: Rolling Back the Oracle RAC or Oracle RAC One Node Database Homes and GI Homes Together
Case 2: Rolling Back from the Oracle RAC or Oracle RAC One Node Database Homes
Case 5: Rolling Back the Patch from a Software Only GI Home Installation
Case 1: Rolling Back the Oracle RAC or Oracle RAC One Node 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 or Oracle RAC One Node database homes of release version 11.2.0.2 and the 11.2.0.2 GI home.
Case 1.1 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 or Oracle RAC One Node databases that depend on the GI stack, ASM for data file, or ACFS file system. |
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>
ORACLE_HOME: Complete path of the Oracle database home.
Make sure the ACFS file systems are unmounted on all the nodes. Use instructions in Section 2.8 for un-mounting ACFS file systems.
As root user, execute the following on all the remote nodes to stop the CRS stack:
# <GI_HOME>/bin/crsctl stop crs
Rollback 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
On the remote node, as root user, run:
# <GI_HOME>/crs/install/rootcrs.pl -patch
This step must be done after the first node is patched (Step 4), but before the stack is started on the remote nodes (Step 6).
opatch auto does not need to be run again because the GI home is already updated.
Start the Oracle GI stack on all the remote nodes.
As root user execute:
# <GI_HOME>/bin/crsctl start crs
Mount ACFS file systems. See Section 2.9.
For each Oracle RAC or Oracle RAC One Node database home, execute the following command on each node if the database home software is not shared.
For each database home, execute the following as root user:
# opatch auto <UNZIPPED_PATCH_LOCATION> -oh <ORACLE_HOME> -rollback
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. |
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 1.2: GI Home Is Not Shared
Case 1.2.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
Case 1.2.2A: Rolling Back the GI Home and Database Home Together, the GI Home Is Not Shared, the Database Home Is Shared on ACFS
From the Oracle database home, make sure to stop the Oracle RAC or Oracle RAC One Node databases running on all nodes.
As the database home owner execute:
$ <ORACLE_HOME>/bin/srvctl stop database –d <db-unique-name>
On the 1st node, unmount the ACFS file systems. Use instructions in Section 2.8 for unmounting ACFS file systems.
On the 1st node, roll back 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> -rollback
On the 1st node, remount ACFS file systems. See Section 2.9 for instructions.
On the 1st node, roll back the patch to the Database home using the opatch auto command. This operation will patch the Database home across the cluster given that it is a shared ACFS home.
As root user, execute the following command:
# opatch auto <UNZIPPED_PATCH_LOCATION> -oh <ORACLE_HOME> -rollback
On the 1st node only, restart the Oracle database which 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>
On the 2nd (next) node, unmount the ACFS file systems. Use instructions in Section 2.8 for unmounting ACFS file systems.
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
On the 2nd node, running the opatch auto command in Step 8 will restart the stack.
On the 2nd node, remount ACFS file systems. See Section 2.9 for instructions.
On the 2nd node only, restart the Oracle database which 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>
Repeat Steps 7 through 10 for all remaining nodes of the cluster.
Case 1.2.2B: Rolling Back the 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:
On the local node, unmount the ACFS file systems. Use instructions in Section 2.8 for unmounting ACFS file systems.
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
This operation will patch both the CRS home and the Database home.
The opatch auto command will restart the stack on the local node and restarts the Database on the local node.
Repeat Steps 1 through 3 for all remaining nodes of the cluster.
Case 2: Rolling Back from the Oracle RAC or Oracle RAC One Node Database Homes
You should use the following instructions if you prefer to rollback the patch from Oracle RAC or Oracle RAC One Node databases homes alone.
Case 2.1: Non-Shared Oracle RAC or Oracle RAC One Node Database Homes
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
Case 2.2: Shared Oracle RAC or Oracle RAC One Node Database Homes
Make sure to stop the databases running from the Oracle RAC or Oracle RAC One Node database homes from which you would like to rollback 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>
As root user execute only on the local node.
# opatch auto <UNZIPPED_PATCH_LOCATION> -oh <Comma separated Oracle home paths> -rollback
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: Rolling Back from the GI Home Alone
You should use the following instructions if you prefer to rollback patch from the Oracle GI (Grid Infrastructure) home alone.
Case 3.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 or Oracle RAC One Node databases that depend on the GI stack, ASM for data file, or ACFS file system for database software. |
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>
Make sure the ACFS file systems are unmounted on all the nodes. Use instructions in Section 2.8 for unmounting ACFS file systems.
As root user, execute the following on all the remote nodes to stop the CRS stack:
# <GI_HOME>/bin/crsctl stop crs
Execute the following command on the local node.
As root user execute:
# opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME> -rollback
On the remote node, as root user, run:
# <GI_HOME>/crs/install/rootcrs.pl -patch
This step must be done after the first node is patched (Step 4), but before the stack is started on the remote nodes (Step 6).
opatch auto does not need to be run again because the GI home is already updated.
Start the Oracle GI stack on all the remote nodes.
As root user execute:
# <GI_HOME>/bin/crsctl start crs
Mount ACFS file systems. See Section 2.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 3.2: Non-Shared GI Home
If the GI home is not shared, then use the following instructions to rollback the patch from the GI home.
Case 3.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
Case 3.2.2: ACFS File System Is Configured
Repeat Steps 1 through 5 for each node in the cluster:
From the Oracle database home, stop the Oracle RAC or Oracle RAC One Node database running on that node.
As the database home owner execute:
$ <ORACLE_HOME>/bin/srvctl stop instance -d <db-unique-name> -n <node_name>
Make sure the ACFS file systems are unmounted on that node. Use instructions in Section 2.8 for unmounting ACFS file systems.
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
Remount ACFS file systems on that node. See Section 2.9 for instructions.
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 4: 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.
As root user execute:
# opatch auto <UNZIPPED_PATCH_LOCATION> -oh <ORACLE_HOME> -rollback
Case 5: Rolling Back the Patch from a Software Only GI Home Installation
Roll back the CRS patch.
As the GI home owner execute:
$ <GI_HOME>/OPatch/opatch rollback -local -id 13696242 -oh <GI_HOME> $ <GI_HOME>/OPatch/opatch rollback -local -id 13696224 -oh <GI_HOME>
Case 6: Rolling Back the Patch from a Software Only Oracle RAC or Oracle RAC One Node Home Installation
Run the pre script for DB component of the patch.
As the database home owner execute:
$ <UNZIPPED_PATCH_LOCATION>/13696242/custom/server/13696242/custom/scripts/prepatch.sh -dbhome <ORACLE_HOME>
Roll back the DB patch from the database home.
As the database home owner execute:
$ <ORACLE_HOME>/OPatch/opatch rollback -local -id 13696242 -oh <ORACLE_HOME> $ <ORACLE_HOME>/OPatch/opatch rollback -local -id 13696224 -oh <ORACLE_HOME>
Run the post script for DB component of the patch.
As the database home owner execute:
$ <UNZIPPED_PATCH_LOCATION>/13696242/custom/server/13696242/custom/scripts/postpatch.sh -dbhome <ORACLE_HOME
ACFS file systems can be used by Oracle RAC or Oracle RAC One Node 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.
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"
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:
# crsctl stop res <acfs file system resource name> -n <nodename>
If the ACFS file system is not used for Oracle Database software and is registered in the ACFS registry, perform the following steps.
Execute the following command to find all ACFS file system mount points.
As the root user execute:
# /sbin/acfsutil registry
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: |
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"
If the ACFS file system is used by Oracle database software, then perform Steps 1 and 2.
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"
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:
# crsctl start res <acfs file system resource name> -n <nodename>
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.
Execute the following command to find all ACFS file system mount points.
As the root user execute:
# /sbin/acfsutil registry
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: |
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.:
Start all database instances running from the Oracle home. (For more information, see Oracle Database Administrator's Guide.)
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 or Oracle RAC One Node environment, the name of the rollback script will have the format catbundle_PSU_<database SID PREFIX>_ROLLBACK.sql.
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".
All other instances can be started and accessed as usual while you are executing the deinstallation steps.
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 1272288.1 11.2.0.2.X Grid Infrastructure Bundle/PSU Known Issues.
Other known issues are as follows.
Known Issues for Opatch Auto
Bug 10339274 - 'OPATCH AUTO' FAILED TO APPLY 11202 PATCH ON EXADATA RAC CLUSTER WITH 11201 RAC
Bug 10339251 - MIN OPATCH ISSUE FOR DB HOME SETUP IN EXADATA RAC CLUSTER USING 'OPATCH AUTO'
These two issues are observed in an environment where lower version database homes coexist with 11202 clusterware and database homes and opatch auto is used to apply the 11202 GIBundle.
Workaround:
Apply the 11202 GIBundle to the 11202 GI Home and Oracle RAC or Oracle RAC One Node database home as follows:
# opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME> # opatch auto <UNZIPPED_PATCH_LOCATION> -oh <11202 ORACLE_HOME>,<11202 ORACLE_HOME>
Bug 10226210 (11,11.2.0.2GIBTWO) 11202_GI_OPATCH_AUTO: OPATCH TAKES MORE STORAGE SPACE AFTER ROLLBACK SUCCEED
Workaround:
Execute the following command as Oracle home owner after a successful rollback to recover the storage used by the backup operation:
$ opatch util cleanup -silent
Bug 11799240 - 11202_GIBTWO:STEP 3 FAILED,CAN'T ACCESS THE NEXT OUI PAGE DURING SETTING UP GI
After applying GI PSU 11.2.0.2.6, the Grid Infrastructure Configuration Wizard fails with error INS-42017 when choosing the nodes of the cluster.
Workaround:
Apply the one off patch for the bug 10055663.
Bug 11856928 - 11202_GIBTWO_HPI:PATCH SUC CRS START FAIL FOR PERM DENY TO MKDIR $EXTERNAL_ORACL
This issue is seen only on the HPI platform when the opatch auto command is invoked from a directory that does not have write permission to the root user.
Workaround:
Execute the opatch auto from a directory that has write permission to the root user.
The following ignorable errors may be encountered while running the catbundle.sql script or its rollback script:
ORA-29809: cannot drop an operator with dependent objects ORA-29931: specified association does not exist ORA-29830: operator does not exist ORA-00942: table or view does not exist ORA-00955: name is already used by an existing object ORA-01430: column being added already exists in table ORA-01432: public synonym to be dropped does not exist ORA-01434: private synonym to be dropped does not exist ORA-01435: user does not exist ORA-01917: user or role 'XDB' does not exist ORA-01920: user name '<user-name>' conflicts with another user or role name ORA-01921: role name '<role name>' conflicts with another user or role name ORA-01952: system privileges not granted to 'WKSYS' ORA-02303: cannot drop or replace a type with type or table dependents ORA-02443: Cannot drop constraint - nonexistent constraint ORA-04043: object <object-name> does not exist ORA-29832: cannot drop or replace an indextype with dependent indexes ORA-29844: duplicate operator name specified ORA-14452: attempt to create, alter or drop an index on temporary table already in use ORA-06512: at line <line number>. If this error follow any of above errors, then can be safely ignored. ORA-01927: cannot REVOKE privileges you did not grant
Bug 12619571 - 11202_GIBTHREE: PATCH FAILED IN MULTI-BYTES LANG ENV ISSUE SHOULD BE DOCUMENTED
This issue is seen when trying to run opatch auto to apply the GI PSU patch in the Japanese environment. The cause of the problem is that opatch auto currently only supports the English language environment.
Workaround:
Always keep the environment as the English language environment when running opatch auto to apply the GI PSU.
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
Steps for Applying the Patch
|
Note: You must stop the EM agent processes running from the database home, prior to patching the Oracle RAC or Oracle RAC One Node 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 |
Execute the following on each node of the cluster in non-shared CRS and DB home environment to apply the patch.
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. |
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
Apply the CRS patch using.
As the GI home owner execute:
$ <GI_HOME>/OPatch/opatch napply -oh <GI_HOME> -local <UNZIPPED_PATCH_LOCATION>/13696242
As the GI home owner execute:
$ <GI_HOME>/OPatch/opatch apply -oh <GI_HOME> -local <UNZIPPED_PATCH_LOCATION>/13696224
Run the pre script for DB component of the patch.
As the database home owner execute:
$ <UNZIPPED_PATCH_LOCATION>/13696242/custom/server/13696242/custom/scripts/prepatch.sh -dbhome <ORACLE_HOME>
Apply the DB patch.
As the database home owner execute:
$ <ORACLE_HOME>/OPatch/opatch napply -oh <ORACLE_HOME> -local <UNZIPPED_PATCH_LOCATION>/13696242/custom/server/13696242 $ <ORACLE_HOME>/OPatch/opatch apply -oh <ORACLE_HOME> -local <UNZIPPED_PATCH_LOCATION>/13696224
Run the post script for DB component of the patch.
As the database home owner execute:
$ <UNZIPPED_PATCH_LOCATION>/13696242/custom/server/13696242/custom/scripts/postpatch.sh -dbhome <ORACLE_HOME>
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
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
Execute the following on each node of the cluster in non-shared CRS and DB home environment to rollback the patch.
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. |
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
Roll back the CRS patch.
As the GI home owner execute:
$ <GI_HOME>/OPatch/opatch rollback -local -id 13696242 -oh <GI_HOME> $ <GI_HOME>/OPatch/opatch rollback -local -id 13696224 -oh <GI_HOME>
Run the pre script for DB component of the patch.
As the database home owner execute:
$ <UNZIPPED_PATCH_LOCATION>/13696242/custom/server/13696242/custom/scripts/prepatch.sh -dbhome <ORACLE_HOME>
Roll back the DB patch from the database home.
As the database home owner execute:
$ <ORACLE_HOME>/OPatch/opatch rollback -local -id 13696242 -oh <ORACLE_HOME> $ <ORACLE_HOME>/OPatch/opatch rollback -local -id 13696224 -oh <ORACLE_HOME>
Run the post script for DB component of the patch.
As the database home owner execute:
$ <UNZIPPED_PATCH_LOCATION>/13696242/custom/server/13696242/custom/scripts/postpatch.sh -dbhome <ORACLE_HOME>
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
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>
This patch includes the following bug fixes:
CPU molecules in GI PSU 11.2.0.2.6:
GI PSU 11.2.0.2.6 contains all molecules previously released in GI PSU 11.2.0.2.5 and the following new GI PSU 11.2.0.2.6 molecules:
13769501 - DB-11.2.0.2-MOLECULE-019-CPUAPR2012
13769502 - DB-11.2.0.2-MOLECULE-020-CPUAPR2012
13769503 - DB-11.2.0.2-MOLECULE-021-CPUAPR2012
13769504 - DB-11.2.0.2-MOLECULE-022-CPUAPR2012
13769505 - DB-11.2.0.2-MOLECULE-023-CPUAPR2012
13769506 - DB-11.2.0.2-MOLECULE-024-CPUAPR2012
13769507 - DB-11.2.0.2-MOLECULE-025-CPUAPR2012
13769508 - DB-11.2.0.2-MOLECULE-026-CPUAPR2012
13769509 - DB-11.2.0.2-MOLECULE-027-CPUAPR2012
13769510 - DB-11.2.0.2-MOLECULE-028-CPUAPR2012
GI PSU 11.2.0.2.6 contains the following new fixes:
Automatic Storage Management
10089333 - "INIT_HEAP_KFSG" MEMORY LEAKS ON DB INSTANCE USING ASM .
13476583 - AFTER REBALANCE DISK WENT OFFLINE
Buffer Cache Management
12748240 - FIX FOR BUG 12748240
12780098 - FIX FOR BUG 12780098
13503598 - FIX FOR BUG 13503598
Generic
8672862 - ORA-7445 [QCTOSOP] USING LIKE OPERATOR WITH PATCH FOR BUG 7174167 APPLIED
9824435 - ORA-600: INTERNAL ERROR CODE, ARGUMENTS: [KOKEGPINLOB1]
9895207 - RCA ON INSTANCE TERMINATION
9906422 - COMPLEX QUERY FAILS WITH ORA-600 [QCTVCO:CSFORM]
9972680 - OCISERVERATTACH CALLS GENERATE .TRC WITH PROTO/DTY NEGOTIATION 3113 IN 11.2.0.1
10013177 - FUNCTIONAL INDEX CAUSES MAX DECODE GROUP BY SQL TO TRUNCATE VALUES
10322959 - ORA-7445 [PFRUST()+339] AND ORA-7445 [PFRLN0ITINIT()+68] RUNNING PL/SQL
11695416 - ORA-1791 ERROR PREVENTING THE COMPILATION OF FORMS
11716621 - ORA-600 KXHFADDCHUNK1 FOR HASH JOIN QUERY WITH MANUAL MEMORY AND SHARED SERVER
11867127 - ORA-00600:[KGLLOCKOWNERSLISTAPPEND-OVF] SIGNALED IN DATABASE INSTANCES
12633340 - RISK SESSION SPIKE - LIBRARY CACHE LOCK AND LIBRARY CACHE: MUTEX X
12737666 - ORA-00600 [QESRCRO_DOL2RO]
12976376 - MEMORY LEAK IN SHARED CURSOR LAYER: "KKSFBC:HASH1"
High Availability
9835264 - AROLTP-D: HIT READMOSTLY BUG ORA-00600 [KJBMOCVT:RID]
9869287 - PHSB: RMAN BACKUP HUNG ON ADG
9965655 - AROLTP-C: LMS0 HIT ORA-00600 [KJBRPRMEXPACK]
10121589 - KCL_RECONFIG_REMASTER_CHK IS CALLED W/ NULL KEY
13554409 - FIX FOR BUG 13554409
Oracle Portable ClusterWare
10121931 - 11202_SOLX64: DBCA CONFIGURE DATABASE OPTION DISABLED IF 11201 DATABASE PRESENT
10374874 - RBAL GOT UNRESPONSIVE WAITING FOR A RESPONSE FROM OCSSD
10379703 - RDBMS INSTALLER FAILS USER EXISTENCE PRE-REQ CHECK
11077756 - STARTUP FAILURE OF HAIP CAUSES INSTALLATION FAILURE
11664015 - 11202_GIBTWO: EVMD AND CTSSD SHOULD TOLERATE GIPCD GOING TO INTERMEDIATE STATE.
11724464 - CRSCTL STOP CLUSTERWARE FAILS TO STOP, ACFS WONT CLEAN
12398492 - SIHA DOES NOT SET ULIMIT FOR MEMLOCK
12425730 - AIX-11203-GIPC:HAIP START COMMAND ABORTED ON THE HEALTHY NODE
12538907 - ORAAGENT KEEPS EXITING AFTER APPLYING PATCH 12347844
12605690 - LNX64-11203: LOCAL VIP FAILOVER TOOK 16 MINS AFTER BROUGHT DOWN PUBLIC NIC
12709476 - 11202_GIBTHREE_HPI:CRSD ORAAGENT MEMORY LEAK AT 1.5M/1.2H ON NON-PE NODES
13036424 - CHMOS HAS AN ERROR IN CALCULATING THE TOTAL NUMBER OF OPEN FDS ON A SYSTEM
13446398 - 112025_GIPSU:FILE PERMISSION AFTER APPLY CHANGED:DECONFIG
13635562 - TOO MAY CORE FILES GENERATED BY OLOGGERD AFTER JAN 2012 PSU
10121589 - KCL_RECONFIG_REMASTER_CHK IS CALLED W/ NULL KEY
Oracle Security
11683713 - INVALID NAMESPACE ERROR WHEN UPDATE NAMESPACE ATTRIBUTES
Oracle Space Management
9401552 - FOUND ORA-00600:[KTSLA_CACHE_CHECK_DUPS-1] IN DATABASE INSTANCE
11937253 - PQ FAILS WITH ORA-12801 AND ORA-8103 IN ACTIVE DATAGUARD
Oracle Utilities
10126822 - 11.2.0.1 DEFERRED SEGMENT CREATION ERROR
Oracle Virtual Operating System Services
11924400 - ORA-00600 [KSFDRFMS3] STARTING DG BROKER WITH ODM ON PRIMARY
12539000 - 11203:ASM UPGRADE FAILED ON FIRST NODE WITH ORA-03113
Universal Storage Management
9758286 - REVIEW READAHEAD ALGORITHM
12810890 - AIX-11203-ACFS: WRITE ISSUES ON ASM CLUSTER FILE SYSTEM (ACFS)
13025879 - UNABLE TO CREATE ACFS VOLUME DUE TO INCORRECT GROUP ON ACFS CONTROL FILES.
13068077 - PORT RECOVERY PHASE 2 CHANGES TO AIX AND SOLARIS
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
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 13696242 - 11.2.0.2.6 GI Patch Set UpdateRelease 11.2.0.2.6 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.