Oracle® Database
Patch 26610246 - Oracle Grid Infrastructure Patch Set Update 11.2.0.4.170814 (Jul2017) (Includes Database PSU 11.2.0.4.170814)
Platform: Linux x86-64, Solaris SPARC, Solaris x86-64, IBM AIX, HP-UX Itanium
From CPUJan2016 onwards, the 5th digit of the version number will be changed to reflect the release date in the format YYMMDD. See My Oracle Support Document 2061926.1 for more information.
In this document Oracle Database Home refers to Enterprise Edition or Standard Edition Database software. GI refers to Grid Infrastructure and PSU refers to Patch Set Update.
The GI PSU patch includes updates for both the Clusterware home and Database home that can be applied in a rolling fashion.
This patch is Database Vault installable. Review My Oracle Support Document 1195205.1 for details on how to apply this patch to a Database Vault environment.
This patch is Data Guard Standby First Installable - See My Oracle Support Document 1265700.1 Oracle Patch Assurance - Data Guard Standby-First Patch Apply for details on how to remove risk and reduce downtime when applying this patch.
This document is accurate at the time of release. For any changes and additional information regarding GI PSU 11.2.0.4.170814, see these related documents that are available at My Oracle Support (http://support.oracle.com/):
-
Document 854428.1 Patch Set Updates for Oracle Products
-
Document 2264639.1 Oracle Grid Infrastructure Patch Set Update 11.2.0.4.170718 Known Issues
This document includes the following sections:
1 Patch Information
GI PSUs are cumulative and include the Database PSU and associated CPU program security content.
Table 1 describes installation types and security content. For each installation type, it indicates the most recent patches, which includes new security fixes that are pertinent to that installation type. If there are no security fixes to be applied to an installation type, then "None" is indicated. If a specific patch is listed, then apply that or any later patch to be current with security fixes.
Table 1 Installation Types and Security Content
| Patch 26610246 - Oracle Grid Infrastructure Patch Set Update 11.2.0.4.170814 (Jul2017) (Includes Database PSU 11.2.0.4.170814) Platform: Linux x86-64, Solaris SPARC, Solaris x86-64, IBM AIX, HP-UX Itanium From CPUJan2016 onwards, the 5th digit of the version number will be changed to reflect the release date in the format YYMMDD. See My Oracle Support Document 2061926.1 for more information. In this document Oracle Database Home refers to Enterprise Edition or Standard Edition Database software. GI refers to Grid Infrastructure and PSU refers to Patch Set Update. The GI PSU patch includes updates for both the Clusterware home and Database home that can be applied in a rolling fashion. This patch is Database Vault installable. Review My Oracle Support Document 1195205.1 for details on how to apply this patch to a Database Vault environment. This patch is Data Guard Standby First Installable - See My Oracle Support Document 1265700.1 Oracle Patch Assurance - Data Guard Standby-First Patch Apply for details on how to remove risk and reduce downtime when applying this patch. This document is accurate at the time of release. For any changes and additional information regarding GI PSU 11.2.0.4.170814, see these related documents that are available at My Oracle Support (http://support.oracle.com/):
This document includes the following sections:
1 Patch Information GI PSUs are cumulative and include the Database PSU and associated CPU program security content. Table 1 describes installation types and security content. For each installation type, it indicates the most recent patches, which includes new security fixes that are pertinent to that installation type. If there are no security fixes to be applied to an installation type, then "None" is indicated. If a specific patch is listed, then apply that or any later patch to be current with security fixes. Table 1 Installation Types and Security Content
Table 2 lists the various configurations and the applicable PSU that should be used to patch that configuration. Table 2 Configuration and PSU Mapping
Table 3 lists the various patches by patch number getting installed as part of this GI PSU patch. Table 3 Patch Numbers Getting Installed as Part of this GI PSU Patch
2 Patch Installation and Deinstallation This section includes the following sections:
2.1 Patch Installation Prerequisites You must satisfy the conditions in the following sections before applying the patch:
2.1.1 OPatch Utility Information You must use the OPatch utility version 11.2.0.3.6 or later to apply this patch. Oracle recommends that you use the latest released OPatch version for 11.2 releases, which is available for download from My Oracle Support patch 6880880 by selecting ARU link for the 11.2.0.0.0 release. It is recommended that you download the Opatch utility and the patch in a shared location to be able to access them from any node in the cluster for the patch application on each node. When patching the GI Home, a shared location on ACFS only needs to be unmounted on the node where the GI Home is being patched. The new opatch utility should be updated in all the Oracle RAC database homes and the GI home that are being patched. To update Opatch, use the following instructions:
The version output of the previous command should be 11.2.0.3.6 or later. For information about OPatch documentation, including any known issues, see My Oracle Support Document 293369.1 OPatch documentation list. The OPatch utility will prompt for your OCM (Oracle Configuration Manager) response file when it is run. You should enter a complete path of OCM response file if you already have created this in your environment. OCM response file is required and is not optional. If you do not have the OCM response file (ocm.rsp), see the following My Oracle Support Document 966023.1 How To Create An OCM Response File For Opatch Silent Installation. 2.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. 2.1.4 Download and Unzip the Patch To apply the patch, it must be accessible from all nodes in the Oracle cluster. Download the patch and unzip it to a shared location, this is called the <UNZIPPED_PATCH_LOCATION>. This directory must be empty and not be /tmp. Additionally, the directory should have read permission for the ORA_INSTALL group. $ cd <UNZIPPED_PATCH_LOCATION> Check that the directory is empty. $ ls Unzip the patch as grid home owner. $ unzip p26610246_112040_<platform>.zip 2.1.5 Stop EM Agent Processes Prior to Patching and Prior to Rolling Back the Patch You must stop the EM agent processes running from the database home, prior to patching the Oracle RAC database or GI Home and prior to rolling back the patch from Oracle RAC database or GI Home. Execute the following command on the node to be patched or the node where the patch is to be rolled back. As the Oracle RAC database home owner execute: $ <ORACLE_HOME>/bin/emctl stop dbconsole 2.2 One-off Patch Conflict Detection and Resolution See My Oracle Support Document 1061295.1 Patch Set Updates - One-off Patch Conflict Resolution to determine, for each conflicting patch, whether a conflict resolution patch is already available, and if you need to request a new conflict resolution patch or if the conflict may be ignored. The fastest and easiest way to determine whether you have one-off patches in the Oracle home that conflict with the patch, and to get the necessary conflict resolution patches, is to use the Patch Recommendations and Patch Plans features on the Patches & Updates tab in My Oracle Support. These features work in conjunction with the My Oracle Support Configuration Manager. Recorded training sessions on these features can be found in Document 603505.1. However, if you are not using My Oracle Support Patch Plans, the My Oracle Support Conflict Checker tool enables you to upload an OPatch inventory and check the patches that you want to apply to your environment for conflicts. If no conflicts are found, you can download the patches. If conflicts are found, the tool finds an existing resolution to download. If no resolution is found, it will automatically request a resolution, which you can monitor in the Plans and Patch Requests region of the Patches & Updates tab. For more information, see Knowledge Document 1091294.1, How to use the My Oracle Support Conflict Checker Tool.
The Opatch utility has automated the patch application for the Oracle Grid Infrastructure (GI) home and the Oracle RAC database homes when run with root privileges. It must be executed on each node in the cluster if the GI home or Oracle RAC database home is in non-shared storage. The utility should not be run in parallel on the cluster nodes. For more information about opatch auto, see My Oracle Support Document 1339140.1 FAQ: OPatch/Patch Questions/Issues for Oracle Clusterware (Grid Infrastructure or CRS) and RAC Environments. For detailed patch installation instructions, see Section 2.4, "Patch Installation". The patch instructions will differ based on the configuration of the Grid infrastructure and the Oracle RAC database homes. Patching instructions for Oracle RAC Database Homes and GI together are listed below. The most common configurations are listed as follows:
For other configurations listed below, see My Oracle Support Document 1641136.1:
Patching Oracle RAC Database Homes and GI Together
As root user, execute the following command on each node of the cluster: # opatch auto <UNZIPPED_PATCH_LOCATION>/26610246 -ocmrf <ocm response file>
Patching instructions:
2.5 Patch Post-Installation Instructions After installing the patch, perform the following actions:
2.5.1 Applying Conflict Resolution Patches Apply the patch conflict resolution one-off patches that were determined to be needed when you performed the steps in Section 2.2, "One-off Patch Conflict Detection and Resolution". 2.5.2 Loading Modified SQL Files into the Database The following steps load modified SQL files into the database. For an Oracle RAC environment, perform these steps on only one node.
The catbundle.sql execution is reflected in the dba_registry_history view by a row associated with bundle series PSU. For information about the catbundle.sql script, see My Oracle Support Document 605795.1 Introduction to Oracle Database catbundle.sql.
where TIMESTAMP is of the form YYYYMMMDD_HH_MM_SS. If there are errors, see Section 3, "Known Issues".
For more information on the OJVM mitigation patch, see Document 1929745.1 Oracle Recommended Patches -- "Oracle JavaVM Component Database PSU" (OJVM PSU) Patches. 2.5.3 Upgrade Oracle Recovery Manager Catalog If you are using the Oracle Recovery Manager, the catalog needs to be upgraded. Enter the following command to upgrade it: $ rman catalog username/password@alias RMAN> UPGRADE CATALOG; 2.6 Patch Post-Installation Instructions for Databases Created or Upgraded after Installation of Patch in the Oracle Home These instructions are for a database that is created or upgraded after the installation of the patch. You must execute the steps in Section 2.5.2, "Loading Modified SQL Files into the Database" for any new database only if it was created by any of the following methods:
There are no actions required for databases that have been upgraded. The patch rollback instructions will differ based on the configuration of the Grid infrastructure and the Oracle RAC database homes. Roll Back instructions for Oracle RAC Database Homes and GI are listed below. The most common configurations are listed as follows:
For other configurations listed below, see My Oracle Support Document 1641136.1:
Roll Back the Oracle RAC Database Homes and GI Together
As root user, execute the following command on each node of the cluster. # opatch auto <UNZIPPED_PATCH_LOCATION>/26610246 -rollback -ocmrf <ocm response file> 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.
2.8 Patch Post-Deinstallation Instructions for an Oracle RAC Environment Follow these steps only on the node for which the steps in Section 2.5.2, "Loading Modified SQL Files into the Database" were executed during the patch application.:
In an Oracle RAC environment, the name of the rollback script will have the format catbundle_PSU_<database SID PREFIX>_ROLLBACK.sql.
All other instances can be started and accessed as usual while you are executing the deinstallation steps. For issues documented after the release of this PSU, see My Oracle Support Document 2264639.1 Oracle Grid Infrastructure Patch Set Update 11.2.0.4.170718 Known Issues. This section includes the following known issues: When Trace File Analyzer (TFA) is patched as part of a PSU, any rollback of the PSU will not roll back any patch applied to TFA. This is intended behavior, but if there are any issues with patching TFA itself, then manual steps will be required to recover. If a PSU has been rolled back and due to some issue with patching TFA it has to be reinstalled, then you should:
If a PSU is installed but not rolled back and there are issues with TFA, then contact Oracle Support to help resolve the TFA issues. After rolling back using opatch auto from the Oracle Grid infrastructure Patch Set Update 11.2.0.4.4, database and listener resources are going to be offline. You should start the database and listener resources using the srvctl command. When performing any further patching actions, databases and listeners may not be started up automatically for the home being patched on a node. Start up these explicitly by executing srvctl start database and srvctl start listener commands. When 11.2.0.4.160719 GIPSU is applied on top of 11.2.0.4.160419 GIPSU on platform Linux x86 32-bit, it results in a conflict error. To workaround this issue, roll back 11.2.0.4.160419 GIPSU if it has been previously applied, and then apply 11.2.0.4.160719 GIPSU. The following documents are references for this patch. Document 1494646.1 Patch Installation and Deinstallation Document 1494652.1 Instructions for Mounting/Unmounting ACFS File Systems Document 854428.1 Patch Set Updates for Oracle Products Document 360870.1 Impact of Java Security Vulnerabilities on Oracle Products Document 468959.1 Enterprise Manager Grid Control Known Issues Document 1339140.1 Opatch/Patch Questions/Issues for Oracle Clusterware (Grid Infrastructure or CRS) and RAC Environments Document 2264639.1 Oracle Grid Infrastructure Patch Set Update 11.2.0.4.170718 Known Issues 5 Manual Steps for Apply/Rollback Patch See My Oracle Support Document 1641136.1 for cases where opatch auto cannot be used. See My Oracle Support Document 1614046.1. 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. 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/us/corporate/accessibility/support/index.html if you are hearing impaired.
Patch 26610246 - Oracle Grid Infrastructure Patch Set Update 11.2.0.4.170814 Jul2017 (Includes Database PSU) Copyright © 2006, 2017, 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 END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government. 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 about 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 unless otherwise set forth in an applicable agreement between you and Oracle. 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, except as set forth in an applicable agreement between you and Oracle. Copyright © 2006, 2017, Oracle and/or its affiliates. All rights reserved.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Table 2 lists the various configurations and the applicable PSU that should be used to patch that configuration.
Table 2 Configuration and PSU Mapping
| Configuration | GI Version | Database Versions | PSU Patch (to Apply) | OPatch Command | Comments |
|---|---|---|---|---|---|
| GI Home in conjunction with RAC, RACOne, or Single Instance home | 11.2.0.4 | 11.2.0.4 | GI PSU | OPatch auto | GI Home and all the Database Homes will be patched |
| GI Home in conjunction with RAC, RACOne, or Single Instance home | 11.2.0.4 | 11.2.0.4 and prior versions | GI PSU | OPatch auto | GI Home and Database Home at 11.2.0.4 version will be patched. For Database home with version other than 11.2.0.4, apply the appropriate Database PSU for that version. For example, apply 11.1.0.7.x PSU to Database version 11.1.0.7.0. |
| GI Home in conjunction with RAC, RACOne, or Single Instance home | 11.2.0.4 | Versions prior to 11.2.0.4 | GI PSU | OPatch auto | GI Home alone is patched. For Database home, apply the appropriate Database PSU for that version. For example, apply 11.1.0.7.x PSU to Database version 11.1.0.7.0. |
| Oracle Restart Home | 11.2.0.4 | 11.2.0.4 | GI PSU | OPatch auto | GI Home and all the Database Homes will be patched. |
| Database Single Instance home | NA | 11.2.0.4 | Database PSU | OPatch apply | None |
| Database Client home | NA | 11.2.0.4 | Database PSU | OPatch apply | None |
Table 3 lists the various patches by patch number getting installed as part of this GI PSU patch.
Table 3 Patch Numbers Getting Installed as Part of this GI PSU Patch
| Patch Number | Description | Applicable Homes |
|---|---|---|
| 26609445 | DB PSU 11.2.0.4.170814 (INCLUDES CPUJUL2017) | Both DB Homes and Grid Home |
| 26609929 | OCW PSU 11.2.0.4.170814 | Both DB Homes and Grid Home |
| 22502505 | ACFS PSU 11.2.0.4.160419 | Only Grid Home |
2 Patch Installation and Deinstallation
This section includes the following sections:
-
Section 2.2, "One-off Patch Conflict Detection and Resolution"
-
Section 2.8, "Patch Post-Deinstallation Instructions for an Oracle RAC Environment"
2.1 Patch Installation Prerequisites
You must satisfy the conditions in the following sections before applying the patch:
2.1.1 OPatch Utility Information
You must use the OPatch utility version 11.2.0.3.6 or later to apply this patch. Oracle recommends that you use the latest released OPatch version for 11.2 releases, which is available for download from My Oracle Support patch 6880880 by selecting ARU link for the 11.2.0.0.0 release. It is recommended that you download the Opatch utility and the patch in a shared location to be able to access them from any node in the cluster for the patch application on each node.
When patching the GI Home, a shared location on ACFS only needs to be unmounted on the node where the GI Home is being patched.
The new opatch utility should be updated in all the Oracle RAC database homes and the GI home that are being patched.
To update Opatch, use the following instructions:
-
Download the OPatch utility to a temporary directory.
-
For each Oracle RAC database home and the GI home that are being patched, run the following commands as the home owner to extract the OPatch utility.
<span style="color:#000000">$ unzip <OPATCH-ZIP> -d <ORACLE_HOME> $ <ORACLE_HOME>/OPatch/opatch version </span>
The version output of the previous command should be 11.2.0.3.6 or later.
For information about OPatch documentation, including any known issues, see My Oracle Support Document 293369.1 OPatch documentation list.
2.1.2 OCM Configuration
The OPatch utility will prompt for your OCM (Oracle Configuration Manager) response file when it is run. You should enter a complete path of OCM response file if you already have created this in your environment. OCM response file is required and is not optional.
If you do not have the OCM response file (ocm.rsp), see the following My Oracle Support Document 966023.1 How To Create An OCM Response File For Opatch Silent Installation.
2.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.
<span style="color:#000000">$ <ORACLE_HOME>/OPatch/opatch lsinventory -detail -oh <ORACLE_HOME>
</span>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.
2.1.4 Download and Unzip the Patch
To apply the patch, it must be accessible from all nodes in the Oracle cluster. Download the patch and unzip it to a shared location, this is called the <UNZIPPED_PATCH_LOCATION>. This directory must be empty and not be /tmp. Additionally, the directory should have read permission for the ORA_INSTALL group.
<span style="color:#000000">$ cd <UNZIPPED_PATCH_LOCATION>
</span>Check that the directory is empty.
<span style="color:#000000">$ ls
</span>Unzip the patch as grid home owner.
<span style="color:#000000">$ unzip p26610246_112040_<platform>.zip
</span>
2.1.5 Stop EM Agent Processes Prior to Patching and Prior to Rolling Back the Patch
You must stop the EM agent processes running from the database home, prior to patching the Oracle RAC database or GI Home and prior to rolling back the patch from Oracle RAC database or GI Home. Execute the following command on the node to be patched or the node where the patch is to be rolled back.
As the Oracle RAC database home owner execute:
<span style="color:#000000">$ <ORACLE_HOME>/bin/emctl stop dbconsole
</span>
2.2 One-off Patch Conflict Detection and Resolution
See My Oracle Support Document 1061295.1 Patch Set Updates - One-off Patch Conflict Resolution to determine, for each conflicting patch, whether a conflict resolution patch is already available, and if you need to request a new conflict resolution patch or if the conflict may be ignored.
The fastest and easiest way to determine whether you have one-off patches in the Oracle home that conflict with the patch, and to get the necessary conflict resolution patches, is to use the Patch Recommendations and Patch Plans features on the Patches & Updates tab in My Oracle Support. These features work in conjunction with the My Oracle Support Configuration Manager. Recorded training sessions on these features can be found in Document 603505.1.
However, if you are not using My Oracle Support Patch Plans, the My Oracle Support Conflict Checker tool enables you to upload an OPatch inventory and check the patches that you want to apply to your environment for conflicts.
If no conflicts are found, you can download the patches. If conflicts are found, the tool finds an existing resolution to download. If no resolution is found, it will automatically request a resolution, which you can monitor in the Plans and Patch Requests region of the Patches & Updates tab.
For more information, see Knowledge Document 1091294.1, How to use the My Oracle Support Conflict Checker Tool.
| Note: When performing the conflict analysis on the Database Oracle Home inventory, use the Database PSU patch instead of the Grid Infrastructure PSU patch. |
2.3 OPatch auto for GI
The Opatch utility has automated the patch application for the Oracle Grid Infrastructure (GI) home and the Oracle RAC database homes when run with root privileges. It must be executed on each node in the cluster if the GI home or Oracle RAC database home is in non-shared storage. The utility should not be run in parallel on the cluster nodes.
For more information about opatch auto, see My Oracle Support Document 1339140.1 FAQ: OPatch/Patch Questions/Issues for Oracle Clusterware (Grid Infrastructure or CRS) and RAC Environments.
For detailed patch installation instructions, see Section 2.4, "Patch Installation".
2.4 Patch Installation
The patch instructions will differ based on the configuration of the Grid infrastructure and the Oracle RAC database homes. Patching instructions for Oracle RAC Database Homes and GI together are listed below.
The most common configurations are listed as follows:
-
Case 1: GI Home and the Database Homes that are not shared and ACFS file system is not configured.
-
Case 2: GI Home is not shared, Database Home is shared, ACFS may be used.
For other configurations listed below, see My Oracle Support Document 1641136.1:
-
GI Home is not shared, the Database Home is not shared, ACFS may be used.
-
Patching Oracle RAC Database Homes.
-
Patching GI Home alone.
-
Patching Oracle Restart Home.
-
Patching a software only GI Home installation or before the GI Home is configured.
Patching Oracle RAC Database Homes and GI Together
-
Case 1: GI Home and the Database Homes that are not shared and ACFS file system is not configured.
As root user, execute the following command on each node of the cluster:
<span style="color:#000000"># opatch auto <UNZIPPED_PATCH_LOCATION>/26610246 -ocmrf <ocm response file> </span> -
Case 2: GI Home is not shared, Database Home is shared, ACFS may be used.
Patching instructions:
-
From the Oracle database home, make sure to stop the Oracle RAC databases running on all nodes. As the database home owner execute:
<span style="color:#000000">$ <ORACLE_HOME>/bin/srvctl stop database –d <db-unique-name> </span> -
On the 1st node, unmount the ACFS file systems. See My Oracle Support Document 1494652.1 for unmounting ACFS file systems.
-
On the 1st node, apply the patch to the GI Home using the
opatch autocommand. As root user, execute the following command:<span style="color:#000000"># opatch auto <UNZIPPED_PATCH_LOCATION>/26610246 -ocmrf <ocm response file> </span> -
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.
-
On the 1st node, remount ACFS file systems. See My Oracle Support Document 1494652.1 for mounting ACFS file systems.
-
On the 1st node, apply the patch to the Database home using the
opatch autocommand. Since the Database home is shared, this operation will patch the Database home across the cluster. Note that a USM only patch cannot be applied to a database home. As root user, execute the following command:<span style="color:#000000"># opatch auto <UNZIPPED_PATCH_LOCATION>/26610246 -oh <DATABASE_HOME> -ocmrf <ocm response file> </span> -
On the 1st node only, restart the Oracle instance, which you have previously stopped in Step 1. As the database home owner execute:
<span style="color:#000000">$ <ORACLE_HOME>/bin/srvctl start instance –d <db-unique-name> -n <nodename> </span> -
On the 2nd (next) node, unmount the ACFS file systems. See My Oracle Support Document 1494652.1 for unmounting ACFS file systems.
-
On the 2nd node, apply the patch to GI Home using the
opatch autocommand. As root user, execute the following command:<span style="color:#000000"># opatch auto <UNZIPPED_PATCH_LOCATION>/26610246 -oh <GI_HOME> -ocmrf <ocm response file> </span> -
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.
-
On the 2nd node, running the
opatch autocommand in Step 9 will restart the stack. -
On the 2nd node, remount ACFS file systems. See My Oracle Support Document 1494652.1 for mounting ACFS file systems.
-
On the 2nd node only, restart the Oracle instance, which you have previously stopped in Step 1. As the database home owner execute:
<span style="color:#000000">$ <ORACLE_HOME>/bin/srvctl start instance –d <db-unique-name> -n <nodename> </span> -
Repeat Steps 8 through 13 for all remaining nodes of the cluster.
-
2.5 Patch Post-Installation Instructions
After installing the patch, perform the following actions:
-
Apply conflict resolution patches as explained in Section 2.5.1.
-
If applying a PSU, load modified SQL files into the database, as explained in Section 2.5.2.
-
Upgrade Oracle Recovery Manager catalog, as explained in Section 2.5.3.
2.5.1 Applying Conflict Resolution Patches
Apply the patch conflict resolution one-off patches that were determined to be needed when you performed the steps in Section 2.2, "One-off Patch Conflict Detection and Resolution".
2.5.2 Loading Modified SQL Files into the Database
The following steps load modified SQL files into the database. For an Oracle RAC environment, perform these steps on only one node.
-
For each database instance running on the Oracle home being patched, connect to the database using SQL*Plus. Connect as
SYSDBAand run thecatbundle.sqlscript as follows:<span style="color:#000000">cd $ORACLE_HOME/rdbms/admin sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> STARTUP SQL> @catbundle.sql psu apply SQL> QUIT </span>The
catbundle.sqlexecution is reflected in thedba_registry_historyview by a row associated with bundle seriesPSU.For information about the
catbundle.sqlscript, see My Oracle Support Document 605795.1 Introduction to Oracle Database catbundle.sql. -
If the OJVM PSU was applied for a previous GI PSU patch, you may see invalid Java classes after execution of the
catbundle.sqlscript in the previous step. If this is the case, runutlrp.sqlto re-validate these Java classes.<span style="color:#000000">cd $ORACLE_HOME/rdbms/admin sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> @utlrp.sql </span> -
Check the following log files in
$ORACLE_BASE/cfgtoollogs/catbundlefor any errors:<span style="color:#000000">catbundle_PSU_<em><database SID></em>_APPLY_<em><TIMESTAMP></em>.log catbundle_PSU_<em><database SID></em>_GENERATE_<<em>TIMESTAMP></em>.log </span>where TIMESTAMP is of the form YYYYMMMDD_HH_MM_SS. If there are errors, see Section 3, "Known Issues".
-
This patch now includes the OJVM Mitigation patch (Patch:19721304). If an OJVM PSU is installed or planned to be installed, no further actions are necessary. Otherwise, the workaround of using the OJVM Mitigation patch can be activated. As
SYSDBAdo the following from theadmindirectory:<span style="color:#000000">SQL > @dbmsjdev.sql SQL > exec dbms_java_dev.disable </span>For more information on the OJVM mitigation patch, see Document 1929745.1 Oracle Recommended Patches -- "Oracle JavaVM Component Database PSU" (OJVM PSU) Patches.
2.5.3 Upgrade Oracle Recovery Manager Catalog
If you are using the Oracle Recovery Manager, the catalog needs to be upgraded. Enter the following command to upgrade it:
<span style="color:#000000">$ rman catalog username/password@alias
RMAN> UPGRADE CATALOG;
</span>
2.6 Patch Post-Installation Instructions for Databases Created or Upgraded after Installation of Patch in the Oracle Home
These instructions are for a database that is created or upgraded after the installation of the patch.
You must execute the steps in Section 2.5.2, "Loading Modified SQL Files into the Database" for any new database only if it was created by any of the following methods:
-
Using DBCA (Database Configuration Assistant) to select a sample database (General, Data Warehouse, Transaction Processing)
-
Using a script that was created by DBCA that creates a database from a sample database
There are no actions required for databases that have been upgraded.
2.7 Patch Deinstallation
The patch rollback instructions will differ based on the configuration of the Grid infrastructure and the Oracle RAC database homes. Roll Back instructions for Oracle RAC Database Homes and GI are listed below.
The most common configurations are listed as follows:
-
Case 1: GI Home and Database Homes that are not shared and ACFS file system is not configured.
-
Case 2: GI Home is not shared, Database Home is shared and ACFS may be used.
For other configurations listed below, see My Oracle Support Document 1641136.1:
-
GI Home is not shared, the Database Home is not shared, ACFS may be used.
-
Rolling back from Oracle RAC Database Homes.
-
Rolling back from GI Home alone.
-
Rolling back the patch from Oracle Restart Home.
-
Rolling back the patch from a software only GI Home installation or before the GI Home is configured.
Roll Back the Oracle RAC Database Homes and GI Together
-
Case 1: GI Home and Database Homes that are not shared and ACFS file system is not configured.
As root user, execute the following command on each node of the cluster.
<span style="color:#000000"># opatch auto <UNZIPPED_PATCH_LOCATION>/26610246 -rollback -ocmrf <ocm response file> </span>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.
-
Case 2: GI Home is not shared, Database Home is shared and ACFS may be used.
-
From the Oracle database home, make sure to stop the Oracle RAC databases running on all nodes. As the database home owner execute:
<span style="color:#000000">$ <ORACLE_HOME>/bin/srvctl stop database –d <db-unique-name> </span> -
On the 1st node, unmount the ACFS file systems. See My Oracle Support Document 1494652.1 for unmounting ACFS file systems.
-
On the 1st node, roll back the patch from the GI Home using the
opatch autocommand. As root user, execute the following command:<span style="color:#000000"># opatch auto <UNZIPPED_PATCH_LOCATION>/26610246 -oh <GI_HOME> -rollback -ocmrf <ocm response file> </span> -
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.
-
On the 1st node, remount ACFS file systems. See My Oracle Support Document 1494652.1 for mounting ACFS file systems.
-
On the 1st node, roll back the patch to the Database home using the
opatch autocommand. This operation will rollback the patch to the Database home across the cluster given that it is a shared ACFS home. Note that a USM only patch cannot be applied to a Database home. As root user, execute the following command:<span style="color:#000000"># opatch auto <UNZIPPED_PATCH_LOCATION>/26610246 -oh <DATABASE_HOME> -rollback -ocmrf <ocm response file> </span> -
On the 1st node only, restart the Oracle instance, which you have previously stopped in Step 1. As the database home owner execute:
<span style="color:#000000">$ <ORACLE_HOME>/bin/srvctl start instance –d <db-unique-name> -n <nodename> </span> -
On the 2nd (next) node, unmount the ACFS file systems. See My Oracle Support Document 1494652.1 for unmounting ACFS file systems.
-
On the 2nd node, roll back the patch to GI Home using the
opatch autocommand. As root user, execute the following command:<span style="color:#000000"># opatch auto <UNZIPPED_PATCH_LOCATION>/26610246 -oh <GI_HOME> -rollback -ocmrf <ocm response file> </span> -
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.
-
On the 2nd node, running the
opatch autocommand in Step 9 will restart the stack. -
On the 2nd node, remount ACFS file systems. See My Oracle Support Document 1494652.1 for mounting ACFS file systems.
-
On the 2nd node only, restart the Oracle instance, which you have previously stopped in Step 1. As the database home owner execute:
<span style="color:#000000">$ <ORACLE_HOME>/bin/srvctl start instance –d <db-unique-name> -n <nodename> </span> -
Repeat Steps 8 through 13 for all remaining nodes of the cluster.
-
2.8 Patch Post-Deinstallation Instructions for an Oracle RAC Environment
Follow these steps only on the node for which the steps in Section 2.5.2, "Loading Modified SQL Files into the Database" were executed during the patch application.:
-
Start all database instances running from the Oracle home. (For more information, see Oracle Database Administrator's Guide.)
-
For each database instance running out of the
ORACLE_HOME, connect to the database using SQL*Plus asSYSDBAand run the rollback script as follows:<span style="color:#000000">cd $ORACLE_HOME/rdbms/admin sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> STARTUP SQL> @catbundle_PSU_<em><database SID PREFIX></em>_ROLLBACK.sql SQL> QUIT </span>In an Oracle RAC environment, the name of the rollback script will have the format catbundle_PSU_<database SID PREFIX>_ROLLBACK.sql.
-
If the OJVM PSU was applied for a previous GI PSU patch, you may see invalid Java classes after execution of the
catbundle.sqlscript in the previous step. If this is the case, runutlrp.sqlto re-validate these Java classes.<span style="color:#000000">cd $ORACLE_HOME/rdbms/admin sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> @utlrp.sql </span> -
Check the log file for any errors. The log file is found in
$ORACLE_BASE/cfgtoollogs/catbundleand is namedcatbundle_PSU_<database SID>_ROLLBACK_<TIMESTAMP>.logwhere TIMESTAMP is of the form YYYYMMMDD_HH_MM_SS. If there are errors, see Section 3, "Known Issues". -
Ensure that you verify the Oracle Inventory and compare the output with the one you ran in Section 2.1.3, "Validation of Oracle Inventory" and re-apply any patches that were rolled back as part of this patch apply. To verify the inventory, run the following command:
<span style="color:#000000">$ opatch lsinventory </span>
All other instances can be started and accessed as usual while you are executing the deinstallation steps.
3 Known Issues
For issues documented after the release of this PSU, see My Oracle Support Document 2264639.1 Oracle Grid Infrastructure Patch Set Update 11.2.0.4.170718 Known Issues.
This section includes the following known issues:
Issue 1
When Trace File Analyzer (TFA) is patched as part of a PSU, any rollback of the PSU will not roll back any patch applied to TFA. This is intended behavior, but if there are any issues with patching TFA itself, then manual steps will be required to recover.
If a PSU has been rolled back and due to some issue with patching TFA it has to be reinstalled, then you should:
-
Remove TFA by executing the following command on each node as the root user:
<span style="color:#000000">GIHOME/tfa/<nodename>/tfa_home/bin/uninstalltfa.sh -local </span> -
Reinstall the previous TFA version by executing the following command on each node as the root user:
<span style="color:#000000">GIHOME/crs/install/tfa_setup.sh -crshome <path to GIHOME> -silent </span>
If a PSU is installed but not rolled back and there are issues with TFA, then contact Oracle Support to help resolve the TFA issues.
Issue 2
After rolling back using opatch auto from the Oracle Grid infrastructure Patch Set Update 11.2.0.4.4, database and listener resources are going to be offline.
You should start the database and listener resources using the srvctl command.
When performing any further patching actions, databases and listeners may not be started up automatically for the home being patched on a node. Start up these explicitly by executing srvctl start database and srvctl start listener commands.
Issue 3
When 11.2.0.4.160719 GIPSU is applied on top of 11.2.0.4.160419 GIPSU on platform Linux x86 32-bit, it results in a conflict error.
To workaround this issue, roll back 11.2.0.4.160419 GIPSU if it has been previously applied, and then apply 11.2.0.4.160719 GIPSU.
4 References
The following documents are references for this patch.
Document 1494646.1 Patch Installation and Deinstallation
Document 1494652.1 Instructions for Mounting/Unmounting ACFS File Systems
Document 854428.1 Patch Set Updates for Oracle Products
Document 360870.1 Impact of Java Security Vulnerabilities on Oracle Products
Document 468959.1 Enterprise Manager Grid Control Known Issues
Document 1339140.1 Opatch/Patch Questions/Issues for Oracle Clusterware (Grid Infrastructure or CRS) and RAC Environments
Document 2264639.1 Oracle Grid Infrastructure Patch Set Update 11.2.0.4.170718 Known Issues
5 Manual Steps for Apply/Rollback Patch
See My Oracle Support Document 1641136.1 for cases where opatch auto cannot be used.
6 Bugs Fixed by This Patch
See My Oracle Support Document 1614046.1.
7 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/us/corporate/accessibility/support/index.html if you are hearing impaired.
Patch 26610246 - Oracle Grid Infrastructure Patch Set Update 11.2.0.4.170814 Jul2017 (Includes Database PSU)
Copyright © 2006, 2017, 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 END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
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 about 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 unless otherwise set forth in an applicable agreement between you and Oracle. 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, except as set forth in an applicable agreement between you and Oracle.
Copyright © 2006, 2017, Oracle and/or its affiliates. All rights reserved.
3万+
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
