Space banner This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Creating an Oracle cluster

This topic describes how to provision an Oracle cluster for Real Applications Cluster (RAC) databases by using BMC Database Automation (BDA).

Before you begin

Ensure that the following prerequisites are met:

  • A node that meets all of the Oracle Cluster Ready Services (CRS) prerequisites is available for provisioning.
  • From within the Management Console hierarchy, you can access the domain in which you want to create a RAC database.

  • If you want to perform inline patching and apply the patch before CRS is configured (for example, in case of Oracle One-Off patches), edit the patch package and set the following options:

    • Install Method as Apply
    • Command Line Options as applicable for the OPatch Apply method

    Note

    OPatch Auto is not applicable for this type of patching.

  • If you want to perform inline patching and apply the patch after CRS is configured, edit the patch package and set the following options:
    • Install Method as Auto or Apply
    • Command Line Options as applicable for the OPatch Auto or Apply method

Tip

To enable a global option in BDA that allows the Oinstall user name value to begin with a number, you must set can_oinstall_user_start_with_number to true in /app/clarity/dmanager/etc/d2500_config or contact Customer Support for assistance.

To create an Oracle cluster

  1. From the Management Console, navigate to the node within which you want to create an Oracle cluster and then select the domain name.
  2. Select Provision > Create Oracle Grid Infrastructure.

  3. In the General Information page, populate the following fields, and click Next.

    The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.

  4. If the Custom Fields page appears, enter values for the custom fields, and click Next.
    This page appears only when custom fields are defined in the BDA XML template that is used for this provisioning activity. See Adding-custom-fields-to-a-template.

  5. In the Setup page, populate the following fields, and click Next.

    The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.

  6. In the Configuration page, populate the following fields, and click Next.

    Note

    For RAC databases, the inventory directory that is used for the cluster home is also used for any DBMS homes that are created.

    The following rules apply for provisioning Oracle Base and Oracle Home:

    • For an Oracle 11.2.0.1 Restart-enabled cluster, there are no restrictions (Oracle Home can be under Oracle Base).
    • For Oracle 11.2.0.2 and 11.2.0.3 Restart-enabled clusters, Oracle Home cannot be under Oracle Base.

    The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.

  7. In the Listener/ASM Configuration page, populate the following fields, and click Next.

    Note

    The fields that appear vary depending on the version of Oracle installed on the node. Differences are noted in the following table.

    The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.

  8. If the ASM Diskgroup page appears, populate the following fields, and click Next.

    Note

    This page does not appear for provisioning of RAC databases on NFS.

    The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.

  9. If the GIMR Diskgroup page appears, populate the following fields, and click Next.

    Note

    This page does not appear for provisioning of RAC databases on NFS.

    The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.

  10. In the Oracle Home Components page, populate the following fields, and click Next.

    Note

    If you chose to create a listener or ASM instance in step 5 of this procedure, a DBMS Oracle Home is also created. This option is reflected in the Oracle Home Components page.

    The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.

  11. (Applicable for version 8.9.01 and later) In the Disk page, populate the following fields, and click Next. The Disk page appears only for provisioning of RAC databases on NFS.

    Note

    The Disk page appears depending on the selection of the Configure ASM check box in the Setup page.

    The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.

  12. In the Devices page, populate the following fields, and click Next. This Devices page appears only for provisioning of RAC databases on ASM. 

    The Devices page appears only for 11gR1 and 11gR2 databases.

    The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.

  13. In the Networking page, populate the following fields, and click Next.

    Note

    The fields that appear vary depending on the version of Oracle that is installed on the node. Differences are noted in the table.

    The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.

  14. In the Custom Scripts Configuration page, select any pre-provisioning or post-provisioning scripts that you want to run as follows, and click Next.

    The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.

  15. In the Job Options page, specify any of the following Job options, and click Next.

    The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.

  16. If the Change Control page displays, populate the following fields, and click Next.

    The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.

    Note

    The Change Control page appears only when change control is configured for your environment. See Configuring-change-control.

  17. In the Summary page, review the provisioning information.
    To make changes, do the following actions:
    1. Click Go to to return to the provisioning step that you want to edit.
    2. Make your changes.
    3. Click Save and Review to return to the Summary page.
  18. Specify your verification preferences.
    For additional information, see Understanding-pre-verification-tests.
    • To continue with database creation after the pre-verification tests have been run successfully without manual intervention, select Automatically Continue If All Tests Succeed.

    • To create the database without having first run the pre-verification steps, select Skip Pre-Verification Tests.

      Note

      The Skip Pre-Verification Tests option should only be used when you are certain all tests can succeed. The option skips the verification process and advances directly to the actual provisioning activity.

  19. Click Create Cluster.
    If you disabled the Automatically Continue If All Tests Succeed and Skip Pre-Verification Tests options, you are prompted to click Continue after the pre-verification steps are done.
    The cluster creation process begins and a progress page appears.

  20. If this procedure was not successful, see Troubleshooting.

    Note

    Detailed current and historical information about this action can be viewed in the Jobs section of the Management Console. See Monitoring-jobs-and-viewing-job-history.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*