9 Deleting or Scaling Down Oracle Real Application Clusters

Deployment Phases

The following describes the different phases involved in this Deployment Procedure:

Table 9-2 Deployment Phases Involved in Deleting the Entire Oracle RAC

Phase	Description
	Delete/Scale Down Oracle RAC Allows you to select an existing Oracle RAC and all the nodes you want to delete from it, specify Oracle home credentials, schedule the Deployment Procedure to run immediately or later.
	Review Allows you to review the details you have provided for deleting the entire Oracle RAC instance.

Prerequisites

Before running the Deployment Procedure, meet the following prerequisites:

Prerequisites for Designers

• Ensure that you meet the prerequisites described in the following sections:

  • Mandatory Infrastructure Requirements for Provisioning and Patching

  • Optional Infrastructure Requirements

• Ensure that oinstall and dba groups are available.

• Ensure that operating system users such as oracle and crsuser are available on all nodes of the cluster. These users must be a part of the relevant operating system groups such as dba and oinstall.

• Ensure that the credentials being used to run this operation along with the group ID are the same on all nodes of the selected cluster.

Prerequisites for Operators

• If you have PAM/LDAP enabled in your environment, then ensure that the target agents are configured with PAM/LDAP. For more information, see My Oracle Support note 422073.1.

• Ensure that you use an operating system user that has the privileges to run the Deployment Procedure, and that can switch to root user and run all commands on the target hosts. For example, commands such as mkdir, ls, and so on.

  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 example, user account A might have the root privileges, but you might use user account B to run the Deployment Procedure. In this case, you can switch from user account B to A by customizing the Deployment Procedure.

  For information about customization, see Chapter 30, "Customizing Steps to Run as Another User".

Procedure

To delete the entire Oracle RAC, follow these steps:

1. In Grid Control, click the Deployments tab.

2. On the Deployments page, in the Deployment Procedure Manager section, click RAC Provisioning Procedures.

3. On the Deployment Procedure Manager page, in the Procedures subtab, from the table, select Delete/Scale down Oracle Real Application Clusters. Then click Schedule Deployment.

   Enterprise Manager Grid Control displays the Delete/Scale down Oracle Real Application Clusters page.

4. On the Delete/Scale down Oracle Real Application Clusters page, do the following:

   1. In the Select Cluster section, click the torch icon for Select Cluster and select an Oracle Clusterware instance that you want to delete. Along with the selected Oracle Clusterware, the associated Oracle RAC and ASM instances will also be deleted. The table displays details about the member nodes that are part of the selected Oracle Clusterware.

      
      

      Note:

      When you use the torch icon to search for Oracle Clusterware, if you do not find the Oracle Clusterware that you are looking for, then from the tip mentioned below the table, click here to manually provide details about that clusterware and search for it.

      This is particularly useful when you want to delete partially-provisioned or configured Oracle Clusterware instances because, by default, when you click the torch icon, only the fully-provisioned clusterware instances appear for selection. In this case, to search, select, and delete the partially-provisioned instances, click here, and in the Enter Cluster Details window, manually provide details about the cluster node that contains the partially-provisioned instance and click OK. You can then select the host that appears in the Select Nodes to Delete section and mark for deletion.

   2. In the Reference Host Options section, from the Cluster Node list, select a node that you want to use as the primary node for all cleanup operations.

      
      

      For Working directory, specify the full path to an existing directory on the selected node that can be used for staging files temporarily.

   3. In the Select Nodes to Delete section, click Mark all to select all the nodes for deletion. On clicking Mark all, you should see a cross icon against all the nodes in the Deletion column. These cross icons indicate that the nodes have been selected for deletion.

      
      

   4. In the User Credentials (Override Preferred Credentials) section, retain the default selection, that is, Use Preferred Credentials.

      Note:

      You can optionally override these preferred credentials. For example, if you have added two destination hosts where the users are A and B, then you can choose to override the preferred credentials with different credentials for each of the hosts. Similarly, if the destinations hosts have same credentials, which may be different from the preferred credentials, then you can override the preferred credentials with same credentials for all hosts.

      For example, if you have added two destination hosts where the users are A and B, then you can choose to override the preferred credentials with different credentials for each of the hosts. Similarly, if the destinations hosts have same credentials, which may be different from the preferred credentials, then you can override the preferred credentials with same credentials for all hosts.

      The credentials you specify here are used by the Deployment Procedure to run the provisioning operation. If this environment is secure and has locked accounts, then make sure that:

      • The credentials you specify here have the necessary privileges to switch to the locked account for performing the provisioning operation.

      • The Deployment Procedures has been customized to support locked environments.

      For more information, see Chapter 30, "Customizing Steps to Run as Another User".

      From the Host Credentials list, select Different for each Oracle Home if you want to use different operating system credentials for each Oracle home, or Same for all Oracle Homes if you want to use the same set of credentials for all Oracle homes. Depending on the selection you make, specify the credentials. Ensure that the users belong to the same group (dba/oinstall).

   5. In the Schedule section, schedule the Deployment Procedure to run either immediately or later.

      
      

   6. Click Review.

5. On the Review page, review the details you have provided for deleting Oracle RAC, and click Submit.

Deployment Phases

The following describes the different phases involved in this Deployment Procedure:

Table 9-3 Deployment Phases Involved in Scaling Down an Existing Oracle RAC

Phase	Description
	Delete/Scale Down Oracle RAC Allows you to select an existing Oracle RAC and the nodes you want to delete from it, specify credentials, and schedule the Deployment Procedure to run immediately or later.
	Review Allows you to review the details you have provided for scaling down the Oracle RAC instance.

Prerequisites

Prerequisites for Designers

• Ensure that you meet the prerequisites described in the following sections:

  • Mandatory Infrastructure Requirements for Provisioning and Patching

  • Optional Infrastructure Requirements

• Ensure that oinstall and dba groups are available.

• Ensure that operating system users such as oracle and crsuser are available on all nodes of the cluster. These users must be a part of the relevant operating system groups such as dba and oinstall.

• Ensure that the credentials being used to run this operation along with the group ID are the same on all nodes of the selected cluster.

Prerequisites for Operators

• If you have PAM/LDAP enabled in your environment, then ensure that the target agents are configured with PAM/LDAP. For more information, see My Oracle Support note 422073.1.

• Ensure that you use an operating system user that has the privileges to run the Deployment Procedure, and that can switch to root user and run all commands on the target hosts. For example, commands such as mkdir, ls, and so on.

  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 example, user account A might have the root privileges, but you might use user account B to run the Deployment Procedure. In this case, you can switch from user account B to A by customizing the Deployment Procedure.

  For information about customization, see Chapter 30, "Customizing Steps to Run as Another User".

Procedure

To scale down Oracle RAC by deleting one or more nodes that are part of it, follow these steps:

1. In Grid Control, click the Deployments tab.

2. On the Deployments page, in the Deployment Procedure Manager section, click RAC Provisioning Procedures.

3. On the Deployment Procedure Manager page, in the Procedures subtab, from the table, select Delete/Scale down Oracle Real Application Clusters. Then click Schedule Deployment.

   Enterprise Manager Grid Control displays the Delete/Scale down Oracle Real Application Clusters page.

4. On the Delete/Scale down Oracle Real Application Clusters page, do the following:

   1. In the Select Cluster section, click the torch icon for Select Cluster and select an Oracle Clusterware instance that you want to scale down. Along with the selected Oracle Clusterware, the associated Oracle RAC and ASM instances will also be deleted. The table displays details about the member nodes that are part of the selected Oracle Clusterware.

      
      

      Note:

      When you use the torch icon to search for Oracle Clusterware, if you do not find the Oracle Clusterware that you are looking for, then you can manually provide details about that clusterware and search for it. To do so, from the tip mentioned below the table, click here.

   2. In the Reference Host Options section, from the Cluster Node list, select a node that you want to use as the primary node for all cleanup operations.

      
      

      For Working directory, specify the full path to an existing directory on the selected node that can be used for staging files.

   3. In the Select Nodes to Delete section, select the nodes you want to delete, and click Mark for delete. On clicking Mark for delete, you should see a cross icon against the selected nodes in the Deletion column. These cross icons indicate that the nodes have been selected for deletion.

      If you do not see the nodes that are part of the cluster, then click Add more nodes to add those nodes so that nodes that do not appear as targets in Enterprise Manager Grid Control also are selected for deletion.

      
      

      If you want to deselect a node, click Unmark. If you want to select all nodes at a time, click Mark all, and if you want to deselect all nodes, click Unmark all.

   4. In the User Credentials (Override Preferred Credentials) section, retain the default selection, that is, Use Preferred Credentials.

      Note:

      You can optionally override these preferred credentials. For example, if you have added two destination hosts where the users are A and B, then you can choose to override the preferred credentials with different credentials for each of the hosts. Similarly, if the destinations hosts have same credentials, which may be different from the preferred credentials, then you can override the preferred credentials with same credentials for all hosts.

      The credentials you specify here are used by the Deployment Procedure to run the provisioning operation. If this environment is secure and has locked accounts, then make sure that:

      • The credentials you specify here have the necessary privileges to switch to the locked account for performing the provisioning operation.

      • The Deployment Procedures has been customized to support locked environments.

      For more information, see Chapter 30, "Customizing Steps to Run as Another User".

      From the Host Credentials list, select Different for each Oracle Home if you want to use different operating system credentials for each Oracle home, or Same for all Oracle Homes if you want to use the same set of credentials for all Oracle homes. Depending on the selection you make, specify the credentials. Ensure that the users belong to the same group (dba/oinstall).

   5. In the Schedule section, schedule the Deployment Procedure to run either immediately or later.

      
      

   6. Click Review.

5. On the Review page, review the details you have provided for deleting or scaling down Oracle RAC, and click Submit.