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.

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.

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

2. On the Reference Target page, click the search icon to select a target.
3. In the Search and Select:Targets display box, select the database you want to create a profile for, and then, click Select.
4. 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

   
   
   
5. 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.
6. 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.

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

     
     
     
8. 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.
9. Specify or select a working directory. Click Next.
10. 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.

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, this is know as a dehydrate of a PDB by an SSA user.

Figure 20-1 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 20-2 Preserve a Backup

1. Log into Enterprise Manager as a user with the EM_SSA_ADMINISTRATOR role.
2. 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.
3. Click the Setup link next to the Databases option in the left panel. Select Pluggable Database from the drop down menu.
4. Click the Service Templates link. The Service Templates page appears. Click Create. The Create Service Template: General page appears.
5. 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.
6. 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.
7. 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.
8. 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.
9. 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.
10. 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.
11. 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.
12. Click Next. The Create New Service Template: Configurations page appears.
    For TDE enabled databases enter the Wallet Transport key. This is the same key provided during unplugging of the PDB.
13. 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.
14. 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.
15. 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.
16. 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.
17. Click Next. The Create Service Template: Review page appears where you can review the details entered so far.
18. 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.

1. Log into Enterprise Manager as a user with the EM_SSA_ADMINISTRATOR role.
2. 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.
3. Click the Setup link next to the Databases option in the left panel. Select Pluggable Database from the drop down menu.
4. Click the Service Templates link. The Service Templates page appears. Click Create. The Create Service Template: General page appears.
5. 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.
6. In the Pluggable Databases region, select the Create Empty Pluggable Database option to create an empty PDB that can be configured by the user.
7. 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.
8. 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.
9. 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
10. 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.
11. Click Next. The Create New Service Template: Configurations page appears.
    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.
12. 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.
13. 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.
14. 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.
15. 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.
16. Click Next. The Create Service Template: Review page appears where you can review the details entered so far.
17. 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.

1. Log into Enterprise Manager as a user with the EM_SSA_ADMINISTRATOR role.
2. 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.
3. Click the Setup link next to the Databases option in the left panel. Select Pluggable Database from the drop down menu.
4. Click the Service Templates link. The Service Templates page appears. Click Create. The Create Service Template: General page appears.
5. 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.
6. 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.
7. 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.
8. 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.
9. Selected Create Pluggable database using Data Profile selected by SSA user at request time. 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.
10. 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.
11. 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.
12. Click Next. The Create New Service Template: Configurations page appears.
13. 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.
14. 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.
15. 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.
16. 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.
17. Click Next. The Create Service Template: Review page appears where you can review the details entered so far.
18. 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.

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, this is known as a Hydrate PDB process.

Before you create a PDB with an SSA User you must set up a Service Template with the Create Pluggable database using Data Profile selected by SSA user at request time option selected, to do this see: Creating a Service Template Using a Data Profile Selected by an SSA User At Request Time.

1. 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.
2. 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.
3. In the Source section, specify or search for the parent database from which the database has been created. This provides better lineage tracking.
4. In the Data Masking section, you can choose to desensitize the data by applying masking templates or by running additional scripts of your choice.
5. 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.
6. Click Submit.
   
   

   

   
   

1. Right click on the test master pluggable database, select Oracle Database, select Cloning, and then select Disable as a Test Master.
2. 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.
3. Click Submit.