| Oracle® Enterprise Manager Administrator's Guide for Software and Server Provisioning and Patching 10g Release 5 (10.2.0.5.0) Part Number E14500-04 |
|
|
PDF · Mobi · ePub |
| Oracle® Enterprise Manager Administrator's Guide for Software and Server Provisioning and Patching 10g Release 5 (10.2.0.5.0) Part Number E14500-04 |
|
|
PDF · Mobi · ePub |
This chapter explains how you can patch Oracle Clusterware. In particular, this chapter covers the following:
This section helps you get started with this chapter by providing an overview of the steps involved in patching Oracle Clusterware. Consider this section to be a documentation map to understand the sequence of actions you must perform to successfully patch Oracle Clusterware. Click the reference links provided against the steps to reach the relevant sections that provide more information.
Table 17-1 Getting Started with Patching Oracle Clusterware
| Step | Description | |
|---|---|---|
 |
Understanding the Deployment Procedure Understand the Deployment Procedure that is offered by Enterprise Manager Grid Control for patching Oracle Clusterware. Know how the Deployment Procedure functions, what use cases it covers, and so on. |
To learn about the Deployment Procedure, see Deployment Procedures. |
 |
Knowing About The Supported Releases Know what releases of Oracle Clusterware can be patched by the Deployment Procedure. |
To learn about the releases supported by the Deployment Procedure, see Supported Releases. |
 |
Selecting the Patching Mode Identify whether the host that runs Enterprise Manager Grid Control has an Internet connection to connect to My Oracle Support. If it has, then choose to patch in online mode. Otherwise, choose to patch in offline mode. |
|
 |
Patching Clusterware Nodes Individually or Collectively Decide whether you want to patch the nodes one by one, using the Rolling methodology, or all at a time, in parallel, using the All Nodes methodology. |
Online Mode:
Offline Mode:
|
 |
Understanding the Deployment Phases The Deployment Procedure consists of a series of interview screens that take you through the different deployment phases and capture the required information. Understand the different phases involved and know what information is captured in each phase. |
Online Mode:
Offline Mode:
|
 |
Meeting the Prerequisites Before you run any Deployment Procedure, you must meet the prerequisites, such as setting up of the environment for online or offline patching, applying mandatory patches, setting up of Oracle Software Library, and so on. |
Online Mode:
Offline Mode:
|
 |
Running the Deployment Procedure Run the Deployment Procedure to successfully patch Oracle Clusterware. |
Online Mode:
Offline Mode:
|
Enterprise Manager Grid Control offers the following Deployment Procedures for patching Oracle Clusterware:
Patch Oracle Clusterware - Rolling
Patch Oracle Clusterware - All Nodes
While the former one allows you to patch the nodes one by one, the latter one allows you to patch all the nodes at a time, in parallel. For more information about these patching methodologies and circumstances under which you must use the Rolling methodology or All Nodes methodology, see Understanding Patching Methodologies.
Using these Deployment Procedures, you can patch the following releases of Oracle Clusterware:
Oracle Clusterware 10g Release 1 (10.1.x.x)
Oracle Clusterware 10g Release 2 (10.2.x.x)
Oracle Clusterware 11g Release 1 (11.1.x.x)
IMPORTANT:
These Deployment Procedures are not supported on Microsoft Windows.This section describes how you can patch Oracle Clusterware in online mode, that is, by connecting to My Oracle Support. This option is best suited when you have an Internet connection on the host where Enterprise Manager Grid Control is running.
In online mode, you can either patch the nodes one by one, or patch all the nodes at a time, in parallel. This section provides instructions for both these methodologies.
In particular, this section provides instructions for the following:
This section describes how you can patch the nodes of Oracle Clusterware one by one, using the Rolling methodology.
This methodology is best suited when you are applying one-off patches that support this methodology, and when you want to maintain high availability of your targets, so when one node is being patched, the other nodes are available for service. For example, if you are patching a clusterware that has five nodes, then the first node is shut down, patched, and restarted, and then the process is rolled over to the next node, and so on, until all the nodes are patched successfully.
This section covers the following:
iMPORTANT:
You cannot use this methodology to patch shared Oracle homes. If you want to patch a shared Oracle home, then use Deployment Procedure that support the All Nodes methodology. For more information, see Patching Oracle Clusterware Nodes Collectively.
Although most one-off patches support this methodology, there are some one-off patches that can be applied only using the All Nodes methodology. You can identify the supported methodology while downloading the one-off patches from My Oracle Support.
If the Deployment Procedure abruptly stops or terminates at any step while it is being run, you may rerun the same procedure from where it stopped or from the beginning, all over again.
The following describes the different phases involved in this Deployment Procedure:
Table 17-2 Deployment Phases for Patching Oracle Clusterware in Online Mode
| Phase | Description |
|---|---|
 |
Software Updates Allows you to select the software updates (patches and patch sets) you want to apply, black out associated targets, and run OPatch options. |
 |
Target List Allows you to select the clusterware targets you want to patch. |
 |
Credentials Allows you to specify Oracle home credentials required to patch clusterware Oracle homes, and host credentials to access the hosts where the clusterware instances are present. |
 |
Schedule Allows you to schedule the Deployment Procedure to run immediately or later. |
 |
Review Allows you to review the details you have provided for patching the selected clusterware instances. |
Before running the Deployment Procedure, meet the following prerequisites:
Ensure that you meet the prerequisites described in the following sections:
Ensure that you have the latest release of the OPatch software on the target host (where the clusterware to be patched is running).
Ensure that operating system users such as oracle and crsuser are available on all the nodes of the cluster. These users must be a part of the relevant operating system groups such as dba and oinstall.
Ensure that you run the prerequisite checker Deployment Procedure as described in Running Patch Prerequisite Checker for Oracle Clusterware.
Ensure that you use an operating system user that has the privileges to run the Deployment Procedure and its commands on the target hosts. If you do not have the privileges to do so, that is, if you are using a locked account, then request your administrator (a designer) to either customize the Deployment Procedure to run it as another user or ignore the steps that require special privileges. For information about customization, see Chapter 23, "Customizing Steps to Run as Another User".
To patch an Oracle Cluterware, follow these steps:
In Grid Control, click the Deployments tab.
On the Deployments page, in the Deployment Procedure Manager section, click Patch Procedures.
On the Deployment Procedure Manager page, in the Procedures subtab, from the table, select Patch Oracle Clusterware - Rolling. Then click Schedule Deployment.
Enterprise Manager Grid Control displays the Software Updates page of the Deployment Procedure.
On the Software Updates page, do the following:
In the Select Stage Location section, retain the default selection, that is, Enter Stage Location that has the value %emd_root%/EMStage.
This default value refers to a location on the target host where the clusterware to be patched is running. The software updates are downloaded from My Oracle Support to Oracle Software Library, and then staged in this location on the target hosts.
You can modify the location if you want to, and click Save. If you save multiple custom locations, then the Select Stage Location option gets enabled and allows you to select any of the saved custom locations the next time you visit the same page.
Instead of %emd_root%, you can also specify %oracle_home% to indicate the current home location being patched or %perlbin% to indicate the location of perl binary used by Oracle Management Agent (Management Agent).
In the CRS Updates section, click Add to search and select software updates from My Oracle Support. Alternatively, if you have a text file that contains details about the patches, then click Upload From File to select and upload that text file.
On clicking Add, Enterprise Manager Grid Control displays the Search and Select Software Updates page. On this page, select Search My Oracle Support, specify the details of the patches you want to search, and click Go.
Enterprise Manager Grid Control connects to My Oracle Support, searches the patches, and displays details about them on the Search and Select Software Updates page. Select the ones you want to apply using the Deployment Procedure, and click Select.
On clicking Upload From File, Enterprise Manager Grid Control displays the Upload File page. On this page, select Upload from Local Machine or Upload from Software Library depending on where the text file is available, click Browse to search and select that file, and then click Upload.
In the Black Out Associated Targets section, retain the default selection so that all targets associated with the clusterware to be patched are blacked out while the patching is in progress.
In the Advanced OPatch Options section, specify any opatch-related options you want to pass while running this Deployment Procedure. For example, if you want the Deployment Procedure to ignore duplicate patches, then specify -skip_duplicate.
The following are the options you can specify:
-skip_duplicate, skips duplicate patches
-skip_conflict, skips conflicting patches
-skip_missing_component, skips patches whose components are missing
-invPtrLoc, the location of oraInst.loc file
Note:
If you want to specify multiple options, then separate the list with a white space. For example,
-skip_duplicate -skip_conflictClick Next.
On the Target List page, in the Clusterware Targets to be Patched section, click Add to add the clusterware targets you want to patch. Then click Next.
When you click Add, Enterprise Manager Grid Control displays the Select Target page. On this page, search and select the clusterware you want to patch, and click Continue. On the next page, select the associated instances, and click Select to return to the Target List page.
On the Credentials page, in the Home Credentials section, specify the Oracle home credentials required to patch the clusterware Oracle homes, and in the Host Credentials section, specify the operating system credentials to log in to the hosts where the clusterware Oracle homes are present. Then click Next.
Note:
When there are Oracle home active steps, the Home Credentials section appears. When there are host-level active steps, the Host Credentials section appears. When Oracle home active steps and host-level active steps are present, both the sections appear.For both sections, choose to use the preferred credentials so that the credentials stored in the Management Repository can be used.
Of course, you can always override the preferred credentials with a new set of credentials. If you choose to do so, you can specify either a common set of credentials to be used across Oracle homes and hosts, or a unique set of credentials for each Oracle home and host.
After specifying a new set of credentials to override the preferred credentials, click Save OH Credential if you want to store the new credentials in the Management Repository.
On the Schedule page, schedule the Deployment Procedure to run either immediately or later.
For Instance Name, specify a unique name for this Deployment Procedure instance so that it can be tracked later and reused with the same settings.
On the Review page, review the details you have provided for patching the selected clusterware, and click Submit.
The prerequisites and the deployment instructions for patching all the nodes of Oracle Clusterware at a time, in parallel, using the All Nodes methodology, are the same as the ones described in Patching Oracle Clusterware Nodes Individually. However, in Step (3), on the Deployment Procedure Manager page, in the Procedures tab, from the table, select Patch Oracle Clusterware - All Nodes. Then click Schedule Deployment.
Although the instructions remain the same, when you submit the Deployment Procedure, Enterprise Manager Grid Control internally patches all the nodes of the clusterware collectively, that is, all the nodes are shut down and the patch is applied on all of them at the same time.
This methodology is best suited when you are applying a patch set or those one-off patches that support this methodology, or when you want to patch a shared Oracle home clusterware. For example, if you are patching a shared Oracle home clusterware that has five nodes, the patch and the scripts within it are run only once on the shared Oracle home, and the other nodes are ignored or skipped. This saves time as the patching operation is performed only once, that is, only on the shared Oracle home, not on all the nodes.
Note:
Patching of shared Oracle homes is supported only for Oracle Clusterware 10g Release 2 (10.2.0.1) or higher.
If the Deployment Procedure abruptly stops or terminates at any step while it is being run, you may rerun the same procedure from where it stopped or from the beginning, all over again.
This section describes how you can patch Oracle Clusterware in offline mode, that is, without connecting to My Oracle Support. This option is best suited when you do not have an Internet connection on the host where Enterprise Manager Grid Control is running.
In offline mode, you can either patch the nodes one by one, or patch all the nodes at a time, in parallel. This section provides instructions for both these methodologies.
In particular, this section provides instructions for the following:
This section describes how you can patch the nodes of Oracle Clusterware one by one, using the Rolling methodology.
This methodology is best suited when you are applying one-off patches that support this methodology, and when you want to maintain high availability of your targets, so when one node is being patched, the other nodes are available for service. For example, if you are patching a clusterware that has five nodes, then the first node is shut down, patched, and restarted, and then the process is rolled over to the next node, and so on, until all the nodes are patched successfully.
This section covers the following:
The following describes the different phases involved in this Deployment Procedure:
Table 17-3 Deployment Phases for Patching Oracle Clusterware in Offline Mode
| Phase | Description |
|---|---|
|
Software Updates Allows you to select the software updates (patches and patch sets) you want to apply, black out associated targets, and run OPatch options. |
|
Target List Allows you to select the clusterware targets you want to patch. |
|
Credentials Allows you to specify Oracle home credentials required to patch clusterware Oracle homes, and host credentials to access the hosts where the clusterware instances are present. |
|
Schedule Allows you to schedule the Deployment Procedure to run immediately or later. |
|
Review Allows you to review the details you have provided for patching the selected clusterware instances. |
Before running the Deployment Procedure, meet the following prerequisites:
Ensure that you meet the prerequisites described in the following sections:
Ensure that you have the latest release of the OPatch software on the target host (where the clusterware to be patched is running).
Ensure that operating system users such as oracle and crsuser are available on all the nodes of the cluster. These users must be a part of the relevant operating system groups such as dba and oinstall.
Ensure that you run the prerequisite checker Deployment Procedure as described in Running Patch Prerequisite Checker for Oracle Clusterware.
Ensure that you use an operating system user that has the privileges to run the Deployment Procedure and its commands on the target hosts. If you do not have the privileges to do so, that is, if you are using a locked account, then request your administrator (a designer) to either customize the Deployment Procedure to run it as another user or ignore the steps that require special privileges. For information about customization, see Chapter 23, "Customizing Steps to Run as Another User".
To patch an Oracle Cluterware, follow these steps:
In Grid Control, click the Deployments tab.
On the Deployments page, in the Deployment Procedure Manager section, click Patch Procedures.
On the Deployment Procedure Manager page, in the Procedures subtab, from the table, select Patch Oracle Clusterware - Rolling. Then click Schedule Deployment.
Enterprise Manager Grid Control displays the Software Updates page of the Deployment Procedure.
On the Software Updates page, do the following:
In the Select Stage Location section, retain the default selection, that is, Enter Stage Location that has the value %emd_root%/EMStage.
This default value refers to a location on the target host where the clusterware to be patched is running. The software updates are downloaded from My Oracle Support to Oracle Software Library, and then staged in this location on the target hosts.
You can modify the location if you want to, and click Save. If you save multiple custom locations, then the Select Stage Location option gets enabled and allows you to select any of the saved custom locations the next time you visit the same page.
Instead of %emd_root%, you can also specify %oracle_home% to indicate the current home location being patched or %perlbin% to indicate the location of perl binary used by Oracle Management Agent (Management Agent).
In the CRS Updates section, click Add to search and select software updates from My Oracle Support. Alternatively, if you have a text file that contains details about the patches, then click Upload From File to select and upload that text file.
On clicking Add, Enterprise Manager Grid Control displays the Search and Select Software Updates page. On this page, select Search Software Library, specify the details of the patches you want to search, and click Go.
Enterprise Manager Grid Control searches the patches in Oracle Software Library, and displays details about them on the Search and Select Software Updates page. Select the ones you want to apply using the Deployment Procedure, and click Select.
On clicking Upload From File, Enterprise Manager Grid Control displays the Upload File page. On this page, select Upload from Local Machine or Upload from Software Library depending on where the text file is available, click Browse to search and select that file, and then click Upload.
In the Black Out Associated Targets section, retain the default selection so that all targets associated with the clusterware to be patched are blacked out while the patching is in progress.
In the Advanced OPatch Options section, specify any opatch-related options you want to pass while running this Deployment Procedure. For example, if you want the Deployment Procedure to ignore duplicate patches, then specify -skip_duplicate.
The following are the options you can specify:
-skip_duplicate, skips duplicate patches
-skip_conflict, skips conflicting patches
-skip_missing_component, skips patches whose components are missing
-invPtrLoc, the location of oraInst.loc file
Note:
If you want to specify multiple options, then separate the list with a white space. For example,-skip_duplicate -skip_conflictClick Next.
On the Target List page, in the Clusterware Targets to be Patched section, click Add to add the clusterware targets you want to patch. Then click Next.
When you click Add, Enterprise Manager Grid Control displays the Select Target page. On this page, search and select the clusterware you want to patch, and click Continue. On the next page, select the associated instances, and click Select to return to the Target List page.
On the Credentials page, in the Home Credentials section, specify the Oracle home credentials required to patch the Oracle homes, and in the Host Credentials section, specify the operating system credentials to log in to the hosts where the Oracle homes are present. Then click Next.
Note:
When there are Oracle home active steps, the Home Credentials section appears. When there are host-level active steps, the Host Credentials section appears. When Oracle home active steps and host-level active steps are present, both the sections appear.For both sections, choose to use the preferred credentials so that the credentials stored in the Management Repository can be used.
Of course, you can always override the preferred credentials with a new set of credentials. If you choose to do so, you can specify either a common set of credentials to be used across Oracle homes and hosts, or a unique set of credentials for each Oracle home and host.
After specifying a new set of credentials to override the preferred credentials, click Save OH Credential if you want to store the new credentials in the Management Repository.
On the Schedule page, schedule the Deployment Procedure to run either immediately or later.
For Instance Name, specify a unique name for this Deployment Procedure instance so that it can be tracked later and reused with the same settings.
On the Review page, review the details you have provided for patching the selected clusterware, and click Submit.
The prerequisites and the deployment instructions for patching all the nodes of Oracle Clusterware at a time, in parallel, using the All Nodes methodology, are the same as the ones described in Patching Oracle Clusterware Nodes Individually. However, in Step (3), on the Deployment Procedure Manager page, in the Procedures tab, from the table, select Patch Oracle Clusterware - All Nodes. Then click Schedule Deployment.
Although the instructions remain the same, when you submit the Deployment Procedure, Enterprise Manager Grid Control internally patches all the nodes of the clusterware collectively, that is, all the nodes are shut down and the patch is applied on all of them at the same time.
This methodology is best suited when you are applying a patch set or those one-off patches that support this methodology, or when you want to patch a shared Oracle home clusterware. For example, if you are patching a shared Oracle home clusterware that has five nodes, the patch and the scripts within it are run only once on the shared Oracle home, and the other nodes are ignored or skipped. This saves time as the patching operation is performed only once, that is, only on the shared Oracle home, not on all the nodes.
Note:
Patching of shared Oracle homes is supported only for Oracle Clusterware 10g Release 2 (10.2.0.1) or higher.Note:
If the Deployment Procedure abruptly stops or terminates at any step while it is being run, you may rerun the same procedure from where it stopped or from the beginning, all over again.
|
 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|