Patch 9952245 - 10.2.0.5.2 for CRS Patch Set Update
Date: January 18, 2011
This document is accurate at the time of release. For any changes and additional information regarding PSU 10.2.0.5.2 for CRS, 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 405820.1 10.2.0.X CRS Bundle Patch Information
This document includes the following sections:
PSU 10.2.0.5.2 for CRS contains the bug fixes listed in Section 5, "Bugs Fixed by This Patch".
This section includes the following sections:
For a list of platforms that are supported in this Patch Set Update, see My Oracle Support Note 1263374.1 Patch Set Update and Critical Patch Update Jaunary 2011 Availability Document.
You must use the OPatch 10.2 version 10.2.0.4.7 or later to apply this patch. Oracle recommends that you use the latest released OPatch 10.2, which is available for download from My Oracle Support patch 6880880 by selecting the 10.2.0.0.0 release.
For information about OPatch documentation, including any known issues, see My Oracle Support Note 293369.1 OPatch documentation list.
Your system configuration (Oracle Server version and patch level, and operating system version) must exactly match those in the bug database entry. Any one-off patches that were installed before applying PSU 10.2.0.5.2 for CRS will need to be removed; otherwise, they will be superseded by this patch.
If you do not meet these requirements, or if you are uncertain whether you meet these requirements, submit a Service Request (also called an iTAR or Technical Assistance Request) so that an Oracle Support analyst may review your situation, to help determine if this patch is suitable for you to apply to your system. Oracle recommends that you not apply any temporary patch unless directed by an Oracle Support analyst who has reviewed your system and determined that it is applicable.
This patch can be applied to the CRS Home and the associated RAC RDBMS homes in either of the following ways:
Automatic patching: Apply the patch in an automated manner using the opatch auto command. Automatic patching streamlines patching for both Clusterware and RAC homes, minimizes the number of steps you need to execute, and provides rollback capabilities if you need them. Section 2.4.2, "Automatic Patch Installation" describes the instructions for automatic patching.
Manual patching: Apply the patch in a manual fashion that involves more steps. Section 2.4.4, "Manual Patch Installation" describes the instructions for manual patching.
Regardless of whether you choose automatic patching or manual patching, first read Section 2.4.1, "Patch Pre-Installation Instructions". Then, go to whichever of the following sections are relevant for you:
Before you install PSU 10.2.0.5.2 for CRS, perform the following actions to check the environment and to detect and resolve any one-off patch conflicts.
Ensure that the $PATH definition includes the directory containing the opatch script.
To check the location of this directory, use the following command:
which opatch
For manual patching, ensure that the following environment variables are correctly defined:
CRS_HOME = the full path to the CRS home
RDBMS_HOME = the full path to the Oracle Database server home
If the owners of these homes are different, ensure that you perform the installation steps as the correct owner in the correct environment.
For manual patching, ensure that all instances running under the ORACLE_HOME being patched are cleanly shut down before installing this patch, and ensure that the tool used to terminate the instance or instances has exited cleanly. (For automatic patching, the CRS stack must be up and running.)
If the CRS home is shared, plan for a full cluster outage. The patch will update the shared copy of the binaries, and no daemons can be online while the binaries are modified.
If the CRS home is not shared (that is, if each node of the cluster has its own CRS home), apply the patch as a rolling upgrade. Perform all the installation steps for each node, and do not patch two or more nodes at the same time.
With automatic patching, the opatch auto command stops all the dependent databases and all CRS resources before applying the patch, stops the CRS stack, applies the patch to the CRS home and all applicable RDBMS homes, and starts up the CRS stack and the CRS resources and databases that were stopped earlier. Automatic patching replaces all the manual steps that were needed in previous releases for the application of the CRS bundle patch.
To install the patch using automatic patching, follow these steps:
Verify that the Oracle Inventory is properly configured by entering the following commands:
As the Oracle Clusterware (CRS) software owner:
% opatch lsinventory -detail -oh <CRS_HOME>
As the RDBMS (Oracle Database) server owner:
% opatch lsinventory -detail -oh <RDBMS_HOME>
These commands should list the components for the list of nodes. If the Oracle inventory is not set up correctly, one or both of these commands will fail.
Unzip the PSE container file:
% unzip 9952245.zip
Apply the patch to the CRS Home and all applicable RDBMS homes by entering the following command as the root user:
% opatch auto <top-level directory where 9952245 exists>
If the CRS home is shared, enter this command on any one node only. If the CRS home is not shared, enter this command on all cluster nodes serially.
When you are prompted to enter the OCM (Oracle Configuration Manager) response file path, if the OCM response file is already created in your environment, enter the absolute file path of the OCM response file. Otherwise, you can create the OCM response file with the following command:
<CRS_HOME>/Opatch/ocm/bin/emocmrsp
Note the following additional command options for opatch auto:
To apply the patch to a selective list of Oracle homes:
% opatch auto <top-level directory of unzipped patch> -oh <oraclehome1_path, oraclehome2_path, ...>
To roll back the patch from a selective list of Oracle homes:
% opatch auto -rollback <top-level directory of unzipped patch> -oh <oraclehome1_path, oraclehome2_path, ...>
To apply the patch only to the CRS home (with the CRS stack up):
% opatch auto <top-level directory of unzipped patch> -och <crshome_path>
To roll back the patch only from the CRS home (with the CRS stack up):
% opatch auto -rollback <top-level directory of unzipped patch> -och <crshome_path>
To get help on "opatch auto":
% opatch auto -h
If there are errors, refer to Section 3, "Known Issues".
To roll back the patch from the CRS home and all applicable RDBMS homes, follow these steps:
Verify that the Oracle Inventory is properly configured by entering the following commands:
As the Oracle Clusterware (CRS) software owner:
% opatch lsinventory -detail -oh <CRS_HOME>
As the RDBMS (Oracle Database) server owner:
% opatch lsinventory -detail -oh <RDBMS_HOME>
These commands should list the components for the list of nodes. If the Oracle inventory is not set up correctly, one or both of these commands will fail.
Unzip the PSE container file:
% unzip 9952245.zip
Roll back the patch from the CRS Home and all applicable RDBMS homes by entering the following command as the root user:
% opatch auto rollback <top-level directory of unzipped patch>
If the CRS home is shared, enter this command on any one node only. If the CRS home is not shared, enter this command on all cluster nodes serially.
If there are errors, refer to Section 3, "Known Issues".
To install the patch using manual patching, follow these steps:
Verify that the Oracle Inventory is properly configured by entering the following commands:
As the Oracle Clusterware (CRS) software owner:
% opatch lsinventory -detail -oh <CRS_HOME>
As the RDBMS (Oracle Database) server owner:
% opatch lsinventory -detail -oh <RDBMS_HOME>
These commands should list the components for the list of nodes. If the Oracle inventory is not set up correctly, one or both of these commands will fail.
Unzip the PSE container file:
% cd 9952245 % unzip 9952245.zip
If the CRS home is shared, shut down the RDBMS and ASM instances, listeners, and nodeapps on all nodes before shutting down the CRS daemons on all nodes, as follows:
To shut down the RDBMS instance on all nodes, enter the following command:
% $ORACLE_HOME/bin/srvctl stop database -d <dbname>
To shut down ASM instances, enter the following command on each node:
% $ORACLE_HOME/bin/srvctl stop asm -n <node_name>
To shut down nodeapps, enter the following command on each node:
% $ORACLE_HOME/bin/srvctl stop nodeapps -n <node_name>
To shut down CRS daemons on each node, enter the following command as root:
# $CRS_HOME/bin/crsctl stop crs
If the oprocd is running, then as root stop the oprocd:
% $CRS_HOME/bin/oprocd stop
If the CRS home is not shared, shut down the RDBMS and ASM instances, listeners, nodeapps, and CRS daemons on each local node, as follows:
To shut down the RDBMS instance, enter the following command:
% $ORACLE_HOME/bin/srvctl stop instance -d dbname -i <instance_name>
To shut down ASM instances, enter the following command:
% $ORACLE_HOME/bin/srvctl stop asm -n <node_name>
To shut down nodeapps, enter the following command:
% $ORACLE_HOME/bin/srvctl stop nodeapps -n <node_name>
To shut down CRS daemons, enter the following command as root:
# $CRS_HOME/bin/crsctl stop crs
Run the following script (on only one node if the CRS home is shared, but on each node if the CRS home is not shared) as root to unlock protected files:
# custom/scripts/prerootpatch.sh -crshome <CRS_HOME> -crsuser <username>
where <username> is the software installer/owner for the CRS home.
Run the following script (on only one node if the CRS home is shared, but on each node if the CRS home is not shared) as the CRS software installer/owner to save important configuration settings:
% custom/scripts/prepatch.sh -crshome <CRS_HOME>
Note: The RDBMS portion can only be applied to an RDBMS home that has been upgraded to 10.2.0.5.0.
Also, If the CRS Version and RDBMS version are the same at patch set level, enter the following command as the RDBMS software owner:
% custom/server/9952245/custom/scripts/prepatch.sh -dbhome <RDBMS_HOME>
Enter the following command from the top-level directory where 9952245 exists (on only one node if the CRS home is shared, but on each node if the CRS home is not shared) to patch the CRS home files:
% opatch napply -local -oh <CRS_HOME> -id 9952245
Note: This step can be applied only to an RDBMS home that has been upgraded to 10.2.0.5.0. For more information, see My Oracle Support Note 363254.1 Applying one-off Oracle Clusterware patches in a mixed version home environment.
Enter the following command from within the 9952245 directory (on only one node if the CRS home is shared, but on each node if the CRS home is not shared) to patch the RDBMS home files:
% opatch napply custom/server/ -local -oh <RDBMS_HOME> -id 9952245
If there are multiple Oracle Database (RDBMS) homes in your configuration, then apply the patch to each home before continuing.
|
Note: If you later install an additional Oracle Database (RDBMS) home, or if you skip an Oracle Database home, then applying the patch to additional homes is easier, and it can be done while CRS is active:
|
Configure the CRS home, because after the opatch command finishes, some configuration settings need to be applied to the patched files. As the Oracle Clusterware (CRS) software owner, enter the following command (on only one node if the CRS home is shared, but on each node if the CRS home is not shared):
% custom/scripts/postpatch.sh -crshome <CRS_HOME>
Note: This step can be applied only to an RDBMS home that has been upgraded to 10.2.0.5.0. For more information, see My Oracle Support Note 363254.1 Applying one-off Oracle Clusterware patches in a mixed version home environment.
Configure the RDBMS home, because after the opatch command finishes, some configuration settings need to be applied to the patched files. As the Oracle Database software owner, enter the following command (on only one node if the CRS home is shared, but on each node if the CRS home is not shared):
% custom/server/9952245/custom/scripts/postpatch.sh -dbhome <RDBMS_HOME>
Restore security settings to the CRS home using CRS software owner and restart the CRS daemons by running the following script (on all nodes) as root:
% custom/scripts/postrootpatch.sh -crshome <CRS_HOME>
If the CRS home is shared, run this script on each node, one node at a time. Do not run this script in parallel on two or more nodes.
Do not run this script in any other context than as part of the patching process.
You can determine whether the patch has been successfully installed by entering the following commands:
As the Oracle Clusterware (CRS) software owner:
% opatch lsinventory -detail -oh <CRS_HOME>
As the RDBMS (Oracle Database) server owner:
% opatch lsinventory -detail -oh <RDBMS_HOME>
These commands should list the components for the list of nodes.
If there are errors, refer to Section 3, "Known Issues".
To roll back the patch, follow these steps:
Verify that the Oracle Inventory is properly configured by entering the following commands:
As the Oracle Clusterware (CRS) software owner:
% opatch lsinventory -detail -oh <CRS_HOME>
As the RDBMS (Oracle Database) server owner:
% opatch lsinventory -detail -oh <RDBMS_HOME>
These commands should list the components for the list of nodes. If the Oracle inventory is not set up correctly, one or both of these commands will fail.
Unzip the PSE container file:
% cd 9952245 % unzip 9952245.zip
If the CRS home is shared, shut down the RDBMS and ASM instances, listeners, and nodeapps on all nodes before shutting down the CRS daemons on all nodes, as follows:
To shut down the RDBMS instance on all nodes, enter the following command:
% $ORACLE_HOME/bin/srvctl stop database -d <dbname>
To shut down ASM instances, enter the following command on each node:
% $ORACLE_HOME/bin/srvctl stop asm -n <node_name>
To shut down nodeapps, enter the following command on each node:
% $ORACLE_HOME/bin/srvctl stop nodeapps -n <node_name>
To shut down CRS daemons on each node, enter the following command as root:
# $CRS_HOME/bin/crsctl stop crs
If the oprocd is running, then as root stop the oprocd:
# $CRS_HOME/bin/oprocd stop
If the CRS home is not shared, shut down the RDBMS and ASM instances, listeners, nodeapps, and CRS daemons on each local node, as follows:
To shut down the RDBMS instance, enter the following command:
% $ORACLE_HOME/bin/srvctl stop instance -d dbname -i <instance_name>
To shut down ASM instances, enter the following command:
% $ORACLE_HOME/bin/srvctl stop asm -n <node_name>
To shut down nodeapps, enter the following command:
% $ORACLE_HOME/bin/srvctl stop nodeapps -n <node_name>
To shut down CRS daemons, enter the following command as root:
# $CRS_HOME/bin/crsctl stop crs
Run the following script (on only one node if the CRS home is shared, but on each node if the CRS home is not shared) as root to unlock protected files:
custom/scripts/prerootpatch.sh -crshome <CRS_HOME> -crsuser <username>
where <username> is the software installer/owner for the CRS home.
Run the following script (on only one node if the CRS home is shared, but on each node if the CRS home is not shared) as the CRS software installer/owner to save important configuration settings:
% custom/scripts/prepatch.sh -crshome <CRS_HOME>
Note: The RDBMS portion can only be applied to an RDBMS home that has been upgraded to 10.2.0.5.2.
Also, If the CRS Version and RDBMS version are the same, enter the following command as the RDBMS software owner:
% custom/server/9952245/custom/scripts/prepatch.sh -dbhome <RDBMS_HOME>
Enter the following commands (on only one node if the CRS home is shared, but on each node if the CRS home is not shared) to roll back the patch on all homes:
% opatch rollback -id 9952245 -local -oh <CRS_HOME> % opatch rollback -id 9952245 -local -oh <RDBMS_HOME>
Configure the CRS home, because after the opatch command finishes, some configuration settings need to be applied to the patched files. As the Oracle Clusterware (CRS) software owner, enter the following command (on only one node if the CRS home is shared, but on each node if the CRS home is not shared):
% custom/scripts/postpatch.sh -crshome <CRS_HOME>
Note: This step can be applied only to an RDBMS home that has been upgraded to 10.2.0.5.2. For more information, see My Oracle Support Note 363254.1 Applying one-off Oracle Clusterware patches in a mixed version home environment.
Configure the RDBMS home, because after the opatch command finishes, some configuration settings need to be applied to the patched files. As the Oracle Database software owner, enter the following command (on only one node if the RDBMS home is shared, but on each node if the CRS home is not shared):
% custom/server/9952245/custom/scripts/postpatch.sh -dbhome <RDBMS_HOME>
Restore security settings to the CRS home and restart the CRS daemons by running the following script (on all nodes) as root:
% custom/scripts/postrootpatch.sh -crshome <CRS_HOME>
If the CRS home is shared, run this script on each node, one node at a time. Do not run this script in parallel on two or more nodes.
Do not run this script in any other context than as part of the patching process.
You can determine whether the patch has been successfully rolled back by entering the following commands:
As the Oracle Clusterware (CRS) software owner:
% opatch lsinventory -detail -oh <CRS_HOME>
As the RDBMS (Oracle Database) server owner:
% opatch lsinventory -detail -oh <RDBMS_HOME>
These commands should list the components for the list of nodes.
If there are errors, refer to Section 3, "Known Issues".
For information about OPatch issues, see My Oracle Support Note 293369.1 OPatch documentation list.
For issues documented after the release of this PSU, see My Oracle Support Note 405820.1 10.2.0.X CRS Bundle Patch Information.
Other known issues are as follows.
For patch updates on Solaris clusters, the UDLM must have been be upgraded to have the appropriate version of libskgxn2, to avoid node reboots. To determine whether the correct version of libskgxn2.so is installed, enter the following command:
/usr/bin/pkginfo -l ORCLudlm
The output of this command includes a VERSION line, for example:
VERSION: Dev Release 03/09/06, 64bit 3.3.4.9 reentrant, async
libskgxn2.so version 1 with bug 6404642 fix
If libskgxn2.so is not at version 1 in the UDLM package, the UDLM must be upgraded.
On AIX systems, if you see any errors about files being locked or OPatch being unable to copy files, then this might be caused by a process that needs to be terminated or by an additional file that needs to be unloaded from the system cache.To identify the likely cause, execute the following commands (specifying either the full or partial <CRS_HOME> path):
genld -l | grep <CRS_HOME> genkld | grep <CRS_HOME>
Provide the output of these commands to your Oracle Support representative, who will be able to identify the corrective steps.
If the genld command returns data, then a currently executing process has something open in the <CRS_HOME> directory; you should terminate the process as required or recommended.
If the genkld command returns data, then remove the entries from the operating system cache by running the slibclean command as root:
slibclean
With automatic patching, when opatch auto is used with the -oh option to apply or roll back the patch only on the CRS home, the command succeeds, but it displays the following ignorable error after the execution of postrootpatch.sh:
verify failure: exit code 256 for srvctl_config_p Action failed, do you want to retry it? (y/n/abort/N/N1-N2/help):
Enter n and let the process complete.
With automatic patching, when the Clusterware stack is down, you can patch the Clusterware home only with the -och option. The RDBMS homes cannot be patched automatically when the Clusterware stack is down. After the Clusterware home is patched, you can use the -oh option to patch the RDBMS homes.
With automatic patching, if the patch is not installed on all the nodes at same location, the following ignorable error message is displayed:
verify failure: exit code 32512 for cat Action failed, do you want to retry it? (y/n/abort/N/N1-N2/help):
Enter n and let the process complete.
With automatic patching, if some of the cluster nodes are down, the following ignorable error message is displayed:
verify failure: exit code 65280 for cat Action failed, do you want to retry it? (y/n/abort/N/N1-N2/help):
Enter n and let the process complete.
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 10248542.8 Bug 10248542 - 10.2.0.5.2 Patch Set Update (PSU)
This patch includes the following bug fixes.
CSS
8487143 - ASM FAILED TO OPEN - [KFGFINALIZE_2]
8996060 - THE FAILOVER OF VIP FAILED WHILE PUBLIC NETWORK CABLE WAS PULLED OUT
9577921 - AFTER DOWN INTERCONNECT, ALL THE NODES REBOOTED
9610672 - CSS COREDUMP AT CLSSNMCLUSTERLISTENER WHEN UPGRADE TO 10205
9646836 - CALCULATION OF THE MISSTIME TO ADDRESS LRG 4618412
9872299 - CRSSETUP.ADD.BAT FAILED WHEN ADD NEW NODE TO CLUSTER
9879181 - ROOTUPGRADE FAIL CSSD ABORT FROM THREAD GMCLIENTLISTENER
PCW
8308495 - RPATH LIBHASGEN11.SO USES NON-EXISTANT LIBRARY DIRECTORIES
9103966 - CLONING FAILS AFTER APPLYING PSU 10.2.0.4.2 FOR CRS
9261837 - PASSWORD LOGGED IN FILES OF CRS HOME AND RAC HOME
OPSM
6899183 - PROC-9 BEING SIGNALLED WHEN USING SRVCTL
RACG
8640576 - ALLOW HAS/SRC/CLSR/SOSD/SCLSRVIP.SH TO USE ETHTOOL AS WELL AS MII-TOOL
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.
Patch 9952245 - 10.2.0.5.2 for CRS Patch Set Update Release %version% for CRS for %osname%
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.