Adding a database to an Oracle cluster

Before you begin

• A running Oracle Cluster Ready Services (CRS) cluster currently managed by BMC Database Automation (BDA) must be available.
• The node must meet all of the Oracle database prerequisites.

To add a database to an Oracle cluster

1. From the Management Console, select the cluster within which you want to create an Oracle database.
2. Select Provision > Add Oracle Database.

3. In the Database Naming Information page, populate the following fields, and click Next.
4. If the Custom Fields page appears, enter the password, and click Next.
    The Custom Fields page appears only when custom fields are defined in the BDA XML template used for this provisioning activity. See Adding-custom-fields-to-a-template.
5. In the Oracle Home Selection page, select an Oracle Home from the Use Existing Home list box or create a new one, and click Next.
    The Oracle Home Selection page appears only when an Oracle Home is not defined for the version of the database being provisioned.
    If you selected Create New Home, proceed to the next step.
    If you selected an existing home, proceed to step 8.

6. In the Oracle Home Information page, provision the following fields, and click Next.

   Note

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

   • For a Restart-enabled database (any version), there are no restrictions (Oracle home can be under Oracle base).
   • For a standalone database (any version), there are no restrictions (Oracle home can be under Oracle base).
   • For an Oracle 11.2.0.1 Restart-enabled cluster, there are no restrictions (Oracle home can be under Oracle base).
   • For Oracle RAC One Node, 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.

7. In the Oracle Home Components 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 table.

8. In the Configuration page, populate the following fields, and click Next.
9. In the Database Options page, check the boxes for each of the database options you want.
    The following figure shows the Oracle 12.2 Database Options page:
   
   
   If you select an option with a list box, select a tablespace from the list box, and click Next.
    These options require a tablespace to place the data into.

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

11. In the Database Parameters page, populate the following fields, and click Next.

    Note

    When Use ASM is selected, the following fields are not applicable and do not appear in subsequent wizard steps: Number of Control Files, Control Filepaths, Reuse Existing Control Files, Recovery File Destination, SPFile, SYSAUX Filepath, SYSTEM Filepath, TEMP Filepath, UNDOTBS1 Filepath, USERS Filepath, Number of Redo Log Members for each Group, and Redo Log Member file name.

12. If you selected Use ASM, go to the next step.
     If you did not enable the use of ASM, go to step 15.

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

14. In the Control Files page, provision the following fields, and click Next.

15. In the Directories page, populate the following fields, and click Next.

    Note

    For Oracle 11g and later, the Background, Core and User Dump directories are not shown in the Directories step. Instead, the Diagnostic Directory field is provided. Use this field to enter the path and directory of the Automatic Diagnostic Repository (ADR) Home. The ADR contains the diagnostics (trace, core, and incident files; alert logs) for each database instance.

16. In the Tablespaces page, configure the various tablespace types as follows, and click Next.

17. In the Redo Logs page, populate the following fields, and click Next.

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

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

    Note

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

20. In the Summary page, review the provisioning information.
    To make changes, do the following:
    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.
21. Specify your verification preferences.
     For additional information, see Understanding-pre-verification-tests.
    • To continue with database creation after the pre-verification tests have been successfully run 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 verification and advances directly to the actual provisioning activity.

22. Click Create Oracle Database.
     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 database creation process begins and a progress page appears.
    A pop-up window appears upon successful creation of the database.

    Note

    If you close your browser, the operation continues. You can return to this page by using the Jobs page.

23. Click the magnifying glass icon to view log file details.
24. If this procedure was not successful, see Troubleshooting.

25. Click Done to complete this step and return to the Contents view of this domain.

    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.