Creating a single instance Oracle database on Windows

Before you begin

  • A node is available to be used for provisioning.
  • The node must meet all of the Oracle database prerequisites.

To create a single-instance Oracle database

  1. From the Management Console, select the domain within which you want to create a single-instance Oracle database.
  2. In the Node Configuration section, select Provision > Add Oracle Database.
  3. In the Database Naming Information page, populate the following fields, and click Next.

    Field

    Description

    Domain

    Displays the location in which to create this new database.

    Host

    Displays the host on which to create this new database.

    Oracle Version

    Select the version of Oracle to be installed.

    Template

    (Optional) Select a BMC Database Automation template for this operation. See Managing templates for Oracle on Windows. If you select a template, click Skip Ahead to advance directly to the next step that requires input. An informational message appears on these steps, in green type, listing the fields that require entries before advancing to the next step.

    Display Name

    Type the name of the new BMC Database Automation database you want to create.

  4. If the Custom Fields page appears, enter values for the custom fields and click Next.

    Note

    This page appears only when in the BMC Database Automation XML template, either custom fields are defined used for this provisioning activity or NEW IN 8.9.02any custom fields are defined for the database options (present on the Database Options page in this wizard). If you have defined custom field for a database option, value of that database option on the Database Options page will be derived from this custom field. For more information, 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.
  6. In the Oracle Home Information page, populate the following fields, and click Next.

    Field

    Description

    Oracle Base

    Type the Oracle Base path in the file system.

    Oracle Home Name

    (Optional) Type the name for this Oracle Home in the inventory.

    Oracle Home Location

    Type the Oracle Home path in the file system. In the directory tree, this path must be below (or the same as) the specified Oracle Base.

    Language

    Select the language for this database.

    Upload Oracle Media

    (Optional) Select to upload Oracle media to the Agent as part of this job.

    Cleanup Oracle Media When Completed

    (Optional) Select to remove Oracle media from the Agent after provisioning.

    Upgrade Opatch

    (Optional) Select to upgrade the version of OPatch that is installed by default to the current version on the Manager.

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

    Field

    Description

    Products to Install

    Select the components you want to install in this Oracle Home from the available components list.

    Enterprise Options to Install

    Select the Oracle Enterprise Edition components you want to install in this Oracle Home from the available components list.

    Network Options to Install

    Select the network components you want to install in this Oracle Home from the available components list.

    Install DBMS Companion

    (Optional) Select to install the DBMS Companion which provides additional functionality to the Oracle Home.

  8. In the Database Options page, check the boxes for each of the database options you want.
    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.
  9. In the Database Configuration page, populate the following fields, and click Next.

    Type

    Field

    Description

    Naming

    Oracle Database Name

    Type the Oracle database name.

    Oracle Domain Name

    (Optional) Type the Oracle domain.

    SID

    Type the SID for the new Oracle database instance.

    Options

    Oracle Installation Domain

    Type the domain of the OS user that should own this Oracle installation.

    Oracle Installation User

    Type the OS user that should own this Oracle installation.

    Oracle Installation Password

    Type the password of the OS user that should own this Oracle installation.

    Listener

    Configure Listener?

    (Optional) Select to configure a listener in this Oracle Home.

    Listener Name

    (Required if Configure Listener? is selected) Type the name of the listener. The host name is appended to the name you enter. For example, if the name is Listener and the host name is host1, the listener that is created is Listener_host1.

    Listener Port

    (Required if Configure Listener? is selected) Type the number of the wanted TCP/IP port on which the listener should listen.

    Note

    BMC Database Automation allows you to define a separate inventory for each Oracle Home that is created. If you create a global inventory pointer, BMC Database Automation verifies that the inventory information matches.

  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.

    Field

    Description

    Pre-Provisioning Script Directory

    (Optional) Select the scripts that you want to run before this event and click to move them to the Selected list box. The scripts in Selected are run in the order listed. Use Move Up and Move Down to re-order the scripts when necessary. See also Managing pre-provisioning and post-provisioning script files.

    Post-Provisioning Script Directory

    (Optional) Select the scripts that you want to run after this event and click to move them to the Selected list box. See also Managing pre-provisioning and post-provisioning script files.

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

    Field

    Description

    Character Set

    Type the character set for this database.

    National Character Set

    Type the national character set for this database.

    SYS Password

    Define the SYS user password.

    Confirm SYS Password

    Confirm the SYS user password.

    SYSTEM Password

    Define the SYSTEM user password.

    Confirm SYSTEM Password

    Confirm the SYSTEM user password.

    Ignore Oracle OUI Prerequisite Checks

    (Optional) Selecting does the following:

    • Uses the -ignoreSysPrereqs flag (for 10gR2) or the -ignorePrereq flag (for 11gR2) during Oracle provisioning operations, thus ignoring any failed Oracle prerequisite checks.

    Remote Login Password File

    Select the path for the orapw file.

    Service Name

    (Optional) Define a service for this database.

    Compatibility Level

    (Optional) Specify a compatibility level for this database.

    Max Number of Processes per Instance

    Specify the maximum number of processes for each instance for this database.

    Max Number of Open Cursors per Instance

    Specify the maximum number of open cursors for each instance for this database.

    File Multiblock Read Count

    Specify the file multiblock read count database parameter.

    Job Queue Processes

    Specify the number of job queue processes for each instance.

    Database Block Size

    Select the wanted block size for this database.

    Percentage of Memory for SGA

    (Optional) Specify the percentage or size of memory to be used for the SGA for this database.

    PGA Aggregate Target

    Specify the target aggregate PGA size.

    Custom Initialization Parameters

    (Optional) Specify custom initialization parameters beyond those with specific inputs in the create database process.

  12. In the Control Files page, populate the following fields, and click Next.

    Field

    Description

    Number of Control Files

    Specify the number of control files to create.

    Control Filepaths

    Define where the control files should be stored.

    Reuse Existing Control Files

    (Optional) Select to overwrite the control files if they already exist.

    Maximum Number of Instances

    Define the maximum number of instances in this database.

    Maximum Number of Datafiles

    Define the maximum number of data files in this database.

    Maximum Number of Logfiles

    Define the maximum number of redo log groups that can exist in this database.

    Maximum Number of Log Members

    Define the maximum number of redo log members for each group.

    Maximum Number of Log Histories

    Define the maximum number of redo log files that can be recorded in the log history of the control file.

  13. In the Directories page, provision the following fields, and click Next.

    Note

    For Oracle 11g, the Background, Core and User Dump directories are not shown in the Directories page. 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.

    Field

    Description

    Background Dump Directory

    Type the Background Dump path.

    Core Dump Directory

    Type the Core Dump path.

    User Dump Directory

    Type the User Dump path.

    Audit File Destination

    Type the Audit File destination path.

    Recovery File Destination

    Type the FRA destination path.

    Recovery File Maximum Size

    Specify the maximum FRA size.

    SPFile

    Specify the path to the SPFile.

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

    Tablespace

    Description

    SYSAUX

    Specify the following: the initial size; whether the datafile should be autoextended; maximum size and incremental size of the SYSAUX tablespace; and whether the file should be overwritten if it exists.

    SYSTEM

    Specify the following: the initial size; whether the datafile should be autoextended; maximum size and incremental size of the SYSTEM tablespace; and whether the file should be overwritten if it exists.

    TEMP

    Specify the following: the initial size; whether the datafile should be autoextended; maximum size and incremental size of the TEMP tablespace; and whether the file should be overwritten if it exists.

    Note: If there is not enough space in TEMP, the Oracle installation can fail. 

    UNDOTBS1

    Specify the following: the initial size; whether the datafile should be autoextended; maximum size and incremental size of the UNDOTBS1 tablespace; and whether the file should be overwritten if it exists.

    USERS

    Specify the following: the initial size; whether the datafile should be autoextended; maximum size and incremental size of the USERS tablespace; and whether the file should be overwritten if it exists.

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

    Field

    Description

    Number of Redo Log Groups

    Type the number of redo log groups wanted.

    Number of Redo Log Members per Group

    Type the number of redo log members for each group wanted.

    Redo Log Member Directories

    Type the paths in which to store the redo logs.

    Redo Log Member file name Template

    Type the template for the redo log file names.

    Redo Log Filesize

    Type the size of the redo logs to be created.

    Reuse Redo Logs

    (Optional) Select to overwrite the existing redo logs with the new logs.

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

    Type

    Option

    Description

    Notification Emails

    Email List

    (Optional) Click Add Email to add email addresses to the notification list.

    Job Administration

    Cleanup Agent Logs

    (Optional) Select to automatically remove logs that are generated by BMC Database Automation on the Agent after the Job is complete.

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

    Section

    Field

    Description

    Bypass Change Control

    (Optional) Select to bypass using BMC Remedy ITSM to control the change process. Selecting this option removes the rest of the fields from this page.

    Change Control Options

    Select to determine whether to open a new BMC Remedy ITSM change ticket, or to use an existing BMC Remedy ITSM change ticket to control the change process.

    • Selecting Use Existing Change Ticket displays the fields in the Use Existing Change Ticket section on this page.
    • Selecting Create New Change Ticket displays the fields in the Create New Change Ticket section on this page.

    Use Existing Change Ticket

    ITSM Change ID

    Specify the BMC Remedy ITSM change ticket number to associate with this change process.

    ITSM Task ID

    Specify the BMC Remedy ITSM task ID number to associate with this change process.

    Create New Change Ticket

    Change Type

    Assign the type of change for the new BMC Remedy ITSM change ticket.

    Change Impact

    Assign the impact level of this change process for the new BMC Remedy ITSM change ticket.

    Change Urgency

    Assign the urgency level for the new BMC Remedy ITSM change ticket.

    Change Risk-Level

    Assign the risk level of this change process for the new BMC Remedy ITSM change ticket.

    Change Class

    Assign the change class for the new BMC Remedy ITSM change ticket.

    Change Summary

    Type a summary of the change process.

    Note

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

  18. 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.
  19. 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.

  20. Click Create Oracle Database.
  21. If you disabled the Automatically Continue If All Tests Succeed option, you are prompted to click Continue after the pre-verification steps are done.
    After verification, the activities are performed and the results appear.
  22. (Optional) Click the magnifying glass icon to view log file details.
  23. Check the Results section for the Success message.
    If this procedure was not successful, see Troubleshooting Oracle provisioning problems.

    Note

    You can always return to a Job's Information page by using the Jobs section of the Management Console. See Monitoring jobs and viewing job history.

Was this page helpful? Yes No Submitting... Thank you

Comments