This topic describes how to create an Oracle Pluggable Database (PDB) in a multitenant environment for Oracle 12c RAC and RAC/Restart databases.
In the Naming Information page, populate the following fields, and click Next.
Displays the location in the multitenant environment in which to create this new PDB
|Oracle Cluster||Displays the cluster in which this PDB will reside (RAC only)|
|Oracle Version||Displays the version of the Oracle database|
Displays the name of the CDB in which this PDB will be located
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.
Type the name of the PDB that you want to create.
(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.
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.
In the Provisioning page, populate the following fields based on the mode you selected in Step 5 for creating the PDB, and click Next.
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.|
(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.
In the Configuration page, populate the following fields, and click Next.
Type the Oracle database name.
|Pluggable Database Admin Username||Type the Oracle PDB administrator user name.|
Pluggable Database Admin Password
Type the Oracle PDB administrator password.
Select the method for storing the PDB files.
(Displays when Specify Common Location is selected) Select the diskgroup to store the PDB datafiles.
(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.|
If the ASM Storage page appears, populate the following fields, and click Next.
Displays the predefined diskgroups that you can select in the ASM Diskgroup menu. This lists the names only. No other attributes are listed.
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 clickto 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
ASM Compatibility: Select the ASM compatibility version.
DBMS Compatibility: Select the DBMS compatibility version.
ASM Redundancy: Select the ASM redundancy level:
Click Remove to remove a disk from the list.
Select the predefined diskgroups that corresponds to the disks displayed in Diskgroup Name table of the Predefined Diskgroups section.
In the Custom Scripts Configuration page, select any pre-provisioning or post-provisioning scripts that you want to run as follows, and click Next.
(Optional) Select the scripts that you want to run before this event and click Managing pre-provisioning and post-provisioning script files.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
(Optional) Select the scripts that you want to run after this event and click Managing pre-provisioning and post-provisioning script files.to move them to the Selected list box. See also
In the Job Options page, specify any of the following Job options, and click Next.
(Optional) Click Add Email to add email addresses to the notification list.
Cleanup Agent Logs
(Optional) Select to automatically remove logs that are generated by BDA on the Agent after the job is complete.
If the Change Control page displays, populate the following fields, and click Next.
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.
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
Assign the type of change for the new BMC Remedy ITSM change ticket.
Assign the impact level of this change process for the new BMC Remedy ITSM change ticket.
Assign the urgency level for the new BMC Remedy ITSM change ticket.
Assign the risk level of this change process for the new BMC Remedy ITSM change ticket.
Assign the change class for the new BMC Remedy ITSM change ticket.
Type a summary of the change process.
The Change Control page appears only when change control is configured for your environment. See Configuring change control.
In the Summary page, review the provisioning information.
To make changes, do the following:
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).
To create the database without having first run the pre-verification steps, select Skip Pre-Verification Tests.
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.
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.
If you close your browser, the operation continues. You can return to this page by using the Jobs page.
Click Done and return to the Contents view of this domain.
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.