Provisioning Pluggable Databases

24 Provisioning Pluggable Databases

This chapter describes the process involved in provisioning pluggable databases. It contains the following sections:

Getting Started

An Oracle Database can contain a portable collection of schemas, schema objects, and nonschema objects, that appear to an Oracle Net client as a separate database. This self-contained collection is called a pluggable database (PDB). A multi-tenant container database (CDB) is a database that includes one or more PDBs. Oracle Database 12c Release 1 (12.1) and later versions allow you to create many PDBs within a single CDB.

Table 24-1 Provisioning Pluggable Databases

Step	Task	Role
1	Follow the steps in the Getting Started section to enable DBaaS.	See Getting Started
2	Create one or more resource providers.	See Creating Resource Providers
4	Configure the request settings.	See Configuring Request Settings
5	Define quotas for each self service user.	See Defining Quotas
6	Create a database provisioning profile. This step is optional and is not required if you are creating an empty pluggable database.	See Creating a Database Provisioning Profile Using Export Schema Objects
7	Create a service template. A service template can contain: Empty Pluggable Database: In this case, the service template is created with an empty schema. Pluggable Database from a Profile: In this case, you can import schemas from a database provisioning profile. You can select this option for applications with data such as eBusiness applications.	See Creating a Service Template for PDB Based on Profile
8	Configure the Chargeback Service.	See Configuring Chargeback
9	While deploying a database, select the service template that you have created.	See Requesting a Pluggable Database

Creating Resource Providers

You must create one or more resource providers which include:

PaaS Infrastructure Zones: See Creating a PaaS Infrastructure Zone
Database Pool: See Creating a Database Pool for PDB as a Service

Hybrid PDB as a Service

Before provisioning PDB as a Service on an OCI Database System (via the PDB on OCI DBCS New Service template) you must first create a separate pool and separate zone for the PDB service.

Creating a Database Pool for PDB as a Service

A Pluggable Database (PDB) is portable set of schemas, schema objects, and related structures that appears logically to an application as a separate database. This self-contained collection is called a pluggable database (PDB). Every PDB is owned by a SYS user.

A container is a collection of schemas, objects, and related structures in a container database (CDB) that appears logically to an application as a separate database. A container database (CDB) is an Oracle database that includes zero, one, or many user-created PDBs.

A database pool for PDB as a Service must contain a set of container databases. The container databases must meet the following guidelines:

All CDBs in a database pool must be of the same version and platform.
All CDBs in a database pool must either be single instance databases or RAC databases. Mix and match of database types is not supported.

To create a database pool for PDB as a service, follow these steps:

Log into Enterprise Manager as a user with the EM_SSA_ADMINISTRATOR role.
From the Enterprise menu, select Cloud, then select Cloud Home. From the Oracle Cloud menu, select Setup, then select Getting Started. Click the Setup link next to the Database service family, select Pluggable Database from the drop down link, click on the Pluggable Database Pool link and then click Create.

Figure 24-1 Create Database Pool: Setup Page (PDB)
Enter a name and description for the database pool.
In the Credentials region, specify the credentials that will be used for performing database operations. Specify the following credentials:
- Host: Required for performing remote host operations.
- Grid Infrastructure: Required to register a database service with grid infrastructure credentials.
- Database: Required for creating the pluggable database.
- Container Database Wallet Password: If the PDB is to be encrypted, you must specify the password required to open the wallet from the keystore.
Specify the following details:
- PaaS Infrastructure Zone: Select a PaaS Infrastructure Zone in which the container databases are present. The PDBs will be created on the databases selected for the pool. For details on creating container databases, see Provision a Container Database for PDB as a Service.
- Target Type: Specify the configuration of the target database on which the PDB is being deployed. This can be Single Instance or Cluster Database (RAC).
- Platform and Version: Specify the platform and version of the database being deployed.
Click Add and select one or more container databases to be added to the pool. All databases you select must be present in the same PaaS Infrastructure Zone.

Note:

You can search for database groups that meet your requirements by specifying a search string in the Groups field.
Click Next. The Create New Pool: Policies page appears.
Figure 24-2 Create Database Pool: Policies (PDB)

Specify the placement policy constraints to set maximum ceilings for resource utilization on each database. Placement policy constraints for each database can be defined by services or workloads as follows:
- Pluggable Database: Select the Pluggable Database checkbox and specify the Maximum Number of Pluggable Databases that can be created inside each CDB.
- Workloads Associated with Service Requests: The amount of resources (such as CPU and memory) to manage the workload can be specified here. Specify the workload that is to be enforced for the pluggable database.
  - Maximum CPU Allocation: Specify the maximum CPU that can be allocated to each database.
  - Maximum Memory Allocation: Specify the maximum memory that can be allocated for each database.
  For example: If a container database is caged to 2 CPUs with SGA of 4GB, and you specify the Maximum CPU Allocation and Maximum Memory Allocation as 80%:
  - the maximum CPU limit for each pluggable database is 1.6
  - the maximum SGA / memory limit for each pluggable database is 3.2
If you have chosen to set the placement constraints by Workloads Associated with Service Requests, you can choose to enable the resource manager by selecting the Enable Resource Manager for CPU check box. You can use the resource manager to manage the CPU resource and create Consumer Groups. A Consumer Group is used to ensure that the service gets the requested CPU cycles on a fully loaded system.
Click Submit to create a database pool for PDB as a service. The newly created database pool will appear in the Database Cloud Self Service Portal Setup: Database Pools page.

Creating a Database Provisioning Profile Using Export Schema Objects

To create a database provisioning profile, follow these steps:

You can access the Database Provisioning page using either of the following ways:
- From the Enterprise menu, select Cloud, and then select Cloud Home. On the Cloud home page, click Oracle Cloud, select Setup, and then select Data Sources. On the Database: Data Sources page, in the Data Profiles tab, click Create.
- From the Enterprise menu, select Provisioning and Patching, and then select Database Provisioning. On the Database Provisioning page, in the Profiles section, click Create.
- From the database target home page, click Oracle Database, select Provisioning, and then select Create Provisioning Profile.
On the Reference Target page, click the search icon to select a target.
In the Search and Select:Targets display box, select the database you want to create a profile for, and then, click Select.
On the Reference Target page, select the following:
- Data Content
- Structure and Data to include physical and structural files from the database or Structure Only to include only the structural files in the template.
- Export Schema Objects
In the Credentials section, select the database. In the Credentials column, you can select Named Credentials and then select a credential name from the Credential Name column (or) select Preferred Credentials. Click Next.
On the Content Options page, do the following:
- Select the schema you want to include in the profile by clicking on a schema in the Available Schema list and moving it to the Selected Schema list.
  
  Note:
  
  When one or more schemas are selected, the database checks if the dependent schemas are also selected for export. If the dependent schemas are not exported, you will receive a warning. You can choose to go ahead with the selected schemas, or to include the schemas which were not initially selected.
  
  The same warning is also displayed when you select a profile that does not have the dependent schemas exported.
  
  Note:
  
  The Available Schemas section displays only the user created schemas that has data content in it. All the empty schemas are filtered out by default.
  
  Note:
  
  System schemas such as SYS, SYSTEM, and DBSNMP will not be exported.
  
  The user schemas which do not have their own tablespace are not shown in left side of the shuttle.
- In the Degree of Parallelism section, enter the number of threads required to perform the export operation.
  
  Note:
  
  Increasing the number of threads helps reduce the time required to create the profile at the cost of using system resources.
- In the Directory Locations section, click on Add. In the Select Directory window, select a directory object listed to perform the export operation, and then click Select.
  
  Note:
  
  The number of export threads determines the number of parallel export processes that will run in parallel during export.
  
  Hence, the dump file names should contain %U, to ensure the file names are auto generated with the running count to facilitate parallel operation along with the maximum size for the dump file. For example, 5GB. This means that the file rotation will start after 5GB limit is reached.
  
  Note:
  
  Ensure that the directory location is accessible. The directory object that you select must refer to a location that is accessible across all the nodes. You can also create a directory object on ASM. However, it is not supported on ASM.
  
  In the Log subsection, click on the search icon. In the Select Directory window, select the directory object you require to perform the export operation, and then click Select.
  
  In the Log subsection, enter the file name, and then click on Next.
  
  Note:
  
  You can make use of degree of parallelism with dump file names. The default value of dump files contain %U which creates a running count when degree of parallelism is greater than 1.
  
  Also, this enables you to add multiple dump directories to distribute the storage if required.
On the Create Database Provisioning Profile: Page, in the Profile Information section, do the following:
- Specify or select a profile location in the software library where the database profile will be created.
- Specify a unique profile name.
```
For example:
Export Schema Objects Provisioning Profile for HR database
```
- Add a description for the profile.
- Verify the profile version and the vendor.
- Add any additional notes such as host name, database, data content, data content mode, and the like.
In the Schedule section, you can choose to start the profile creation immediately, or you can schedule it for a later time. You can also choose to repeat the creation of the provisioning profile, and set a repeat time.
Specify or select a working directory. Click Next.
On the Review page, ensure that the selections you have made in the previous pages are correctly displayed and click Submit. Otherwise, click Back repeatedly till you reach the page where you want to make changes. Click Cancel to abort the provisioning profile creation.

Once you have submitted the provisioning profile creation job, manually refresh the page if View Data has been set to Real Time: Manual Refresh. Else, set View Data to reload after a specific period of time, and then select an execution step from the Procedure Steps tree on the left pane to view the details.

To view the submitted jobs, select the Procedure Activity link in the Data Profiles tab.

Creation of SSA User Data Profile for Pluggable Database

An Enterprise Management Self Service Application administrator can enable a Self Service Application (SSA) user to create a data profile.

To enable the SSA user to create a data profile, the option Allow SSA user to create a Data Profile must be selected in the Pluggable Database Service Template. The SSA Administrator must also provide a payload location for storing the backup file(s). The SSA user can now create a data profile for preserving a backup of a pluggable database as part of Delete operation.

Figure 24-3 Create Data Profile

If the Allow SSA user to create a Data Profile option is configured in the Pluggable Database Service Template, the option Preserve a backup of this instance is enabled for SSA User.

The SSA user can preserve a backup of any PDB instance created using this service template for an Instance Delete operation. SSA User can also customize the name and description of the profile created for preserving the backup, and PDB backup is taken on the location configured in the service template. The EM default software library stores the metadata for the profile in the following location: Database Configuration/ <PDB version>/<OSName >/ Database Templates .

Figure 24-4 Preserve a Backup

The following users are granted the view privileges to the software library profile:

SSA User initiating the creation of data profile operation
Any EM Administrator with EM_CLOUD_ADMINISTRATOR role
Any EM Administrator with EM_SSA_ADMINISTRATOR role
Any EM Administrator with a role configured in the service template associated with this instance

Configuring Request Settings

You can configure the request settings by specifying when a request can be made, its duration, and so on. See Configuring Request Settings

Defining Quotas

After configuring the request settings, you must define quotas for each self service user. See Setting Up Quotas

Creating a Service Template for PDB Based on Profile

One or more pluggable databases can be created based on the service template definition. To create a service template for PDB as a service, follow these steps:

Log into Enterprise Manager as a user with the EM_SSA_ADMINISTRATOR role.
From the Enterprise menu, select Cloud, then select Cloud Home. The Cloud Home page appears. From the Oracle Cloud menu, select Setup, then select Getting Started.
Click the Setup link next to the Databases option in the left panel. Select Pluggable Database from the drop down menu.
Click the Service Templates link. The Service Templates page appears. Click Create. The Create Service Template: General page appears.

Figure 24-5 Create Service Template: General (PDB)
Enter a name and description for the service template. The description must be unique and provide information on the type of service template being created.
In the Pluggable Database region, select the Create Pluggable Databases from Profile option and select a database provisioning profile that is to be used to create the pluggable database. Click the Search icon next to the Profile field and select an export schema objects profile from the list. If a profile does not exist, you must create one. See Creating a Database Provisioning Profile Using Export Schema Objects for details.
- Note:
  
  You can also create a PDB from an uplugged PDB. To do so, follow these steps:
  - Unplug the PDB from the container database and specify the location in the Software Library which the PDB template (contains data files and the metadata XML file) is to be stored.
  - In the Service Template Creation wizard, specify the PDB template location in the Shared Location field. The PDB is created with the specified data files.
In the Pools and Zones region, click Add to select a PaaS Infrastructure Zone into which the pluggable database instance is to be provisioned. Click Assign Pool to add a Database Pool (for Pluggable Databases) for the zone.

Note:

A database pool (for PDBs) must be present in the PaaS Infrastructure Zone that you select here.
After the database pool has been assigned, the container database into which the pluggable database is to be added is displayed in the Reference Container Database field. All the validations for the service template will be performed against this database.
If you have selected Create Pluggable Databases from Profile in the Pluggable Database region, in the Shared Location field, specify the Path or the shared location on all hosts in which the schema dumps are present. The Dump File Location must be accessible by all the databases.
In the Placement region, the pluggable database can be provisioned on the container database using one of the following options:
- Selected by placement algorithm: If this option is selected, the container database will be selected based on the placement algorithm.
- Selected by user during request: If this option is selected, while requesting a new PDB, the self service user can select the container database on which the PDB is to be provisioned.
In the Identification region, in the Pluggable Database Prefix Name field, specify the prefix that is to be used to generate a unique Pluggable Database name at the time of database creation. The prefix helps to identify the PDBs that are created using this service template.
Click Next. The Create New Service Template: Configurations page appears.
Figure 24-6 Create Service Template: Configurations (PDB)

Specify the following details:
- Workload Size: Workload represents the total CPU, memory, number of sessions, and storage requirements for each service. You can define workload sizes such as small, medium, and large. The workload sizes defined here will be the default workload sizes available to the users with the EM_SSA_USER role.
  
  Click Create and in the Create Workload window, enter the name, CPU, Memory, and Storage limit for each service.
- Pluggable Database Administrator Privileges: You can assign privileges to the Pluggable Database Administrator by:
  - From Existing Database Roles: If you select this option, click Add Roles to add one or more existing roles from which the privileges will be assigned to the Pluggable Database Administrator.
  - Creating a new Database Role: If you select this option, you must specify the Role Name, Description, and the Privileges such as CREATE_SESSION, ALTER_SESSION, CREATE ANY OPERATOR, CREATE ANY PROCEDURE and so on that will be assigned to the administrator.
- Pluggable Database Storage: The maximum size of the PDB storage can either be Unlimited or Specified by the workload size selected at request time.
- Tablespace: The tablespaces in the profile are displayed. You can edit the value of the Initial Size of the tablespace.
  
  Note:
  
  You can create encrypted tablespaces by specifying a Tablespace Data Encryption (TDE) key. This encrypts and decrypts the data in the tablespace. If you are using a profile with encrypted tablespaces, you will be prompted for the wallet password here.
Click Next. The Create Service Template: Initialization Parameters page appears. In this page, you can configure the values of various initialization parameters that affect the operation of the database instance. Select the parameter and click the Set icon to modify the value of the parameter.
Click Next. The Create Service Template: Customization page appears. Specify the custom scripts that need to be executed before and after the database is created. See Pre and Post Request Creation / Deletion Scripts for details.
In the Target Properties region, you can specify global target properties such as Location, Department, Line of Business, and so on. You can do the following:
- Mark a property as mandatory by selecting the Required check box. If a property is marked as mandatory, the self service user must specify a value for this property while requesting a database.
- Lock a property. When a property is locked, the self service user cannot modify the value of this property while requesting a database.
Click Next. The Create Service Template: Roles page appears. Click Add to select the EM_SSA_USER roles to which this service template will be available. All users belonging to the selected role can use this service template.
Click Next. The Create Service Template: Review page appears where you can review the details entered so far.
Click Submit. The newly created service template will appear in the Database Cloud Self Service Portal Setup: Service Templates page. You can click on the Service Template Name link to view additional details.

Creating a Service Template for an Empty PDB

One or more pluggable databases can be created based on the service template definition. To create a service template for PDB as a service, follow these steps:

Log into Enterprise Manager as a user with the EM_SSA_ADMINISTRATOR role.
From the Enterprise menu, select Cloud, then select Cloud Home. The Cloud Home page appears. From the Oracle Cloud menu, select Setup, then select Getting Started.
Click the Setup link next to the Databases option in the left panel. Select Pluggable Database from the drop down menu.
Click the Service Templates link. The Service Templates page appears. Click Create. The Create Service Template: General page appears.

Figure 24-7 Create Service Template: General (Empty)
Enter a name and description for the service template. The description must be unique and provide information on the type of service template being created.
In the Pluggable Databases region, select the Create Empty Pluggable Database option to create an empty PDB that can be configured by the user.
In the Pools and Zones region, click Add to select a PaaS Infrastructure Zone into which the pluggable database instance is to be provisioned. Click Assign Pool to add a Database Pool (for Pluggable Databases) for the zone.

Note:

A database pool (for PDBs) must be present in the PaaS Infrastructure Zone that you select here.
After the database pool has been assigned, the container database into which the pluggable database is to be added is displayed in the Reference Container Database field. All the validations for the service template will be performed against this database.
In the Placement region, the pluggable database can be provisioned on the container database using one of the following options:
- Selected by placement algorithm
- Selected by user during request
In the Identification region, in the Pluggable Database Prefix Name field, specify the prefix that is to be used to generate a unique Pluggable Database name at the time of database creation. The prefix helps to identify the PDBs that are created using this service template.
Click Next. The Create New Service Template: Configurations page appears.
Figure 24-8 Create Service Template: Configurations (PDB)

Specify the following details:
- Workload Size: Workload represents the total CPU, memory, number of sessions, and storage requirements for each service. You can define workload sizes such as small, medium, and large. The workload sizes defined here will be the default workload sizes available to the users with the EM_SSA_USER role.
  
  Click Create and in the Create Workload window, enter the name, CPU, Memory, and Storage limit for each service.
- Pluggable Database Administrator Privileges: You can assign privileges to the Pluggable Database Administrator by:
  - From Existing Database Roles: If you select this option, click Add Roles to add one or more existing roles from which the privileges will be assigned to the Pluggable Database Administrator.
  - Creating a new Database Role: If you select this option, you must specify the Role Name, Description, and the Privileges such as CREATE_SESSION, ALTER_SESSION, CREATE ANY OPERATOR, CREATE ANY PROCEDURE and so on that will be assigned to the administrator.
- Pluggable Database Storage: The maximum size of the PDB storage can either be Unlimited or Specified by the workload size selected at request time.
- Tablespace: Specify the number of tablespaces that should be present in the new empty PDB.
Click Next. The Create Service Template: Initialization Parameters page appears. In this page, you can configure the values of various initialization parameters that affect the operation of the database instance. Select the parameter and click the Set icon to modify the value of the parameter.
Click Next. The Create Service Template: Customization page appears. Specify the custom scripts that need to be executed before and after the database is created. See Pre and Post Request Creation / Deletion Scripts for details.
In the Target Properties region, you can specify global target properties such as Location, Department, Line of Business, and so on. You can do the following:
- Mark a property as mandatory by selecting the Required check box. If a property is marked as mandatory, the self service user must specify a value for this property while requesting a database.
- Lock a property. When a property is locked, the self service user cannot modify the value of this property while requesting a database.
Click Next. The Create Service Template: Roles page appears. Click Add to select the EM_SSA_USER roles to which this service template will be available. All users belonging to the selected role can use this service template.
Click Next. The Create Service Template: Review page appears where you can review the details entered so far.
Click Submit. The newly created service template will appear in the Database Cloud Self Service Portal Setup: Service Templates page. You can click on the Service Template Name link to view additional details.

Configuring Chargeback

Optionally, you can configure the chargeback service. See Chargeback Administration.

Requesting a Pluggable Database

The self service user can now select the service template and create a pluggable database. See Requesting a Pluggable Database

Pluggable Database creation using SSA User Data Profile

An EM Self Service Application administrator can enable a Self Service Application (SSA) user to create a new PDB instance using a pre-existing Data Profile.

The SSA User can create a new pluggable database using a pluggable database backup preserved as an SSA User Data Profile.

To enable the SSA user to create a new PDB instance, the option Create Pluggable Database using Data Profile by SSA user at request time must be selected in the Pluggable Database Service Template.

Figure 24-9 Create Pluggable Database using Data Profile by SSA user

The SSA user selects a data profile during creation of a new PDB instance. However, the Select Data Profile option is enabled depending on the configuration of the service template.

Figure 24-10 Select Data Profile

In the Select Data Profile field, when you click the search icon, the profiles created by the SSA user and the profiles for which the user has view privileges, are listed.

Creating Test Master Pluggable Databases and Snapshot Clones

This section provides the following different solutions of creating test master pluggable database and snapshot clones of test master pluggable databases:

Creating a Test Master Pluggable Database

If you have the 12.1.0.8 Enterprise Manager for Oracle Database plug-in deployed in your system, you can create a test master PDB from a source PDB, using the new Clone PDB Wizard.

To create a test master PDB from a source PDB, follow these steps:

From the Targets menu, select Databases.
For View, select Search List. From the View menu, select Expand All.
Look for the source CDB (the CDB that the source PDB is a part of) in the list, then click the name of the PDB from which you want to create a test master PDB.
From the Oracle Database menu, select Cloning, then select Create Test Master.

Alternatively, in Step 3, you can right click the name of the PDB from which you want to create a test master PDB, select Oracle Database, select Cloning, then select Create Test Master.
On the Create Test Master Pluggable Database: Source and Destination page, do the following:
- Specify the SYSDBA credentials for the source CDB. You can choose to use the preferred credentials, use a saved set of named credentials, or specify a new set of credentials.
- In the Pluggable Database Definition section, specify a name, and a display name for the test master PDB. Enterprise Manager uses the display name to identify the test master PDB target.
- In the PDB Administrator Credentials section, specify the credentials of the admin user account that you want to use to administer the test master PDB.
- In the Container Database section, specify the destination CDB (the CDB that the test master PDB must be a part of).
- In the Credentials section, specify the SYSDBA credentials for the destination CDB, and the host credentials for the destination CDB. Also, if the destination CDB is using Automatic Storage Management (ASM) to manage disk storage, you must specify the ASM credentials.
  
  Click Next.
On the Create Test Master Pluggable Database: Configuration page, do the following:

In the Database Files Location section, specify the storage location where the datafiles of the test master PDB must be stored. If the destination CDB is using ASM to manage disk storage, specify the disk group where the datafiles of the test master PDB must be stored.

To ensure that only the source PDB data model definition is cloned (and the source PDB data is not cloned), select Exclude User Data.

In the PDB Administrator Credentials section, specify the credentials of the admin user account that you want to use to administer the test master PDB.

In the Advanced Configuration section, specify the storage limits for the maximum size of the test master PDB, and the maximum size of a shared tablespace within the test master PDB. By default, no limits are placed on the values for these attributes. In the Miscellaneous section, select the logging option that you want to use for the tablespaces created within the test master PDB.

Note that if the destination CDB is part of an Exadata machine, the Access Controls and Permissions section is displayed in place of the Advanced Configuration section. In this case, you must specify the owner and the group that must be granted read only permissions on the datafiles.

Click Next.
On the Create Test Master Pluggable Database: Post Processing page, in the Data Masking section, specify the data masking definition that you want to apply after creating the test master PDB. Data masking masks sensitive data in a database.

For information on how to create a data masking definition, see the Oracle Data Masking and Subsetting Guide. Note that you can apply a data masking definition only if you have the Subset-Masking license pack.

In the Custom Scripts section, for Pre Script and Post Script, specify the Oracle Software Library components that contain the scripts that you want to run before, and after creating the test master PDB respectively. Also, for SQL Script, specify the SQL scripts that you want to run after creating the test master PDB. For Run As User, select the user account that you want to use to run the SQL scripts.

Click Next.
Specify an instance name for the deployment procedure. Also, specify the point in time when you want the deployment procedure to begin.

In the Notification section, select the deployment procedure states for which you want to receive e-mail notifications. For example, if you select Scheduled and Succeeded for Status for Notification, you will receive e-mail notifications when the deployment procedure is scheduled, and when it succeeds.

Click Next.
Review all the details you provided. If you want to edit certain details, click Back to navigate to the required page.

Click Clone to submit the deployment procedure to create a test master PDB from the source PDB.

Note:
The pluggable database cloning procedure contains a prerequisite step that is enabled by default. This step causes the cloning procedure to fail. To disable this step, run the following command:
emctl set property -name oracle.sysman.db.pdb.prereq_enabled —sysman_pwd <sysman password> —value false

To enable this step, run the following command:

emctl set property -name oracle.sysman.db.pdb.prereq_enabled -sysman_pwd <sysman password> —value true

Creating an Exadata Test Master Pluggable Database

If you have the 12.1.0.8 Enterprise Manager for Oracle Database plug-in deployed in your system, you can create a test master PDB from a source PDB, using the new Clone PDB Wizard.

To create a test master PDB from a source PDB, follow these steps:

From the Targets menu, select Databases.
For View, select Search List. From the View menu, select Expand All.
Look for the source CDB (the CDB that the source PDB is a part of) in the list, then click the name of the PDB from which you want to create a test master PDB.
From the Oracle Database menu, select Cloning, then select Create Test Master.

Alternatively, in Step 3, you can right click the name of the PDB from which you want to create a test master PDB, select Oracle Database, select Cloning, then select Create Test Master.
On the Create Test Master Pluggable Database: Source and Destination page, do the following:
- Specify the SYSDBA credentials for the source CDB. You can choose to use the preferred credentials, use a saved set of named credentials, or specify a new set of credentials.
- In the Pluggable Database Definition section, specify a name, and a display name for the test master PDB. Enterprise Manager uses the display name to identify the test master PDB target.
- In the PDB Administrator Credentials section, specify the credentials of the admin user account that you want to use to administer the test master PDB.
- In the Container Database section, specify the destination CDB (the CDB that the test master PDB must be a part of).
- In the Credentials section, specify the SYSDBA credentials for the destination CDB, and the host credentials for the destination CDB. Also, if the destination CDB is using Automatic Storage Management (ASM) to manage disk storage, you must specify the ASM credentials.
  
  Click Next.
On the Create Test Master Pluggable Database: Configuration page, do the following:

In the Database Files Location section, specify the disk group where the data files of the test master PDB will be created.

To ensure that only the source PDB data model definition is cloned (and the source PDB data is not cloned), select Exclude User Data.

In the Access Controls and Permissions section, specify the owner and the group that must be granted read-only permissions on the data files.

Click Next.
On the Create Test Master Pluggable Database: Post Processing page, in the Data Masking section, specify the data masking definition that you want to apply after creating the test master PDB. Data masking masks sensitive data in a database.

For information on how to create a data masking definition, see the Oracle Data Masking and Subsetting Guide. Note that you can apply a data masking definition only if you have the Subset-Masking license pack.

In the Custom Scripts section, for Pre Script and Post Script, specify the Oracle Software Library components that contain the scripts that you want to run before, and after creating the test master PDB respectively. Also, for SQL Script, specify the SQL scripts that you want to run after creating the test master PDB. For Run As User, select the user account that you want to use to run the SQL scripts.

Click Next.
Specify an instance name for the deployment procedure. Also, specify the point in time when you want the deployment procedure to begin.

In the Notification section, select the deployment procedure states for which you want to receive e-mail notifications. For example, if you select Scheduled and Succeeded for Status for Notification, you will receive e-mail notifications when the deployment procedure is scheduled, and when it succeeds.

Click Next.
Review all the details you provided. If you want to edit certain details, click Back to navigate to the required page.

Click Clone to submit the deployment procedure to create a test master PDB from the source PDB.

Creating a Snapshot Clone of an Exadata Test Master PDB

Note:

You can create snapshot clones of only those test master PDBs that are of version 12.1.0.2.0 or higher.

If you have the 12.1.0.8 Enterprise Manager for Oracle Database plug-in deployed in your system, you can create a snapshot clone of a test master PDB using the new Clone PDB Wizard.

To create a snapshot clone of an exadata test master PDB, follow these steps:

From the Targets menu, select Databases.
For View, select Search List. From the View menu, select Expand All.
Look for the source CDB (the CDB that the source test master PDB is a part of) in the list, then click the name of the test master PDB that you want to clone.
From the Oracle Database menu, select Cloning, then select Create Snapshot Clone.

Alternatively, in Step 3, you can right click the name of the test master PDB that you want to clone, select Oracle Database, select Cloning, then select Create Snapshot Clone.
On the Source and Destination: Create Snapshot Clone Pluggable Database, do the following:
- Specify the SYSDBA credentials for the source CDB. You can choose to use the preferred credentials, use a saved set of named credentials, or specify a new set of credentials.
- In the Credentials section, specify the SYSDBA credentials of the CDB.
- In the Pluggable Database Definition section, specify the name of the PDB, and a display name of the PDB snapshot clone. Enterprise Manager uses the display name to identify the PDB snapshot clone target.
- In the PDB Administrator Credentials section, specify the credentials of the Admin user account that you want to use to administer the PDB snapshot clone.
  
  To clone the test master PDB to a CDB different from the source CDB, select Clone the Pluggable Database into a different Container Database, then specify the destination CDB.
- In the Credentials section, specify the CDB host credentials. Also, specify the ASM credentials of the ASM that will be used to manage disk storage.
If you do not need to specify anymore details, click Clone. This submits the deployment procedure to clone a PDB to a CDB that is deployed in a public cloud setup.

To specify other configuration details, mask data, as well as schedule the cloning process, click Advanced.

Follow the rest of the steps, if you have selected the Advanced option. The option to Clone is available on each page.
On the Create Snapshot Clone Pluggable Database: Source and Destination page, verify the details specified, and then click Next.
On the Create Snapshot Clone Pluggable Database: Configuration page, do the following:
- In the Database Files Location section, specify the name of the Sparse disk group where the data files of the PDB snapshot clone will be created.
- In the Advanced Configuration section, specify the storage limits for the maximum size of the PDB snapshot clone, and the maximum size of a shared tablespace within the PDB snapshot clone. By default, no limits are placed on the values for these attributes.
- In the Miscellaneous section, select the default logging option for the tablespaces created within the PDB snapshot clone.
- Click Next.
On the Create Snapshot Clone Pluggable Database: Post Processing section, in the Data Masking section, specify the data masking definition that you want to apply after cloning the PDB. Data masking masks sensitive data in a database.

For information on how to create a data masking definition, see the Oracle Data Masking and Subsetting Guide. Note that you can apply a data masking definition only if you have the Subset-Masking license pack.

In the Custom Scripts section, for Pre Script and Post Script, specify the Oracle Software Library components that contain the scripts that you want to run before cloning, and after cloning the PDB respectively. Also, for SQL Script, specify the SQL scripts that you want to run after cloning the PDB. For Run As User, select the user account that you want to use to run the SQL scripts.

Click Next.
On the Create Snapshot Clone Pluggable Database: Schedule page, specify an instance name for the cloning deployment procedure. Also, specify the point in time when you want the cloning procedure to begin.

In the Notification section, select the deployment procedure states for which you want to receive e-mail notifications. For example, if you select Scheduled and Succeeded for Status for Notification, you will receive e-mail notifications when the cloning deployment procedure is scheduled, and when it succeeds.

Click Next.
On the Create Snapshot Clone Pluggable Database: Review page, review all the details you provided. If you want to edit certain details, click Back to navigate to the required page.

Click Clone to submit the deployment procedure to create a snapshot clone of the exadata test master PDB.

Creating an ACFS Test Master Pluggable Database

If you have the 12.1.0.8 Enterprise Manager for Oracle Database plug-in deployed in your system, you can create a test master PDB from a source PDB, using the new Clone PDB Wizard.

To create a test master PDB from a source PDB, follow these steps:

From the Targets menu, select Databases.
For View, select Search List. From the View menu, select Expand All.
Look for the source CDB (the CDB that the source PDB is a part of) in the list, then click the name of the PDB from which you want to create a test master PDB.
From the Oracle Database menu, select Cloning, then select Create Test Master.

Alternatively, in Step 3, you can right click the name of the PDB from which you want to create a test master PDB, select Oracle Database, select Cloning, then select Create Test Master.
On the Create Test Master Pluggable Database: Source and Destination page, do the following:
- Specify the SYSDBA credentials for the source CDB. You can choose to use the preferred credentials, use a saved set of named credentials, or specify a new set of credentials.
- In the Pluggable Database Definition section, specify a name, and a display name for the test master PDB. Enterprise Manager uses the display name to identify the test master PDB target.
- In the PDB Administrator Credentials section, specify the credentials of the admin user account that you want to use to administer the test master PDB.
- In the Container Database section, specify the destination CDB (the CDB that the test master PDB must be a part of).
- In the Credentials section, specify the SYSDBA credentials for the destination CDB, and the host credentials for the destination CDB. Also, if the destination CDB is using Automatic Storage Management (ASM) to manage disk storage, you must specify the ASM credentials.
  
  Click Next.
On the Create Test Master Pluggable Database: Configuration page, in the Database Files Location section, specify the ACFS mount point storage location where the data files of the test master PDB will be created.

To ensure that only the source PDB data model definition is cloned (and the source PDB data is not cloned), select Exclude User Data.

Click Next.
On the Create Test Master Pluggable Database: Post Processing page, in the Data Masking section, specify the data masking definition that you want to apply after creating the test master PDB. Data masking masks sensitive data in a database.

For information on how to create a data masking definition, see the Oracle Data Masking and Subsetting Guide. Note that you can apply a data masking definition only if you have the Subset-Masking license pack.

In the Custom Scripts section, for Pre Script and Post Script, specify the Oracle Software Library components that contain the scripts that you want to run before, and after creating the test master PDB respectively. Also, for SQL Script, specify the SQL scripts that you want to run after creating the test master PDB. For Run As User, select the user account that you want to use to run the SQL scripts.

Click Next.
Specify an instance name for the deployment procedure. Also, specify the point in time when you want the deployment procedure to begin.

In the Notification section, select the deployment procedure states for which you want to receive e-mail notifications. For example, if you select Scheduled and Succeeded for Status for Notification, you will receive e-mail notifications when the deployment procedure is scheduled, and when it succeeds.

Click Next.
Review all the details you provided. If you want to edit certain details, click Back to navigate to the required page.

Click Clone to submit the deployment procedure to create a test master PDB from the source PDB.

Creating a Snapshot Clone of an ACFS Test Master PDB

Note:

You can create snapshot clones of only those test master PDBs that are of version 12.1.0.2.0 or higher.

If you have the 12.1.0.8 Enterprise Manager for Oracle Database plug-in deployed in your system, you can create a snapshot clone of a test master PDB using the new Clone PDB Wizard.

To create a snapshot clone of an exadata test master PDB, follow these steps:

From the Targets menu, select Databases.
For View, select Search List. From the View menu, select Expand All.
Look for the source CDB (the CDB that the source test master PDB is a part of) in the list, then click the name of the test master PDB that you want to clone.
From the Oracle Database menu, select Cloning, then select Create Snapshot Clone.

Alternatively, in Step 3, you can right click the name of the test master PDB that you want to clone, select Oracle Database, select Cloning, then select Create Snapshot Clone.
On the Source and Destination: Create Snapshot Clone Pluggable Database, do the following:
- Specify the SYSDBA credentials for the source CDB. You can choose to use the preferred credentials, use a saved set of named credentials, or specify a new set of credentials.
- In the Credentials section, specify the SYSDBA credentials of the CDB.
- In the Pluggable Database Definition section, specify the name of the PDB, and a display name of the PDB snapshot clone. Enterprise Manager uses the display name to identify the PDB snapshot clone target.
- In the PDB Administrator Credentials section, specify the credentials of the Admin user account that you want to use to administer the PDB snapshot clone.
  
  To clone the test master PDB to a CDB different from the source CDB, select Clone the Pluggable Database into a different Container Database, then specify the destination CDB.
- In the Credentials section, specify the CDB host credentials. Also, specify the ASM credentials of the ASM that will be used to manage disk storage.
If you do not need to specify anymore details, click Clone. This submits the deployment procedure to clone a PDB to a CDB that is deployed in a public cloud setup.

To specify other configuration details, mask data, as well as schedule the cloning process, click Advanced.

Follow the rest of the steps, if you have selected the Advanced option. The option to Clone is available on each page.
On the Create Snapshot Clone Pluggable Database: Source and Destination page, verify the details specified, and then click Next.
On the Create Snapshot Clone Pluggable Database: Configuration page, do the following:
- In the Database Files Location section, specify the name of the Sparse disk group where the data files of the PDB snapshot clone will be created.
- In the Advanced Configuration section, specify the storage limits for the maximum size of the PDB snapshot clone, and the maximum size of a shared tablespace within the PDB snapshot clone. By default, no limits are placed on the values for these attributes.
- In the Miscellaneous section, select the default logging option for the tablespaces created within the PDB snapshot clone.
- Click Next.
On the Create Snapshot Clone Pluggable Database: Post Processing section, in the Data Masking section, specify the data masking definition that you want to apply after cloning the PDB. Data masking masks sensitive data in a database.

For information on how to create a data masking definition, see the Oracle Data Masking and Subsetting Guide. Note that you can apply a data masking definition only if you have the Subset-Masking license pack.

In the Custom Scripts section, for Pre Script and Post Script, specify the Oracle Software Library components that contain the scripts that you want to run before cloning, and after cloning the PDB respectively. Also, for SQL Script, specify the SQL scripts that you want to run after cloning the PDB. For Run As User, select the user account that you want to use to run the SQL scripts.

Click Next.
On the Create Snapshot Clone Pluggable Database: Schedule page, specify an instance name for the cloning deployment procedure. Also, specify the point in time when you want the cloning procedure to begin.

In the Notification section, select the deployment procedure states for which you want to receive e-mail notifications. For example, if you select Scheduled and Succeeded for Status for Notification, you will receive e-mail notifications when the cloning deployment procedure is scheduled, and when it succeeds.

Click Next.
On the Create Snapshot Clone Pluggable Database: Review page, review all the details you provided. If you want to edit certain details, click Back to navigate to the required page.

Click Clone to submit the deployment procedure to create a snapshot clone of the exadata test master PDB.

Enabling a Test Master Pluggable Database

To convert a pluggable database into a test master, follow these steps:

Right click on the pluggable database target name that you want to enable as a test master, select Oracle Database, select Cloning, and then select Enable as a Test Master.
On the Enable as a Test Master page, in the Credentials section, specify the credentials for the container database of the pluggable database, and the credentials of the Oracle Home.
In the Source section, specify or search for the parent database from which the database has been created. This provides better lineage tracking.
In the Data Masking section, you can choose to desensitize the data by applying masking templates or by running additional scripts of your choice.
In the Custom Scripts section, you can select the Software Library components which contain post cloning scripts. The clone database can also be customized by executing the post cloning SQL script.
Click Submit.

Disabling a Test Master Pluggable Database

Disabling a test master pluggable database, resets the data files to read-write mode and restarts the pluggable database in open mode. You can make further changes to the database and then enable it as a test master again.

To disable a test master pluggable database, follow these steps:

Right click on the test master pluggable database, select Oracle Database, select Cloning, and then select Disable as a Test Master.
On the Disable Test Master page, specify the credentials of the container database of the test master pluggable database. Also, specify the credentials of the Oracle Home.
Click Submit.