oracle集羣管理 11.2版本升級和回滾【psu,acfs，ocw patch】

第一章節  Manual Steps for Apply/Rollback Patch

Steps for Applying the Patch

 

Note:

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

As the Oracle RAC database home owner execute:

$ <ORACLE_HOME>/bin/emctl stop dbconsole

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

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

    

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

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

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

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

    

   Note:

    You need to make sure that the Oracle ACFS file systems are unmounted (see My Oracle Support document 1494652.1 How to Mount or Unmount ACFS File System While Applying GI Patches?) and all other Oracle processes are shutdown before you proceed.

2. Run the pre root script.

    

   If this is a GI Home, as the root user execute: （不執行打補丁，一些文件無法覆蓋，無權限）

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

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

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

4. Apply the CRS patch using (Generate response file, if needed, using the emocmrsp and specify using -ocmrf option)

    

   As the GI home owner execute:

   $ <GI_HOME>/OPatch/opatch napply -oh <GI_HOME> -local <UNZIPPED_PATCH_LOCATION>/<GI_PSU_number>/<OCW Components_number>
   

   As the GI home owner execute:

   $ <GI_HOME>/OPatch/opatch napply -oh <GI_HOME> -local <UNZIPPED_PATCH_LOCATION>/<GI_PSU_number>/<ACFS Components_number>
   

   As the GI home owner execute:

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

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

    

   As the database home owner execute:

   $ <UNZIPPED_PATCH_LOCATION>/<GI_PSU_number>/<OCW Components_number>/custom/server/<OCW Components_number>/custom/scripts/prepatch.sh -dbhome <ORACLE_HOME>
   

6. Apply the DB patch.

    

   As the database home owner execute (Generate response file, if needed, using the emocmrsp and specify using -ocmrf option):

   $ <ORACLE_HOME>/OPatch/opatch napply -oh <ORACLE_HOME> -local <UNZIPPED_PATCH_LOCATION>/<GI_PSU_number>/<OCW Components_number>/custom/server/<OCW Components_number>
   $ <ORACLE_HOME>/OPatch/opatch apply -oh <ORACLE_HOME> -local <UNZIPPED_PATCH_LOCATION>/<GI_PSU_number>/<DB_PSU_number>
   

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

    

   As the database home owner execute:

   $ <UNZIPPED_PATCH_LOCATION>/<GI_PSU_number>/<OCW Components_number>/custom/server/<OCW Components_number>/custom/scripts/postpatch.sh -dbhome <ORACLE_HOME>
   

8. Run the post script.

    

   As the root user execute:

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

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

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

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

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

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

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

     

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

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

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

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

11. Refer Section 2.5, "Patch Post-Installation Instructions" step after installing the patch

第二章節   Steps for Rolling Back the Patch From a GI Home

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

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

    

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

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

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

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

    

   Note:

    You need to make sure that the Oracle ACFS file systems are unmounted (see My Oracle Support document 1494652.1 How to Mount or Unmount ACFS File System While Applying GI Patches?) and all other Oracle processes are shut down before you proceed.

2. Run the pre root script.

    

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

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

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

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

3. Roll back the CRS patch.

    

   As the GI home owner execute:

   $ <GI_HOME>/OPatch/opatch rollback -local -id <OCW Components_number> -oh <GI_HOME> 
   $ <GI_HOME>/OPatch/opatch rollback -local -id <ACFS Components_number> -oh <GI_HOME> 
   $ <GI_HOME>/OPatch/opatch rollback -local -id <DB_PSU_number> -oh <GI_HOME> 
   

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

    

   As the database home owner execute:

   $ <UNZIPPED_PATCH_LOCATION>/<GI_PSU_number>/<OCW Components_number>/custom/server/<OCW Components_number>/custom/scripts/prepatch.sh -dbhome <ORACLE_HOME>
   

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

    

   As the database home owner execute:

   $ <ORACLE_HOME>/OPatch/opatch rollback -local -id <OCW Components_number> -oh <ORACLE_HOME> 
   $ <ORACLE_HOME>/OPatch/opatch rollback -local -id <DB_PSU_number> -oh <ORACLE_HOME>
   

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

    

   As the database home owner execute:

   $ <UNZIPPED_PATCH_LOCATION>/<GI_PSU_number>/<OCW Components_number>/custom/server/<OCW Components_number>/custom/scripts/postpatch.sh -dbhome <ORACLE_HOME>
   

7. Run the post script.

    

   As the root user execute:

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

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

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

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

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

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

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

    

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

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

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

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

10. Refer Section 2.8, "Patch Post-Deinstallation Instructions for an Oracle RAC Environment" for the post rollback steps

Patching an Oracle RAC Home Installation Manually

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

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

    

   As the database home owner execute:

   $ <UNZIPPED_PATCH_LOCATION>/<GI_PSU_number>/<OCW Components_number>/custom/server/<OCW Components_number>/custom/scripts/prepatch.sh -dbhome <ORACLE_HOME>
   

2. Apply the DB patch.

    

   As the database home owner execute (Generate response file, if needed, using the emocmrsp and specify using -ocmrf option):

   $ <ORACLE_HOME>/OPatch/opatch napply -oh <ORACLE_HOME> -local <UNZIPPED_PATCH_LOCATION>/<GI_PSU_number>/<OCW Components_number>/custom/server/<OCW Components_number>
   $ <ORACLE_HOME>/OPatch/opatch apply -oh <ORACLE_HOME> -local <UNZIPPED_PATCH_LOCATION>/<GI_PSU_number>/<DB_PSU_number>
   

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

    

   As the database home owner execute:

   $ <UNZIPPED_PATCH_LOCATION>/<GI_PSU_number>/<OCW Components_number>/custom/server/<OCW Components_number>/custom/scripts/postpatch.sh -dbhome <ORACLE_HOME>
   

4. Refer Section 2.5, "Patch Post-Installation Instructions" step after installing the patch

Rolling Back the Patch from an Oracle RAC Home Installation Manually

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

    

   As the database home owner execute:

   $ <UNZIPPED_PATCH_LOCATION>/<GI_PSU_number>/<OCW Components_number>/custom/server/<OCW Components_number>/custom/scripts/prepatch.sh -dbhome <ORACLE_HOME>
   

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

    

   As the database home owner execute:

   $ <ORACLE_HOME>/OPatch/opatch rollback -local -id <OCW Components_number> -oh <ORACLE_HOME>
   $ <ORACLE_HOME>/OPatch/opatch rollback -local -id <DB_PSU_number> -oh <ORACLE_HOME>
   

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

    

   As the database home owner execute:

   $ <UNZIPPED_PATCH_LOCATION>/<GI_PSU_number>/<OCW Components_number>/custom/server/<OCW Components_number>/custom/scripts/postpatch.sh -dbhome <ORACLE_HOME>
   

4. Refer Section 2.8, "Patch Post-Deinstallation Instructions for an Oracle RAC Environment" for the post rollback steps

6 Documentation Accessibility

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

Access to Oracle Support

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

---

Oracle Grid Infrastructure 11.2.0.4.x Patch Set Update SUPPLEMENTAL README

Copyright � 2006, 2013, Oracle and/or its affiliates. All rights reserved.

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

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

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

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

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

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

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

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