Page tree
Skip to end of metadata
Go to start of metadata

This topic describes how to create an Oracle Pluggable Database (PDB) in a multitenant environment for Oracle 12c RAC and RAC/Restart databases.

Before you begin

  • A Container Database (CDB) must be available for provisioning.
  • The node must meet all of the Oracle database prerequisites.
  • You can also create a PDB using the bdacli command line tool. For more information, see Provisioning operations and type Oracle Pluggable Database in the Type field to filter the table.

To create an Oracle Pluggable Database

  1. From the Management Console, navigate to the CDB within which you want to create a PDB.
  2. In the Database Configuration page, select Provision > Add Pluggable Database.
  3. In the Naming Information page, populate the following fields, and click Next.

    Field

    Description

    Domain

    Displays the location in the multitenant environment in which to create this new PDB

    Oracle ClusterDisplays the cluster in which this PDB will reside (RAC only)
    Oracle VersionDisplays the version of the Oracle database

    Container Database

    Displays the name of the CDB in which this PDB will be located

    Host

    RAC: Select the host on which to initiate the job.

    Note: All CDB instances are affected during the job.

    Restart: Displays the host on which the job will be initiated.

    Display Name

    Type the name of the PDB that you want to create.

    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.

    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. In the Create Mode page, select the method you want to use to create the PDB in the Create Pluggable Database From: menu and click Next.
    You can choose from the following options:
    • Seed mode uses a special template from Oracle when the CDB is created, which then enables you to create new PDBs within the CDB.
      If a CDB already has 252 PDBs plugged into it, then unplugging one of those enables another PDB to be plugged into that CDB.
    • Metadata mode uses Oracle metadata that was created by a previous unplugging operation and stored in an .xml file.
      The recommended location for this file is /oradata/<your initials>export.xml. Make sure the oracle user has write permissions to the selected directory.
  5. In the Provisioning page, populate the following fields based on the mode you selected in Step 5 for creating the PDB, and click Next.

    Field

    Description

    Number Of Databases To Create

    (For Seed mode only) Type the number of PDBs to create. If you enter a number greater than 1, there will be a sequential number appended to the name of each PDB that is created.

    Metadata Filename

    (For Metadata only) Type the name and location of the .xml file that stores the Oracle metadata from a previous unplugging operation (likely /oradata/<your initials>export.xml.) Make sure the oracle user has write permissions to the selected directory.

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

    Field

    Description

    Database Name

    Type the Oracle database name.

    Pluggable Database Admin UsernameType the Oracle PDB administrator user name.

    Pluggable Database Admin Password

    Type the Oracle PDB administrator password.

    Storage Options

    Select the method for storing the PDB files.

    • Selecting Use Oracle Managed Files specifies that files managed by Oracle are used.
    • Selecting Specify Common Location specifies that you will use a specified file location and name.
    Storage Type

    (Displays when Specify Common Location is selected) Select the diskgroup to store the PDB datafiles.

    • Selecting Automatic Storage Management (ASM) specifies that Oracle ASM be used. When selected, the ASM Storage page appears in the next step of the wizard (see Step 7).
    • Selecting Shared File System specifies that you use any Oracle shared file system.
    Datafile Location

    (Displays when Shared File System is selected as the storage type)

    Type a path where the PDB datafile is located.

    Create Default User Tablespace(Optional) Select to create the default user tablespace.
  7. If the ASM Storage page appears, populate the following fields, and click Next.

    Field

    Description

    Predefined Diskgroups

    Displays the predefined diskgroups that you can select in the ASM Diskgroup menu. This lists the names only. No other attributes are listed.

    Additional Diskgroups

    Select the disks that you want to use to contain the data files and click Add to display the Define Diskgroup page, populate the following fields, and click OK.

    Diskgroup Name: Type the name of the diskgroup. This will be the name that displays in the Diskgroup Name list and the ASM Disgroup field on the ASM Storage page.

    Available Disks: Select the disks that you want to use to contain the data files and click to move them to the Selected list box.

    AU Size: Enter the AU size of the ASM diskgroup. Possible Values: 1, 2, 4, 8, 16, 32, 64
    Note: This field appears when the installation type is Oracle Restart.

    ASM Compatibility: Select the ASM compatibility version.

    DBMS Compatibility: Select the DBMS compatibility version.

    ASM Redundancy: Select the ASM redundancy level:

    • EXTERNAL: diskgroup must have a minimum of one disk
    • NORMAL: diskgroup must have a minimum of two available disks
    • HIGH: diskgroup must have a minimum of three available disks

    Click Remove to remove a disk from the list.

    ASM Diskgroup

    Select the predefined diskgroups that corresponds to the disks displayed in Diskgroup Name table of the Predefined Diskgroups section.

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

    Section

    Description

    Pre-Provisioning Scripts

    (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 Scripts

    (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.

  9. 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 BDA on the Agent after the job is complete.

  10. 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.

  11. 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.

      If you configured ASM in Step 6, the ASM Storage section displays (RAC only).

    2. Make your changes.
    3. Click Save and Review to return to the Summary page.
  12. 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.

  13. Click Create Pluggable 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.

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