Oracle Clusterware 11g Release 2 (11.2.0.2.5)
Patch for Bug# 13635562 for Linux x86-64 platform
This patch is RAC Rolling Installable.
Released: Sat Jan 28 22:02:03 2012
This document describes how you can install the patch for bug# 13635562 for Linux x86-64 on your Oracle Clusterware 11g Release 2 (11.2.0.2.0).
You can install this patch automatically using the "opatch auto" command. Automatic patching helps you reduce the number of manual steps involved in patching the Oracle homes. Technically, as a preinstallation step, automatic patching stops all the dependent databases, the CRS resources, and the entire the CRS stack. It then patches the Oracle Clusterware and all applicable databases, and then, as a postinstallation step, it automatically restarts the entire CRS stack, the CRS Resources, the the dependent databases.
Note:
- Oracle recommends you to avoid applying any temporary patch unless you are directed by Oracle Support who have reviewed your environment and determined that it is applicable.
- A non-clustered RDBMS home runing the CSSD and ASM may also benefit from a number of the CRS home patches.
This document includes the following sections:
Section 1, "Patch Installation and Deinstallation"
Section 2, "Known Issues"
Section 3, "References"
Section 4, "Bugs Fixed by This Patch"
Section 5, "Appendix A: Manual Steps for Apply/Rollback Patch"
Section 6, "Documentation Accessibility"
------------------------------------------
This section includes the following sections:
Section 1.1, "Patch Installation Prerequisites"
Section 1.2, "OPatch Automation"
Section 1.3, "Patch Installation"
Section 1.4, "Patch Deinstallation"
-------------------------------------
You must satisfy the conditions in the following sections before applying the patch:
1.1.1 OPatch Utility Information
---------------------------------
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.
Note : The new opatch utility should be updated in all the Oracle 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 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>
Note : If you already have OPatch utility installed, then while unzipping OPatch you will be prompted like below for which please mention "A" to override the existing files.
% unzip p6880880_112000_LINUX.X64.zip -d /u01/app/11.2.0/grid/
Archive: p6880880_112000_LINUX.X64.zip
replace OPatch/ocm/ocm.zip? [y]es, [n]o, [A]ll, [N]one, [r]ename:A
% <ORACLE_HOME>/OPatch/opatch version
The version output of the previous command should be 11.2.0.1.4 or later.
For information about OPatch documentation, including any known issues, see My Oracle Support Note 293369.1 OPatch documentation list.
1.1.2 OCM Configuration
------------------------
The OPatch utility will prompt for your OCM (Oracle Configuration Manager) response file (ocm.rsp) 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, you should run the following command to create it.
As the Grid home owner execute:
% <ORACLE_HOME>/OPatch/ocm/bin/emocmrsp
This will create the ocm.rsp file in the current directory (for example, /tmp) from which emocmrsp is executed. Provide the "complete path" when OPatch utility prompts for the OCM response file (ocm.rsp) which is /tmp/ocm.rsp as per example.
Also, please note that the same OCM response file can be used for the GI and Oracle users but need to ensure that read permission is set correctly to allow access to the response file. Or the alternative is to create a separate response file for each home.
1.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.
1.1.4 Unzipping the bundle patch (13635562)
---------------------------------------------
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.
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 p13635562_112025_Linux-x86-64.zip
For example, if <UNZIPPED_PATCH_LOCATION> in your environment is /u01/oracle/patches, enter the following commands:
% cd /u01/oracle/patches
% unzip p13635562_112025_Linux-x86-64.zip
----------------------
The OPatch utility has automated the patch application for the Oracle Grid Infrastructure (GI) home and the Oracle Database home. It operates by querying existing configurations and automating the steps required for patching each Oracle 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 Database home is in Non-shared storage.
Depending on command line options specified, one invocation of OPatch can patch the GI home, one or more Oracle Database home, or both GI and Oracle Database home 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 Database home of the same version:
# opatch auto <PATH_TO_PATCH_DIRECTORY>
To patch only the GI home:
# opatch auto <PATH_TO_PATCH_DIRECTORY> -oh <GI_HOME>
To patch one or more Oracle Database home:
# opatch auto <PATH_TO_PATCH_DIRECTORY> -oh <path to database1 home>[,<path of database2 home>]
To roll back the patch from the GI home and each Oracle Database home:
# opatch auto <PATH_TO_PATCH_DIRECTORY> -rollback
To roll back the patch from the GI home:
# opatch auto <PATH_TO_PATCH_DIRECTORY> -oh <path to GI home> -rollback
To roll back the patch from the Oracle Database home:
# opatch auto <PATH_TO_PATCH_DIRECTORY> -oh <path to database home> -rollback
For more information about opatch auto, see My Oracle Support Note 293369.1 OPatch documentation list.
For detailed patch installation instructions, see Section 1.3, "Patch Installation".
-----------------------
This section will guide you through the steps required to apply this patch to RAC database homes, the Grid home, or all relevant homes on the cluster.
Note: A shared location that is on ACFS file system will be unmounted when patching the GI home.
To install the patch, perform the actions in the following sections:
* Unmounting ACFS File Systems
* Mounting ACFS File Systems
* Patching Installation to Oracle RAC Database and/or the GI Home
1.3.1 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.
You should use the following steps to shutdown 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.
As root user execute:
# crsctl stat res -w "TYPE = ora.acfs.type"
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:
#crsctl stop res <acfs file system resource name>
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>
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"
1.3.2 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"
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:
#crsctl start res <acfs file system resource name>
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>
1.3.3 Patching Installation to Oracle RAC Database and/or the GI Home
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.2.0 and the 11.2.0.2.0 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 databases which depend on 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 1.3.1 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>
5. Start the Oracle GI stack on all the remote nodes.
As root user execute:
# <GI_HOME>/bin/crsctl start crs
6. Mount ACFS file systems. See Section 1.3.2.
7. For each Oracle RAC 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.
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 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.2: ACFS File System is Configured or Database Homes Are Shared
1. Make sure to stop the Oracle RAC databases running from the Oracle database homes.
As the database home owner execute:
% <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.3.1 for unmounting ACFS file systems.
3. Execute the following command on each node of the cluster.
As root user execute:
# opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME>
4. Mount ACFS file systems. See Section 1.3.2.
5. As root user execute the following command on the local node for the database homes that are shared or are on the ACFS file system.
# opatch auto <UNZIPPED_PATCH_LOCATION> -oh <Comma separated Oracle home paths>
As root user execute the following command on each node for the database homes that are not shared.
# opatch auto <UNZIPPED_PATCH_LOCATION> -oh <Comma separated Oracle home paths>
6. Restart the Oracle databases which 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 bundle patch.
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>
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 db -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>
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 db -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 bundle 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 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 1.3.1 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>
5. Start the Oracle GI stack on all the remote nodes.
As root user execute:
# <GI_HOME>/bin/crsctl start crs
6. Mount ACFS file systems. See Section 1.3.2.
7. 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
1. Make sure to stop the Oracle RAC databases running from the Oracle database homes.
As the database home owner execute:
% <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 1.3.1 for unmounting ACFS file systems.
Execute the following command on each node in the cluster.
As root user execute:
# opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME>
3. Mount ACFS file systems. See Section 1.3.2.
4. 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 path Oracle Restart home.
As root user execute:
# opatch auto <UNZIPPED_PATCH_LOCATION> -oh <Oracle-Restart-home>
-------------------------
You can use the following steps to rollback the patch. 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 database home owner execute:
% <ORACLE_HOME>/bin/emctl stop dbconsole
* Case 1: Rolling Back the patch from the Oracle RAC Database Homes and GI Homes Together
* Case 2: Rolling Back the patch from the Oracle RAC Database Homes
* Case 3: Rolling Back the patch from the GI Home Alone
* Case 4: Rolling Back the patch from Oracle Restart Home
Case 1: Rolling Back the patch from 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.2.0 and the 11.2.0.2.0 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 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 1.3.1 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. 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
5. Start the Oracle GI stack on all the remote nodes.
As root user execute:
# <GI_HOME>/bin/crsctl start crs
6. Mount ACFS file systems. See Section 1.3.2.
7. For each Oracle RAC 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.
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 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.2: ACFS File System Is Configured or Database Homes Are Shared
1. Make sure to stop the Oracle RAC databases running from the Oracle database homes.
As the database home owner execute:
% <ORACLE_HOME>/bin/srvctl stop database -d <db-unique-name>
2. Make sure the ACFS file systems are unmounted on all the nodes. See the instructions in Section 1.3.1 for unmounting ACFS file systems.
3. Execute the following command on each node of the cluster.
As root user execute:
# opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME> -rollback
4. Mount ACFS file systems. See Section 1.3.2.
5. As root user execute the following command on the local node for the database homes that are shared or are on the ACFS file system.
# opatch auto <UNZIPPED_PATCH_LOCATION> -oh <Comma separated Oracle home paths> -rollback
As root user execute the following command on each node for the database homes that are not shared.
# opatch auto <UNZIPPED_PATCH_LOCATION> -oh <Comma separated Oracle home paths> -rollback
6. Restart the Oracle databases which 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: Rolling Back the patch from the Oracle RAC Database Homes
You should use the following instructions if you prefer to rollback the patch from Oracle RAC databases homes alone.
Case 2.1: Non-Shared Oracle RAC 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 Database Homes
1. Make sure to stop the databases running from the Oracle RAC 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 db -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
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 db -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 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 1.3.1 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
5. Start the Oracle GI stack on all the remote nodes.
As root user execute:
# <GI_HOME>/bin/crsctl start crs
6. Mount ACFS file systems. See Section 1.3.2.
7. 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
1. Make sure to stop the Oracle RAC databases running from the Oracle database homes.
As the database home owner execute:
<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 1.3.1 for unmounting ACFS file systems.
Execute the following command on each node in the cluster.
As root user execute:
# opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI_HOME> -rollback
3. Mount ACFS file systems. See Section 1.3.2.
4. 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: 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-Restart-home> -rollback
(2) Known Issues
-----------------
For information about OPatch issues, see My Oracle Support Note 293369.1 OPatch documentation list.
Other known issues are as follows.
Issue 1: Known Issues for Opatch Auto
a)Bug 13577181- AUTO DETECTION OF THE ERRORS WHEN A USER UNZIPS THE PATCH WITH INCORRECT USER ID
The above issue is observerd when user unzips the patch with incorrect user id and invokes 'opatch auto'
for installing the patch. The errrors reported by 'opatch auto' will look like following -
patch <PATCH_DIR>/13635562/custom/server/13635562 apply successful for home /u01/app/oracle/product/11.2.0.3/dbhome_1
Successfully unlock /u01/app/11.2.0.3/grid
The opatch Applicable check failed for /u01/app/11.2.0.3/grid. The patch is not applicable for /u01/app/11.2.0.3/grid
patch <PATCH_DIR>/13635562 apply failed for home /u01/app/11.2.0.3/grid
Workaround:
Please follow the MOS note 1349160.1 for details.
b)
Bug 10339274 - 'OPATCH AUTO' FAILED TO APPLY 11202 PATCH ON RAC CLUSTER WITH 11201 RAC
Bug 10339251 - MIN OPATCH ISSUE FOR DB HOME SETUP IN 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 this 11202 bundle patch.
Workaround: Apply this patch to the 11202 GI Home and Oracle database homes as follows:
#opatch auto <UNZIPPED_PATCH_LOCATION> -oh <GI Home path>
#opatch auto <UNZIPPED_PATCH_LOCATION> -oh <11202 ORACLE_HOME1_PATH>,<11202 ORACLE_HOME1_PATH>
(3) References
---------------
The following documents are references for this patch.
Note 293369.1 OPatch documentation list
Note 224346.1 OPatch - Where Can I Find the Latest Version of OPatch?
(4) Bugs Fixed by This Patch
-----------------------------
13343447 - GI PSU 11.2.0.2.5 (INCLUDES DATABASE PSU 11.2.0.2.5)
10157506 - 11.2.0.2 GI BUNDLE1 TRACKING BUG
10178670 - SR #3-2174629171; ACFS VOLUMES ARE NOT MOUNTING ONCE RESTARTED THE SERVER
10425672 - 11.2.0.2 GI BUNDLE2 TRACKING BUG
12311357 - GI PSU 11.2.0.2.2 (INCLUDES DATABASE PSU 11.2.0.2.2)
12419353 - GI PSU 11.2.0.2.3 (INCLUDES DATABASE PSU 11.2.0.2.3)
12827731 - GI PSU 11.2.0.2.4 (INCLUDES DATABASE PSU 11.2.0.2.4)
9959110 - 11202_WINDOWS.X64_100719; GNS INTEGRITY PREREQUISITE FAILED WITH PRVF-5213
10272615 - TB;X;SHUTDOWN SERVICE CELLD ON 2 CELL NODES,CSSD ABORT IN CLSSNMRCFGMGRTHREAD
10314123 - GPNPD MAY NOT UPDATE PROFILE TO LATEST ON START
10014392 - CRSCTL DELETE NODE FAILS WITH CRS-4662 & CRS-4000
10089120 - 11202-NT_X64; WRONG PROMPT MESSAGE BY DEINSTALL COMMAND WHILE DELETING CRS HOME
10057296 - LNX64-112020-CRF;IPD SPLIT BRAIN AFTER CHANGE BDB LOCATION
11692271 - 11203-NT;PARALLEL STOP CRS STACK ON ALL NODES AND ASM STOP FAILED ON LAST NODE
9864003 - TB-CSS; NODE REBOOT DUE TO 'ORA.GNS' FAILED TO BE FENCED OFF DURING CRSD CLEANUP
11775080 - ORA-29701-29702 OCCURS WHEN WORKLOAD TEST RUNNING FOR A LONG TIME AND IS RESTART
9916145 - LX64; INTERNAL ERROR IN CRSD.LOG, MISROUTED REQUEST, ASSERT IN CLSM2M.CPP
12695202 - AIX-11202GIB3_CRS;CRSD ORAAGENT COREDUMP AT CLSN_AGENT;INSTCONNECTION;;BREAKCALL
12593451 - VIP FAILOVER TAKES OVER 30 SECONDS DUE TO CMVIEWCL TIMEOUT
10044622 - TB-SIHA-EVM;EVMD FAILED TO START AFTER KILL OHASD.BIN
11705438 - CRSCTL DELETE NODE RECEIVES CRS-4662 AND CRS-4000
10365625 - 11202_GI_BUND_CRF; OSYSMOND MEMORY LEAK AT THE SPEED OF 10MB-HOUR
12767231 - AIX-11202-GIPC DISABLE SWITCH PORT FOR ONE PRIVATE NIC,HAIP DID NOT FAILOVER
9935308 - TB-GNS; GNSD SPINS CPU (~50%) AFTER FAILOVERED TO ANOTHER NODE
12399977 - TYPO IN SUB PERFORM_START_SERVICE RETURNS ZERO (SUCCESS) EVEN WHEN FAILED
11882456 - SOL11-11203; ORA.CRF START FAILED DURING ROOT.SH
12421404 - 11.2.0.2 GI BUNDLE 3 HAS-CRS TRACKING BUG
12862012 - 11.2.0.2 GI PSU 4 HAS-CRS TRACKING BUG
11744343 - LNX64-11203-RACG; ONE DB INST GETS CLEANED DURING PARALLEL STACK START
12340700 - EVMD CONF FILES CAN HAVE WRONG PERMISSIONS AFTER INSTALL
10056713 - LNX64-11202-CSS; SPLIT BRAIN WHEN START CRS STACK IN PARALLEL WITH PRIV NIC DOWN
10637741 - HARD STOP DEPENDENCY CAN CAUSE WRONG FAIL-OVER ORDER
9939306 - SERVICES NOT COMING UP AFTER SWITCHOVER USING SRVCTL START DATABASE
9795321 - MTU SIZE FOR VIP UNDER 11GR2 GRID INFRASTRUCTURE
9902536 - LNX64-11202-MESSAGE; EXCESSIVE GNS LOGGING IN CRS ALERT FILE WHEN SELFCHECK FAIL
10007185 - LNX64-11202-CRS; GNS DUMPS CORE IN CLSKGOPANIC AT CLSKPDVA 717
10376847 - [ORA.CRF] [START] ERROR = ERROR 9 ENCOUNTERED WHEN CONNECTING TO MOND
10038791 - HAS SRG SRV GETTING MANY DIFS FOR AIX ON LABEL 100810 AND LATER
11741224 - INCORRECT ACTIVE VERSION CHECK WHILE ENABLING THE BATCH FUNCTIONALITY
12823479 - FIX CMDLINE -PROC READ FOR EACH PID
11655840 - 11202_GIBTWO;RAC1 DB STATE_DETAILS IS WRONG AFTER KILL GIPCD
10048487 - LNX64-112020-CRF; DIAGCOLLECTION CANNOT RETRIEVE IPD REPORTS
10322157 - 11202_GIBONE; PERM OF FILES UNDER $CH-CRS-SBS CHANGED AFTER PATCHED
11768599 - LNX64-11203;THE ATTRIBUTES OF CRS_HOME-CV-LOG-CVUTRACE.LOG.0 FILE ISN'T CORRECT
10260251 - GRID INSTALLATION FAILS TO START HAIP DUE TO CHANGE IN NETWORK INTERFACE NAME
10052721 - SOL-SP-11202; 11201->11202 NON-ROLLING,CRSCTL.BIN CORE AT CLSSNSQANUM, SIGNAL 11
10028235 - HAS BUILD - 'CLSNVIPAGENT.CPP', LINE 1522; ERROR; FORMAL ARGUMENT TYPE OF ...
10027079 - CRS_SHUTDOWN_SYNCH EVENT NOT SENT IN SIHA
12412303 - LNX64-11203-DIT;PERMS OF CRS_HOME-CV-LOG WERE WRONG AFTER INSTALL RAC USING 2 USERS
10357258 - SOL-11202-UD; 10205->11202 [IPMP] HUNDREDS OF DUP IP AFTER INTRA-NODE FAILOVER
11871469 - ORAAGENT CHECK TASK IS TIMING OUT WHICH IS FORCING THE AGENT TO ABORT AND EXIT
10045436 - TB-CSS; 'ORA.LISTENER.LSNR' FAILED TO BE FENCED OFF DURING CRSD CLEANUP
10231906 - 11202-OCE-SYMANTEC;DOWN ONE OF PRIVAE LINKS ON NODE 3,OCSSD CRASHED ON NODE 3
12722095 - 11202_GIB3: 'CANNOT PARSE HOSTS FROM OUTPUT' IN DIAGCOLLECTION.PL
10622973 - LOSS OF LEGACY FEATURES IN 11.2
9891341 - TB;SH CRSD CORE DUMP IN PROATH_MASTER_EXIT_HELPER AT PROATH.C;1834
10072474 - LNX64-11202-CRF;A NODE IS NOT MONITORED AFTER STOP AND START THE ORA.CRF ON IT
10036834 - 11202_SOLX64;PATCHES NOT FOUND ERROR WHILE UPGRADING GRID FROM 11201 TO 11202
10029900 - 11202-NT_X64; CVU PRE NODEADD CHECK VD ERROR
9974223 - GRID INFRASTRUCTURE NEEDS MULTICAST COMMUNICATION ON 230.0.1.0 ADDRESSES WORKING
10161846 - BC; CHM-OS; DATA COLLECTION STOPPED ON ONE CLUSTER NODE
10016083 - SOL-SP-MSG; 'OCRCONFIG -ADD' NEEDS HELPFUL MESSAGE FOR ERROR ORA-15221
12597463 - LNX64-11201; NODE SHOULD BE EVICTION WHEN CRS HOME HANG FOR SOME TIME
9918485 - LNX64-11202-DIT; EMCONFIG FAIL WITH NULLPOINTEREXCEPTION AT RACTRANSFERCORE.JAVA
11781515 - EVMD-CRSD FAIL TO START AFTER REBOOT, EVEN AFTER CRSCTL START CLUSTERWARE
10040647 - LNX64-11202-UD; AQ AND RLB DO NOT WORK AFTER UPGRADING FROM 11201
13332363 - BUG 9795321 HAS REAPPEARED IN 11.2.0.3
12651595 - STOP CRS FAILS DURING DOWNGRADE (11.2.0.3.0 TO 11.2.0.1.0)
12345151 - LNX64-11203; GIPCD COREDUMP AT GIPCDMONITORTHREAD.C;126
11925641 - SERVICES DON'T GET REGISTERED IN SUSE IN SIHA CONFIGURATION
10069541 - LNX64-112020-CRF;IPD SPLIT BRAIN AFTER STOPPING ORA.CRF ON MASTER NODE
10029119 - 11202_WINDOWS.X64_100805; 11201-11202 CRS UPGRADE OUI ASKS TO RUN ROOTUPGRADE.SH
10233159 - LNX64-112020-GIBONE;NEED 20 MINS TO STARTUP CRS WHEN 1-2 GIPC NICS DOWN
12332919 - ORAAGENT KEEPS EXITING
9812956 - TB-GIPC; STATUS OF CRSD AND EVMD GOES INTERMEDIATE FOR EVER WHEN KILL GIPC
10036193 - HPI-SG-11202; STANDBY NIC DOESN'T WORK IF DOWN PUBLIC NIC
10015210 - SUSE11-LNX64-11202;OCTSSD LEAK MEMORY 1.7M-HR ON PE MASTER DURING 23 HOURS RUNNI
12424479 - LNX64-112-CMT; VIP FAILOVER TOOK 123 SECONDS AFTER PULLED OUT TWO PUBLIC CABLES
12340501 - SRVCTL SHOWS INSTANCE AS DOWN AFTER RELOCATION
10621175 - TB_RAC_X64;X; CLSSSCEXIT; CSSD SIGNAL 11 IN THREAD GMDEATHCHECK
9686152 - TWO OF THREE RAC INSTANCES DID NOT RESTART AFTER REINSTATEMENT
12556028 - HPI_11203_CRS;CRSD LEAK MEMROY AT 8M-1.2H ON PE MASTER WITH OCR BUSY WORKLOAD RU
11877079 - HUNDREDS OF ORAAGENT.BIN@HOSTNAME SESSSIONS IN 11.2.0.2 DATABASE
8906163 - PE; NETWORK AND VIP RESOURCES FAIL TO START IN SOLARIS CONTAINERS
10111010 - CRSD HANGS FOR THE HANAME OF PEER CRSD
12366642 - DB CHECK ACTIONS TAKE A LONG TIME IF THE SHARED POOL SIZE ISN'T TUNED
11777648 - LNX64-RAC; GMON IN +ASM1, 2, 4 HANG IN 'CSS GROUP REGISTRATION' AFTER REBOOT
10115514 - SOL-X64-11202; CLIENT REGISTER IN GLOBAL GROUP MASTER#DISKMON#GROUP#MX NOT EXIT
10104377 - GIPC ENSURE INITIAL MESSAGE IS NOT LOST DURING ESTABLISH PHASE
10057680 - HPI-SG-11202 OHASD ORAROOTAGENT.BIN SPIN CPU AFTER SIMULATE ASM DISK ERROR
10280665 - TB;X;STOP CELLD ON 2 CELL NODES,CSSD ABORT IN CLSSNMVVERIFYPENDINGCONFIGVFS
10078086 - SOL-X64-11202-UD;ROOTUPGRADE.SH FAIL FOR 'CRSCTL STARTUPGRADE' FAIL,10205->11202
9944948 - HPI-GIPC-11202; START RESOUCE HAIP FAILED WHEN RUN ROOT.SH
10146768 - NETWORK RESOURCE FAILS TO START WITH IPMP ON SOLARIS 11
10052529 - 11202-NT_X64;DB INST OFFLINE AFTER STOP-START CRS STACK ON ALL NODES IN PARALLEL
10011084 - SOL-X64-11202 STEP3 MODIFY BINARY AFTER INSTALLATION CANNOT EXCUTE SUCCESSFULLY
10012319 - ORA-600 [KFDVF_CSS], [19], [542] ON STARTUP OF ASM DURING ADDNODE
10073075 - CRS-9013-ERROR DUMPNODEVIEW; INVALID DATA RECEIVED FROM THE CLUSTER LOGGER SERVI
10233811 - AFTER PATCHING GRID HOME, UNABLE TO START RESOURCES DBFS AND GOLDEN
12720728 - GIPCHALOWERPROCESSNODE; NO VALID INTERFACES FOUND TO NODE
10299006 - AFTER 11.2.0.2 UPGRADE, ORAAGENT.BIN CONNECTS TO DATABASE WITH TOO MANY SESSIONS
12426375 - ASM HANG 'GCS LOCK OPEN S'<='ENQ; FA - ACCESS FILE'
10248739 - 11202_GIBONE; AFTER APPLY THE PATCH, THE NODE EVICTED DURING START CRS STACK
10236074 - ASM INSTANCES CRASH SEVERAL TIMES DURING PARALLEL CRS STARTUP
10128191 - LRGSRG9 AND LRGSRGE FAILURE
11071429 - PORT 11GR2 CRS TO EL6
10019726 - MEMORY LEAK 1.2MB-HR IN CRSD.BIN ON NON-N NODE
9975837 - GNS INCORRECTLY PROCESSES IPV6 LOOKUP REQUESTS
10253630 - TB;X;HANG DETECTED,'WAITING FOR INSTANCE RECOVERY OF GROUP 2' FOR 45 MINUTES
12615394 - GIPC API LEAKING MEMORY IN AIX
10420872 - 11.2.0.2 GRID INFRASTRUCTURE ROOT.SH FAILS
9949676 - SOL-X64-GNS; GNSD.BIN CORE DUMP AFTER KILL ASM PMON ON ALL NODES AT SAME TIME
11936945 - CVU NOT RECOGNIZING THE OEL6 ON LINUX
11820787 - 11202_GIBTWO_LINUX;CRSCTL START RES WITH ERROR 'CRS-5010; UPDATE OF CONF FAILED'
10637483 - TB;X;REBOOT ONE CELL NODE, CSS ABORT AT CLSSNMVDDISCTHREAD
13396479 - 11.2.0.2 GI PSU 5 HAS-CRS TRACKING BUG
12677816 - 11202_GIB3; SCAN LISTENER FAILD TO STARTUP IF VAR-OPT-ORACLE-LISTENER.ORA EXIST
10157622 - 11.2.0.2 GI BUNDLE 1 HAS-CRS TRACKING BUG
11698552 - SRVCTL REPORT WRONG STATUS FOR DATABASE INSTANCE.
10385838 - TB;X;CSS CORE DUMP AT GIPCHAINTERNALSEND
10053985 - 11202_SOLX64;PROC-44; ERROR IN NETWORK ADDRESS ON SOLARIS 11
12718811 - 11202_GIBTHREE_HPI;EXECTASK COREDUMP PERIODICALLY ON NODE RUNNING ORA.CVU
10229297 - LNX64-11202-CRF; OSYSMOND.BIN CONSUMES ABOUT 7.5% CPU IN KERNEL 2.6.32
10425674 - 11.2.0.2 GI BUNDLE 2 HAS-CRS TRACKING BUG
9812970 - TB_SOL_SP-CRF;IPD DO NOT MARK TYPE OF DISKS USED FOR VOTING DISK CORRECTLY
11828633 - DATABASE SERVICE DID NOT FAIL OVER AND COULD NOT BE STARTED AFTER NODE FAILURE
12359585 - AIX-11203-HA-CSS;ROOT.SH FAIL TO START ORA.CSSD DUE TO FAILURE OF EXADATA FENCE
11899801 - 11202_GIBTWO_HPI;AFTER KILL ASM PMON, POLICY AND ADMIN DB RUNNING ON SAME SERVER
10083789 - A NODE DOESNT INITIATE A RECONFIG DUE TO INCORRECT RECONFIG STATE
12728585 - CRSCTL STOP CRS HANGS
9876201 - HPI-CRS-11202; OHASD AGENT CORE DUMP AT EONSHTTP.C;162
10073372 - LNX64-11202; DEINSTALL FAILED TO DELETE CRS_HOME ON REMOTE NODE IF OCR-VD ON NFS
9963327 - 112020PL ; HAS ; SRGSRV ; CHMOD.PL GETS CALLED INSTEAD OF CHMOD.EXE
10428946 - SUSE10-LNX64-11203;OHASD.SLES NOT FOUND WHEN RAN ROOT.SH
11077756 - STARTUP FAILURE OF HAIP CAUSES INSTALLATION FAILURE
10375649 - DISABLE HAIP ON PRIMECLUSTER
9336825 - TB-DAEMON; GPNPD FLUSH PROFILE PUSH ERROR MESSAGES IN CRS ALERT LOG
11682409 - RE-USING OCI MEMORY ACROSS CONNECTIONS CAUSES A MEMORY CORRUPTION
10062301 - AIX-11202-UD VALUE FOR FIELD 'CLUSTER_NAME' IS MISSING IN CRSCONFIG_PARAMS
12767563 - LNX64-11203-CRS; CRSD KEEPS CONSUMING HIGH CPU AFTER UPGRADED TO 11.2.0.3
12546712 - HPI_11203_CRS;ORAROOTAGENT CORE DUMP WHEN ADDING PRIV NIC BACK VIA OIFCFG SETIF
10018215 - RACONE DOES NOT SHUTDOWN INSTANCE DURING RELOCATION
10105195 - PROC-32 ACCESSING OCR; CRS DOES NOT COME UP ON NODE
10419987 - PEER LISTENER IS ACCESSING A GROCK THAT IS ALREADY DELETED
13355549 - OPATCH APPLY FAILS FOR GIPSU 11.2.0.2.4
10071992 - BC; IPDOS; UNREASONABLE VALUES FOR DISK STATISTICS
11807012 - LNX64-11203-RACG; DB SERVICE RUNS INTO 'UNKNOWN' STATE AFTER STACK START
10634513 - 11202_GIBTWO;OHASD DUMPS CORE WHEN PLUG IN UNPLUGGED PRIVATE NETWORK NIC
9926027 - TB-CSS; NODE REBOOTED AFTER CRS CLEAN-UP SUCCEEDED 11202 GI + 10205 RAC DB
10103954 - INTERMITTENT 'CANNOT COMMUNICATE WITH CRSD DAEMON' ERRORS
12743755 - SET FENCING TYPE CAUSES CSSD TO SPIN
12406573 - GRID INFRASTRUCTURE DOES NOT START AFTER REBOOT
10028343 - SOL-X64-11202-GNS GNS CAN NOT BE RELOCATED AFTER PUBLIC RESTARTED
11768055 - ONE NODE CSS JOIN CLUSTER,ALL OTHER NODES CSS ABORT FROM GM PEER LSNR
11866171 - ENABLE CRASHDUMP WHEN REBOOTING THE MACHINE (LINUX)
10065216 - TB; VIRTUAL MEMORY USAGE OF ORAROOTAGENT IS BIG(1321MB) AND NOT DECREASING
9907089 - CSS CORE DUMP DURING EXADATA ROLLING UPGRADE
9897335 - TB-ASM; UNNECCESSARY OCR OPERATION LOG MESSAGES IN ASM ALERT LOG WITH ASM OCR
10190153 - HPI-SG-11202 ORA.CTSSD AND ORA.CRSD GOES OFFLINE AFTER KILL GIPC ON CRS MASTER
11744313 - LNX64-11203-RACG; UNEXPECTED CRSD RESTART DURING PARALLEL STACK START
10175855 - LNX32-11202-UD FAILED TO UGPRADE 11.2.0.1 + ARU 12900951 -> 11.2.0.2
12600343 - ORAAGENT DAEMON CRASH ISSUE
12422324 - LNX64-112-CMT; HIT PRVF-7539 ; GROUP 'DBA' DOES NOT EXIST ON OUDA NODE
10284828 - INTERFACE UPDATES GET LOST DURING BOUNCE OF CRSD PROCESS
10028637 - SCLS.C COMPILE ERRORS ON AIX UNDECLARED IDENTIFIERS
10361177 - LNX64-11203-GNS; MANY GNS SELF CHECK FAILURE ALERT MESSAGES
12800501 - INSTANCE RESOURCE CHECK TIMED OUT AND SO RACGIMON STOPPED THE INSTANCE.
9979706 - COMP OCR CHECK FAILS TO VERIFY SIZE OF OCR LOCATION
12950415 - LNX64-11203-CRF;OSYSMOD DUMP CORE WHEN SYSTEM HAS GREATER THAN 255 MOUNT POINTS
10324594 - STATIC ENDPOINT IN THE LEASE BLOCKS OVERWRITTEN DURING UPGRADE
10015460 - REMOVAL OF WRONG INCARNATION OF A NODE DUE TO MANUAL SHUTDOWN STATE
11818524 - AT CLUSTER REBOOT, CEDING RECONFIG HAS WRONG RULES, CAUSING A STARTUP HANG
9971646 - SOL-GIPC;ORAROOTAGENT CORE DUMPED AT NETWORKHAMAINTHREAD;;READROUTEDATA
11782423 - 11202_GIBTWO; OHASD.BIN TAKES CPU ABOUT 95% ~ 100%
11654726 - SCAN LISTENER STARTUP FAILS IF -VAR-OPT-ORACLE-LISTENER.ORA EXISTS.
9978765 - AIX-11202-UD;ROOTUPGRADE.SH HANG AND CRSD CRASHED ON OTHER NODES,10205->11202
10398810 - DOUBLE FREE IN SETUPWORK DUE TO TIMING
11904778 - LNX64-OEL6-11202; CRS STACK CAN'T BE START AFTER RESTART
10397652 - AIX-11202-GIPC;DISABLE SWITCH PORT FOR ONE PRIVATE NIC,HAIP DID NOT FAILOVER
9915329 - SOL-SP-CMP;ORA-600 [603] IN DB AND ORA-603 IN ASM AFTER DOWN INTER-CONNECT NIC
10107380 - SOL-X64-11202-CRF; IPD NOT STARTED DUE TO SCRFOSM_GET_IDS FAILED
10110969 - AIX-11202-CRS; PORTABILITY ISSUES IN FUNCTION TOLOWER_HOST
10305361 - 11202-OCE;CRF NOT RECOGNIZING VERITAS VXFS
10331452 - SOL-11202-UD; 10205->11202 NETWORK RES USR_ORA_IF VALUE MISSED AFTER UPGRADE
10083009 - GIPCD FAILS TO RETRIEVE INFORMATION FROM PEERS DUE TO INVALID ENDPOINT
10631693 - TB;X;CLSSNMHANDLEVFDISCOVERACK; NO PENDINGCONFIGURATION TO COMPLETE. CSS ABORT
10008467 - 112020PL ; HAS ; LRGCVU1 ; FAILS DUE TO WRONG VERSION OF PERL USED;
10048027 - AIX; 10205_SI->11202_SIHA; ASM UPGRADE FAILS
10040109 - PMON KILL LEAD TO OS REBOOT
9944978 - TB-CSS; FALSE CSS EVICTION AFTER PRIVATE NIC RESUME
10370797 - START OF 'ORA.CLUSTER_INTERCONNECT.HAIP' FAILED DURING UPGRADE TO 11.2.0.2
10033106 - SOL-X64-11202-AD ADDNODE.SH SHOULD INDICATE WHAT HAPPENS WHEN ERROR OCCURRING
12700217 - 11202_GIB3; CRSD AGENT CORE DUMP AT CLSN_AGENT;;CONNECTIONPOOL;;ABORTCONNECTIONS
11840629 - KERNEL CRASH DUMP AND REBOOT FAIL INSIDE SOLARIS CONTAINER
10042143 - ORECORE11 LWSFDSEV CAUSED SEGV IN SRVM NATIVE METHODS
9978195 - BC; STOP DB ACTION TIMED OUT AND AGENT EXITS DUE TO FAILURE TO STOP EVENT BRIDGE
10284693 - GIPC; AIX EPIPE FAILURE
12639016 - CRF SUPPORT NEEDS TO BE DIABLED IN ZLINUX HAS
10638381 - 11202-OCE-SYMANTEC; HAIP FAIL TO START WHEN PRIVATE IP IS PLUMBED ON VIRTUAL NIC
11839004 - CRS-2799; FAILED TO SHUT DOWN RESOURCE 'ORA.DRIVERS.ACFS' ON 'SHESBDB1'
9679401 - HPI-CVU-11202; OUI PREREQ CHECKS FAILED FOR WRONG OWNSHIP OF RESOLV.CONF_`HOST`
11663339 - DBMV2;SHARED PROCESS SPINNING CAUSES DELAY IN PRIMARY MEMBER CLEANUP
10075643 - DBMV2-BIGBH;; (UPGRADE 11.2.0.2); UNABLE TO CONTINUE CONFIG.SH FOR CRS UPGRADE
10057719 - LNX64-11202-RAC1;DB INSTANCE KEEPS RESTART AFTER DIRTY RESET OMOTION SOURCE NODE
11834289 - OHASD FAILED TO START TIMELY
9458055 - CONNECTIONS FAIL WITH ORA-12537
10205290 - LNX64-11203-GNS; DBCA FAILED WITH ERROR ORA-00132
10124517 - [11202-SSPARC64-904.911]CRS STACK DOES NOT START AUTOMATICALLY AFTER NODE REBOOT
12680491 - STOP DEPENDENCY BETWEEN NETWORK AND VIP MUST HAVE INTERMEDIATE MODIFYER
13334158 - REBOOT OF ONE OF THE SWITCH EVICTS INSTANCES
11069614 - RDBMS INSTANCE CRASH DUE TO SLOW REAP OF GIPC MESSAGES ON CMT SYSTEMS
10165314 - CHM-CRF-IPDOS REPOSITORY EXCEEDS 1GB AFTER ADD-REMOVE NODE OR FRESH INSTALL
9593552 - GIPCCONNECT() IS NOT ASYNC 11.2.0.2GIBTWO
10168006 - ORAAGENT PROCESS MEMORY GROWTH PERIODICALLY.
13255295 - ACFS FILE SYSTEMS MAY GO OFFLINE ON AIX
11846686 - ACFSROOT FAILS ON ORACLELINUX-RELEASE-5-6.0.1 RUNNUNG A 2.6.18 KERNEL
9867867 - SUSE10-LNX64-11202;NODE REBOOT HANG WHILE ORACLE_HOME LOCATED ON ACFS
12645334 - SOL-X64-SC-ACFS;HIT ASSERTION FAILURE; FALSE ON ORACLEACFS;PROCESSLOGFILE
10228079 - MOUTING DG ORA-15196 [KFC.C;25316] [ENDIAN_KFBH] AFTER NODE REBOOT
10015603 - TB_ACFS_NT64;KERNEL PANIC IN OKS DRIVER WHEN SHUTDOWING CRS STACK
10241696 - TB_SOL_SP_ACFS;FAILED TO MOUNT ACFS FS TO DIRECTORY CREATED ON ANOTHER ACFS FS
9942881 - TIGHTEN UP KILL SEMANTICS FOR 'CLEAN' ACTION.
10252497 - ADVM-ACFS FAILS TO INSTALL ON SLES10
10283058 - ACFS NEEDS AN OPTION TO DISALLOW THE MOUNTING OF FILE SYSTEMS ON RESOURCE START
12724761 - ACFS WILL NOT INSTALL ON AIX 7.1
13045518 - GBM SCANNING CAUSING PERFORMANCE PROBLEMS
10157625 - 11.2.0.2 GI BUNDLE 1 USM TRACKING BUG
10283167 - ASM INSTANCE CANNOT STARTUP DUE TO EXISTENCE OF VMBX PROCESS
9906432 - TB_ACFS_LNX; KERNEL PANIC WHILE DISMOUNT ACFS DG FORCE
10216878 - 11202_GI_ACFS_REPL;REPLI-RELATED RESOURCE FAILED TO FAILOVER WHEN DG DISMOUNTED
10045316 - 11202_AIX; RAC DB INSTALL ON SHARED ACFS HANGS AT LINKING PHASE
10425675 - 11.2.0.2 GI BUNDLE 2 USM TRACKING BUG
10061534 - TB_SOL_SP;DB INSTANCE TERMINATED DUE TO ORA-445 WHEN START INSTANCE ON ALL NODE
11789566 - ACFS RECOVERY PHASE 2
12932852 - AIX VNOPS, ETC USE ENOTSUP WHERE ENOSYS IS APPROPRIATE
10283549 - FIX AIX PANIC AND REMOVE -DAIX_PERF
12700050 - 11203_ACFS_AIX; ACFS DISMOUNT HANG WHILE DOING DISMOUNT ON ALL NODES
12732899 - ACFS CORRUPTION WHEN A FILESYSTEM IS OVER 16T IN SIZE
10311856 - TB_X64_ACFS_REPL;APPLY ASSERTION FAILURE; PBOARDENTRY-USRGBOARDRECENTRY_RECORD
10150020 - LX64; LINUX HANGS IN ADVM MIRROR RECOVERY, AFTER ASM EVICTIONS
12433819 - SOL_SP64; ACCESS ACFS HUNG AFTER ASM INSTANCE CRASH ON OTHER NODES
12421420 - 11.2.0.2 GI BUNDLE 3 USM TRACKING BUG
13146653 - ACFS FILE SYSTEM FIXER DROPS CORE AND EXITS
12681864 - SOL-X64-SC-ACFS; ASSERTION;!(OFS_TEST_FCBSTATES(PFCB,OFS_FCB_DISK_UPDATE_NEEDED)
12378675 - AIX-11203-HA-ACFS; HIT INVALID ASM BLOCK HEADER WHEN CONFIGURE DG USING AIX LVS
10113899 - AIX KSPRINTTOBUFFER TIMESTAMPS NEEDS TIME SINCE BOOT AND WALL_CLOCK TIMES
13019958 - ACFS FILESYSTEM MOUNTS BECOME OFFLINE FREQUENTLY
12614853 - SOL-SP-11203; ORACLEADVM DRIVER FAILED TO ATTACH AND ROOT.SH ABORT
12694821 - ACFS HANG ACROSS CLUSTER
10069698 - TB_ACFS_ENCR; THE EXISTING FILE COULD CORRUPT IF INPUT INCORRECT PKCS PASSOWRD
9861790 - LX64; ADVM DRIVERS HANGING OS DURING ACFS START ATTEMPTS
13396487 - 11.2.0.2 GI PSU5 USM TRACKING BUG
10087118 - UNMOUNT PANICS IF ANOTHER USER IS SITTING IN A SNAPSHOT ROOT DIRECTORY
10056808 - TB_X64_ACFS_REPL;MOUNT ACFS FS FAILED WHEN FS IS FULL
12433511 - SOL-X64-SC-ACFS;ACFS RELATED OPERATION HANG ON ALL CLUSTER NODES
10146744 - ACFS;ORA.REGISTRY.ACFS BECOME UNKOWN AND ACFS FS DISMOUNT
10326548 - SOLX64-VC-GIB1; WRITE-PROTETED ACFS FILES SHOULD NOT BE DELETED BY NON-ROOT USER
10019796 - TB_ACFSSEC; FAIL TO GET ENCRYPTION STATUS OF FILES UNTIL DOING ENCR OP FIRST
9975343 - TB_ACFSSEC; FAIL TO PREPARE SECURITY IF SET ENCRYPTION FIRST ON THE OTHER NODE
9936659 - LNX64-11202-CRS; ORACLE HOME PUT ON ACFS, DB INST FAILS TO RESTART AFTER CRASH
10244210 - TB-SOL-CON; FAIL TO INSTALL ADVM-ACFS ON SOLARIS CONTAINER
10029794 - TB_ACFS_SEC; THE DIR CAN'T READ EVEN IF THE DIR IS NOT IN ANY REALM
12545774 - SOL-X64-SC-ACFS;LS HANG ON REMOTE NODE WHEN CREATE LOTS OF FILES ON LOCAL NODE
10266447 - ROOTUPGRADE.SH FAILS; 'FATAL; MODULE ORACLEOKS NOT FOUND' , ACFS-9121, ACFS-9310
10193581 - [11202-AIX-101006]NLS;ROOT.SH CRS-2674; START OF 'ORA.REGISTRY.ACFS' FAIL
12318560 - ALLOW IOS TO RESTART WHEN WRITE ERROR MESG RETURNS SUCCESS
11804097 - GBM LOCK TAKEN WHEN DETERMINING WHETHER THE FILE SYSTEM IS MOUNTED AND ONLINE
10070563 - MULTIPLE WRITES TO THE SAME BLOCK WITH REPLICATION ON CAN GO OUT OF ORDER
11058691 - LNX64-11203-ACFS;ACFS CAN BE MOUNTED BUT CAN'T BE ACCESSED AFTER LONG RUNNING
10268642 - SOLX64-VC-BUNDLE;NODE PANIC FOR BAD TRAP IN 'ORACLEADVM' FOR NULL POINTER
12862020 - 11.2.0.2 GI PSU4 USM TRACKING BUG
12747467 - CHMOD CMD TO LOST+FOUND DIR IN ACFS FAILS - SIMILAR TO BUG 12545060
10283596 - ACFS;KERNEL PANIC DURING USM LABEL PATCHING - ON AIX
12594736 - LNX64; NODE ASSERT AT OFS_DLM_CHECK_HASHTABLE_DEBUG WHEN UMOUNT ACFS
12591990 - ALLOW CHOWN OF LOST+FOUND ON SOLARIS, WINDOWS, AND AIX
10089120 - 11202-NT_X64; WRONG PROMPT MESSAGE BY DEINSTALL COMMAND WHILE DELETING CRS HOME
9864003 - TB-CSS; NODE REBOOT DUE TO 'ORA.GNS' FAILED TO BE FENCED OFF DURING CRSD CLEANUP
13635562 - TOO MAY CORE FILES GENERATED BY OLOGGERD AFTER JAN 2012 PSU
9876201 - HPI-CRS-11202; OHASD AGENT CORE DUMP AT EONSHTTP.C;162
10007185 - LNX64-11202-CRS; GNS DUMPS CORE IN CLSKGOPANIC AT CLSKPDVA 717
10038791 - HAS SRG SRV GETTING MANY DIFS FOR AIX ON LABEL 100810 AND LATER
10052721 - SOL-SP-11202; 11201- 11202 NON-ROLLING,CRSCTL.BIN CORE AT CLSSNSQANUM, SIGNAL 11
10045436 - TB-CSS; 'ORA.LISTENER.LSNR' FAILED TO BE FENCED OFF DURING CRSD CLEANUP
10072474 - LNX64-11202-CRF;A NODE IS NOT MONITORED AFTER STOP AND START THE ORA.CRF ON IT
10029900 - 11202-NT_X64; CVU PRE NODEADD CHECK VD ERROR
10016083 - SOL-SP-MSG; 'OCRCONFIG -ADD' NEEDS HELPFUL MESSAGE FOR ERROR ORA-15221
9918485 - LNX64-11202-DIT; EMCONFIG FAIL WITH NULLPOINTEREXCEPTION AT RACTRANSFERCORE.JAVA
10040647 - LNX64-112022-UD; AQ AND RLB DO NOT WORK AFTER UPGRADING FROM 11201
10069541 - LNX64-112020-CRF;IPD SPLIT BRAIN AFTER STOPPING ORA.CRF ON MASTER NODE
10029119 - 11202_WINDOWS.X64_100805; 11201-11202 CRS UPGRADE OUI ASKS TO RUN ROOTUPGRADE.SH
9812956 - TB-GIPC; STATUS OF CRSD AND EVMD GOES INTERMEDIATE FOR EVER WHEN KILL GIPC
10036193 - HPI-SG-11202; STANDBY NIC DOESN'T WORK IF DOWN PUBLIC NIC
10015210 - SUSE11-LNX64-11202;OCTSSD LEAK MEMORY 1.7M HR ON PE MASTER DURING 23 HOURS RUNNI
10057680 - HPI-SG-11202 OHASD ORAROOTAGENT.BIN SPIN CPU AFTER SIMULATE ASM DISK ERROR
10078086 - SOL-X64-11202-UD;ROOTUPGRADE.SH FAIL FOR 'CRSCTL STARTUPGRADE' FAIL,10205- 11202
10178670 - SR #3-2174629171; ACFS VOLUMES ARE NOT MOUNTING ONCE RESTARTED THE SERVER
(5) Appendix A: Manual Steps for Apply/Rollback Patch
-------------------------------------------------------
Steps for Applying the Patch
-----------------------------
Execute the following on each node of the cluster in non-shared GI and DB home environment to apply the patch.
1. Stop the GI managed resources running from DB homes.
As the database home owner execute:
% <ORACLE_HOME>/bin/srvctl stop home -o <ORACLE_HOME> -s <status file location> -n <node name>
2. Run the pre root script.
As the root user execute:
# <GI_HOME>/crs/install/rootcrs.pl -unlock
3. Apply the patch to GI Home :
As the GI home owner execute:
% <GI_HOME>/OPatch/opatch napply -oh <GI_HOME> -local <UNZIPPED_PATH_LOCATION>/13635562
4. Run the pre script for DB component of the patch.
As the database home owner execute.
% <UNZIPPED_PATCH_LOCATION>/13635562/custom/server/13635562/custom/scripts/prepatch.sh -dbhome <ORACLE_HOME>
5. Apply the patch to DB Home :
As the database home owner execute:
% <ORACLE_HOME>/OPatch/opatch napply -oh <ORACLE_HOME> -local <UNZIPPED_PATCH_LOCATION>/13635562/custom/server/13635562
6. Run the post script for DB component of the patch.
As the database home owner execute:
% <UNZIPPED_PATCH_LOCATION>/13635562/custom/server/13635562/custom/scripts/postpatch.sh -dbhome <ORACLE_HOME>
7. Run the post script.
As the root user execute:
# <GI_HOME>/rdbms/install/rootadd_rdbms.sh
# <GI_HOME>/crs/install/rootcrs.pl -patch
8. Start the GI managed resources that were earlier running from DB homes.
As the database home owner execute:
% <ORACLE_HOME>/bin/srvctl start home -o <ORACLE_HOME> -s <status file location> -n <node name>
Steps for Rolling Back the Patch
----------------------------------
Execute the following on each node of the cluster in non-shared GI and DB home environment to rollback the patch.
1. Stop the GI managed resources running from DB homes.
As the database home owner execute:
% <ORACLE_HOME>/bin/srvctl stop home -o <ORACLE_HOME> -s <status file location> -n <node name>
2. Run the pre root script.
As the root user execute:
# <GI_HOME>/crs/install/rootcrs.pl -unlock
3. Roll back the patch from GI Home :
As the GI home owner execute:
% <GI_HOME>/OPatch/opatch rollback -local -id 13635562 -oh <GI_HOME>
4. Run the pre script for DB component of the patch.
As the database home owner execute:
% <UNZIPPED_PATCH_LOCATION>/13635562/custom/server/13635562/custom/scripts/prepatch.sh -dbhome <ORACLE_HOME>
5. Roll back the patch from the database home.
As the database home owner execute:
% <ORACLE_HOME>/OPatch/opatch rollback -local -id 13635562 -oh <ORACLE_HOME>
6. Run the post script for DB component of the patch.
As the database home owner execute:
% <UNZIPPED_PATCH_LOCATION>/13635562/custom/server/13635562/custom/scripts/postpatch.sh -dbhome <ORACLE_HOME>
7. Run the post script.
As the root user execute:
# <GI_HOME>/rdbms/install/rootadd_rdbms.sh
# <GI_HOME>/crs/install/rootcrs.pl -patch
8. Start the GI managed resources that were earlier running from DB homes.
As the database home owner execute:
% <ORACLE_HOME>/bin/srvctl start home -o <ORACLE_HOME> -s <status file location> -n <node name>
(6) Documentation Accessibility
--------------------------------
Our goal is to make Oracle products, services, and supporting documentation accessible to all users, including users that are disabled. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/.
Accessibility of Code Examples in Documentation
Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.
Accessibility of Links to External Web Sites in Documentation
This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.
Access to Oracle Support
Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/support/contact.html or visit http://www.oracle.com/accessibility/support.html if you are hearing impaired.
-------------------------------------------------------------------------
Bug 13635562 - TOO MAY CORE FILES GENERATED BY OLOGGERD AFTER JAN 2012 PSU
Copyright 2006, 2011, 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 software or related documentation 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 USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
This software 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 which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
This software 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.
-------------------------------------------------------------------------