Creating a single instance Oracle database on Linux and UNIX

This topic describes how to add an Oracle single-instance database by using BMC Database Automation (BDA). This includes creating Container Databases (CDBs) on Oracle versions 12.1.0.1 and later.

For information about creating a clustered Oracle database, see Creating an Oracle cluster.

For information about adding a database to an Oracle cluster, see Adding a database to an Oracle cluster.

Before you begin

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

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 a single-instance Oracle database

  1. From the Management Console, select the node within which you want to create an 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 Linux and UNIX. 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.

    Note

    If you select a template for your database, some fields in subsequent pages for this task would be pre-configured and, depending the template specification, non-editable. This allows administrators to enforce standards across the environment.

  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.
    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, populate 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).

    Field

    Description

    Install EditionDisplays the edition of the installed database.

    Oracle Base

    Enter the wanted Oracle Base path in the file system.

    Oracle Home Name

    Enter the wanted name for this Oracle Home in the inventory.

    Oracle Home Location

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

    DBA Group

    Enter the OS group that should have database administrator privileges inside the Oracle Home.

    Operators Group

    Enter the OS group that should have operator privileges inside the Oracle Home.

    Language

    Select the wanted language for this database.

    Upgrade Opatch

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

    Ignore Oracle OUI Prerequisite Checks

    (Optional) Select to continue with the instance removal if the Oracle prerequisite checks are not met.

  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.

    Field

    Description

    Products to Install

    (Not applicable to 11gR2) 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

    (Not applicable to 11gR2) Select the network components you want to install in this Oracle Home from the available components list.

    Install DBMS Companion

    (Optional, not applicable to 11gR2) Select to install the DBMS Companion which provides additional functionality to the Oracle Home.

    Install Example Disk

    (Optional) Select to install the Example Disk which provides additional functionality to the Oracle Home.

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

    Type

    Field

    Description

    Naming


    Oracle Database Name

    Type the Oracle database name.

    Oracle Database Unique Name(Optional) Type the Oracle database unique name.

    Oracle Domain Name

    (Optional) Type the Oracle domain.

    SID

    Type the System Identification (SID) prefix. This is the part of the SID that is consistent across all of the instances. For example, if you have instances named THEDB1, THEDB2, and THEDB3, THEDB is the SID prefix, and the numbers are the instance numbers.

    Options

    Fix oratab Ownership

    (Optional) Select to modify the oratab ownership for the specified oinstall user and bypasses associated init-verify checks.

    Fix Inventory Permissions

    (Optional) Select to change the permissions on the inventory to 770, so that it is writeable by all users in the install group.

    Note: Selecting this option is recommended when the host contains Oracle Homes owned by different users and to avoid pre-verify errors.

    Fix Permissions

    (Optional) Select to fix permissions on directories and files that require changes for deployment in a multi-user environment (that is, environments where different Oracle Homes on the same node are owned by different users).

    Pin Node

    (Oracle 11gR2 only) Select to pin this node, which means the node is permanently bound to the assigned node number. When you are provisioning a RAC that contains nodes running mixed versions (for example, 10gR2 on 11gR2), nodes must be pinned. For more information, refer to Oracle Metalink ID 1285144.1.

    Listener

    Configure Listener?

    (Optional) Select to configure a listener in this Oracle Home. If you configure a listener and this is the second database you are creating on an Oracle Home, this listener is created off of the existing home. The only time a separate home is created is when the first node of a cluster is created and a node level listener is configured. If a listener is not configured (box is not checked), the database is created with any listeners that already existed.

    Listener Name

    (Required if Configure Listener? is selected) Enter the wanted 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) Enter the number of the wanted TCP/IP port on which the listener should listen.

    Container Database
    (Displays only for Oracle versions 12c and later)
    Container DatabaseSelect to create a CDB.
  9. In the Database Options page, check the boxes for each of the database options you want.
    The following figure shows the Oracle 12.1.02 Database Options page:
    If you select an option from a list, 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.

    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.

    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.

    Maximum Number of Processes per Instance

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

    Maximum 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 block size for this database.

    Memory for SGA

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

    PGA Aggregate Target

    Specify the target aggregate Program Global Area (PGA) size.

    Custom Initialization Parameters

    (Optional) Specify custom initialization parameters beyond those with specific inputs in the create database process. For more information, see Adding custom initialization parameters.

  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, populate the following fields, and click Next.

    Note

    For Oracle 11g, 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.

    Field

    Description

    Background Dump Directory

    (Not applicable to 11g) Type the Background Dump path.

    Core Dump Directory

    (Not applicable to 11g) Type the Core Dump path.

    User Dump Directory

    (Not applicable to 11g) Type the User Dump path.

    Diagnostic Directory

    (11gR2 only) Enter the directory that contains diagnostic output.

    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.

    Database Password File/Device

    (Optional) Specify the full path to the Oracle password file or device.

  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. For details about recommended available space in TEMP, see http://download-east.oracle.com/docs/cd/B19306_01/install.102/b15660/pre_install.htm#sthref95

    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. For more information on adding these directories to a provisioning template, see Adding redo log member directory names.

    Redo Log Member Filename 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.
    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.

    Note

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

  21. (Optional) Click the magnifying glass icon to view log file details.
  22. Check the Results section for the Success message.
    If this procedure was not successful, see Troubleshooting Oracle provisioning problems.
  23. Click Done 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.

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

Comments