Skip Headers
Oracle® Database Patch 10248535 - 11.1.0.7.6 for CRS Patch Set Update
 
 

Oracle® Database

Patch 10248535 - 11.1.0.7.6 for CRS Patch Set Update

 

Released: January 18, 2011

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

This document includes the following sections:

1 Patch Information

PSU 11.1.0.7.6 for CRS contains the bug fixes listed in Section 5, "Bugs Fixed by This Patch".

2 Patch Installation and Deinstallation

This section includes the following sections:

2.1 Platforms for PSU 11.1.0.7.6 for CRS

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 January 2011 Availability Document.

2.2 OPatch Utility Information

You must use the OPatch utility version 11.1.0.6.7 or later to apply this patch. Oracle recommends that you use the latest released OPatch 11.1, which is available for download from My Oracle Support patch 6880880 by selecting the 11.1.0.0.0 release.

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

2.3 Additional Requirements

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

2.4 Patch Installation and Deinstallation

This section contains instructions for the following:

2.4.1 Patch Pre-Installation Instructions

Before you install PSU 11.1.0.7.6 for CRS, perform the following actions to check the environment and to detect and resolve any one-off patch conflicts.

2.4.1.1 Environment Checks

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

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

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

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

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

2.4.2 Patch Installation

To install the patch, follow these steps:

  1. Verify that the Oracle Inventory is properly configured by entering the following commands:

    1. As the Oracle Clusterware (CRS) software owner:

      % opatch lsinventory -detail -oh <CRS_HOME>

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

  2. Unzip the PSE container file:

    % unzip p10248535_<sver>_<os>.zip
% cd 10248535

  3. 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:

    1. To shut down the RDBMS instance on all nodes, enter the following command:

      % $ORACLE_HOME/bin/srvctl stop database -d <dbname>

    2. To shut down ASM instances, enter the following command on each node:

      % $ORACLE_HOME/bin/srvctl stop asm -n <node_name>

    3. To shut down listeners, enter the following command on each node:

      % $ORACLE_HOME/bin/srvctl stop listener -n <node_name>

    4. To shut down nodeapps, enter the following command on each node:

      % $ORACLE_HOME/bin/srvctl stop nodeapps -n <node_name>

    5. To shut down CRS daemons on each node, enter the following command as root:

      # crsctl stop crs

  4. 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:

    1. To shut down the RDBMS instance, enter the following command:

      % $ORACLE_HOME/bin/srvctl stop instance -d dbname -i <instance_name>

    2. To shut down ASM instances, enter the following command:

      % $ORACLE_HOME/bin/srvctl stop asm -n <node_name>

    3. To shut down listeners, enter the following command on each node:

      % $ORACLE_HOME/bin/srvctl stop listener -n <node_name>

    4. To shut down nodeapps, enter the following command:

      % $ORACLE_HOME/bin/srvctl stop nodeapps -n <node_name>

    5. To shut down CRS daemons, enter the following command as root:

      # crsctl stop crs

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

  6. 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 11.1.0.7.0.

    Also, If the CRS Version and RDBMS version are the same, enter the following command as the RDBMS software owner:

    % custom/server/10248535/custom/scripts/prepatch.sh -dbhome <RDBMS_HOME>

  7. Enter the following command as the owner of CRS HOME (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 10248535

  8. Note: This step can be applied only to an RDBMS home that has been upgraded to 11.1.0.7.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 as the RDBMS HOME owner (on only one node if the CRS ome is shared, bug on each note if the CRS home is not shared) to patch the RDBMS home files:

    On Linux32 and Linux64 systems only:

    % opatch napply custom/server/ -local -oh <RDBMS_HOME> -id 9952240,7388579

    On all other systems:

    % opatch napply custom/server/ -local -oh <RDBMS_HOME> -id 10248535

    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:

    1. Shut down all instances using that Oracle Database home.

    2. Invoke opatch as described in step 10.

    3. Restart the instances in that Oracle Database home.

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

  10. Note: This step can be applied only to an RDBMS home that has been upgraded to 11.1.0.7.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 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/10248535/custom/scripts/postpatch.sh -dbhome <RDBMS_HOME>

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

  12. You can determine whether the patch has been successfully installed by entering the following commands:

    1. As the Oracle Clusterware (CRS) software owner:

      % opatch lsinventory -detail -oh <CRS_HOME>

    2. As the RDBMS (Oracle Database) server owner:

      % opatch lsinventory -detail -oh <RDBMS_HOME>

    These commands should list the components for the list of nodes.

  13. If there are errors, refer to Section 3, "Known Issues".

2.4.3 Patch Deinstallation

To roll back the patch, follow these steps:

  1. Verify that the Oracle Inventory is properly configured by entering the following commands:

    1. As the Oracle Clusterware (CRS) software owner:

      % opatch lsinventory -detail -oh <CRS_HOME>

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

  2. Unzip the PSE container file:

    % unzip 10248535.zip
% cd 10248535

  3. 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:

    1. To shut down the RDBMS instance on all nodes, enter the following command:

      % $ORACLE_HOME/bin/srvctl stop database -d <dbname>

    2. To shut down ASM instances, enter the following command on each node:

      % $ORACLE_HOME/bin/srvctl stop asm -n <node_name>

    3. To shut down listeners, enter the following command on each node:

      % $ORACLE_HOME/bin/srvctl stop listener -n <node_name>

    4. To shut down nodeapps, enter the following command on each node:

      % $ORACLE_HOME/bin/srvctl stop nodeapps -n <node_name>

    5. To shut down CRS daemons on each node, enter the following command as root:

      # crsctl stop crs

  4. 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:

    1. To shut down the RDBMS instance, enter the following command:

      % $ORACLE_HOME/bin/srvctl stop instance -d dbname -i <instance_name>

    2. To shut down ASM instances, enter the following command:

      % $ORACLE_HOME/bin/srvctl stop asm -n <node_name>

    3. To shut down listeners, enter the following command on each node:

      % $ORACLE_HOME/bin/srvctl stop listener -n <node_name>

    4. To shut down nodeapps, enter the following command:

      % $ORACLE_HOME/bin/srvctl stop nodeapps -n <node_name>

    5. To shut down CRS daemons, enter the following command as root:

      # crsctl stop crs

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

  6. 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 11.1.0.7.0.

    Also, If the CRS Version and RDBMS version are the same, enter the following command as the RDBMS software owner:

    % custom/server/10248535/custom/scripts/prepatch.sh -dbhome <RDBMS_HOME>

  7. Depending on your type of system, enter commands as follows:

    • On Linux32 and Linux64 systems only:

      Enter the following command as the CRS HOME owner (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 10248535 -local -oh <CRS_HOME>

      Enter the following command as the RDBMS HOME owner (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 10248535,7388579 -local -oh <RDBMS_HOME>

    • On all other systems systems:

      Enter the following command as the CRS HOME owner (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 10248535 -local -oh <CRS_HOME>

      Enter the following command as the RDBMS HOME owner (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 10248535 -local -oh <RDBMS_HOME>

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

  9. Note: This step can be applied only to an RDBMS home that has been upgraded to 11.1.0.7.6. 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 RDBMS 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/10248535/custom/scripts/postpatch.sh -dbhome <RDBMS_HOME>

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

  11. You can determine whether the patch has been successfully rolled back by entering the following commands:

    1. As the Oracle Clusterware (CRS) software owner:

      % opatch lsinventory -detail -oh <CRS_HOME>

    2. As the RDBMS (Oracle Database) server owner:

      % opatch lsinventory -detail -oh <RDBMS_HOME>

    These commands should list the components for the list of nodes.

  12. If there are errors, refer to Section 3, "Known Issues".

3 Known Issues

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

For issues for PSUs 11.1.0.7.n, see My Oracle Support Note 810663.1 11.1.0.X CRS Bundle Patch Information.

4 References

The following documents are references for this patch.

Note 293369.1 OPatch documentation list

Note 360870.1 Impact of Java Security Vulnerabilities on Oracle Products

Note 10248535.8 Bug 10248535 - 11.1.0.7.6 Patch Set Update (PSU)

Note 810663.1 11.1.0.X CRS Bundle Patch Information

5 Bugs Fixed by This Patch

This patch includes the following bug fixes.

7308467 - CRS DOES NOT PRESERVE ORACLE PROFILE - RDBMS, ASM, NET FAIL WITH LOW LIMITS

9148531 - CSSD SPLITBRAIN

9371712 - SRVCONFIG DOES NOT UPDATE ORACLE_HOME FOR DB AFTER UPGRADE FROM 10G TO 11G

For more information about bug fixes included in this PSU, see My Oracle Support Note 810663.1 11.1.0.X CRS Bundle Patch Information.

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.

TTY Access to Oracle Support Services

To reach AT&T Customer Assistants, dial 711 or 1.800.855.2880. An AT&T Customer Assistant will relay information between the customer and Oracle Support Services at 1.800.223.1711. Complete instructions for using the AT&T relay services are available at http://www.consumer.att.com/relay/tty/standard2.html. After the AT&T Customer Assistant contacts Oracle Support Services, an Oracle Support Services engineer will handle technical issues and provide customer support according to the Oracle service request process.

Patch 10248535 - 11.1.0.7.6 for CRS Patch Set Update Release 11.1.0.7.6 for CRS

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.

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