Skip Headers
Oracle® Enterprise Manager Cloud Administration Guide
12c Release 4 (12.1.0.4)

E28814-11
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

13 ­­Setting Up the DBaaS Self Service Portal

This chapter describes the procedure to set up and use the Database Self Service Portal. It contains the following sections:

13.1 DBaaS Use Cases

The following figure provides an overview of the different flavors of Enterprise Manager DBaaS.

Figure 13-1 DBaaS Flavors

Surrounding text describes Figure 13-1 .

This chapter covers the following use cases:

13.2 Setting Up the Database Cloud Self Service Portal

The Database Cloud Self Service Portal is a Web page where Cloud users can request, monitor, and manage their own databases using Enterprise Manager. An administrator with the EM_SSA_ADMINISTRATOR role can configure and set up the database self service portal by defining database pools, service templates, and so on. Setting up the Database Cloud Self Service Portal involves the following:

Note:

Click here to view a visual demonstration on how to use the Database Cloud Self Service Portal in Oracle Enterprise Manager Cloud Control 12c.

13.2.1 Creating a Database Pool

A Database Pool contains a set of resources that can be used to provision a database instance within a PaaS Infrastructure Zone. A database pool is a collection of homogenous targets such as servers or clusters with database software installed. For more details, see Section 10.4, "Creating a PaaS Pool".

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

  1. Log into Enterprise Manager as a user with the EM_SSA_ADMINISTRATOR role.

  2. From the Setup menu, select Cloud, then select Database. The Database Cloud Self Service Portal Setup page appears.From the Create menu, select For Database. The Create New Pool page appears.

    Figure 13-2 Create Database Pool

    Create Database Pool
  3. In the Credentials region, specify the following credentials:

    • Host: Required for creating and starting the database.

    • Root: This is an optional field. It is required if you plan to use this database pool for database requests based on snap clone profile. See Section 13.6, "Using Snap Clone to Provision Databases".

    • Grid Infrastructure: This is an optional field. It is required if you plan to use this database pool for live cloning using of a database using ASM.

  4. Enter a name and description for the database pool.

  5. Specify the following details:

    • PaaS Infrastructure Zone: Select the PaaS Infrastructure Zone into which the database instance is to be provisioned.

    • Database Configuration: Specify the configuration of the database being provisioned. This can either be Single Instance or Cluster Database (RAC) but cannot be a combination of both.

    • Platform and Version: Specify the platform and version of the database being deployed.

  6. Click Add and select one or more Oracle Homes to be added to the database pool.

  7. In the Maximum Number of Database Instances (per host), enter the maximum number of database instances that can be running on each host in the pool.

    Note:

    For RAC databases. the value specified in this field is used to ensure that the nodes on which the database is be created meets this criteria.
  8. Click Submit to create a database pool. The newly created pool will appear in the Database Cloud Self Service Portal Setup: Database Pools page. The database pool can now be added to the Service Template.

13.2.2 Configuring Request Settings

You can configure the database request settings by specifying when a request can be made, its duration, and so on. To configure the request settings, follow these steps:

  1. Log into Enterprise Manager as a user with the EM_SSA_ADMINISTRATOR. role.

  2. From the Setup menu, select Cloud, then select Database. The Database Cloud Self Service Portal Setup page appears.

  3. Click the Request Settings tab. Specify the following:

    • FutureReservationLength: How far in advance a request can be scheduled. You can select:

      • No Restriction: A new database request can be scheduled on any date later than the current date.

      • Restricted Reservation: A new database request can be scheduled in the future within the period specified here. Any future request scheduled beyond the Restricted Reservation date will be denied.

        For example, if the Restricted Reservation is 1 year, and the current date is June 20, 2013, you can schedule a future request on or before June 20, 2014.

    • MaximumArchiveRetention: Period after which the requests are automatically archived. You can select:

      • No Restriction: If this option is selected, requests are not archived.

      • Restricted Retention: Requests that older than the specified duration will be archived. The date on which a request is archived is based on the last modified date of the request.

        For example, if a request has been created on June 10, 2013 and the Restricted Retention period specified is 10 days. Suppose there are some associated child requests as follows:

        - Reschedule Request: Submitted on June 12

        - Start Instance: Submitted on June 14

        - Stop Instance: Submitted on June 17

        - Start Instance: Submitted on June 18

        - Delete Instance: Submitted on June 20

        Since the date on which the request was last modified is June 20, the request will be purged on June 30th (Restricted Retention = 10 days).

    • DefaultRetirementPeriod: The maximum period for which the service instance can be retained. You can select:

      • No Restriction: Requests do not have a end date and can be extended as required.

      • Restricted Duration: The period after which the service instance is to be released.

        For example, if the Restricted Duration is 15 days, and the request begin date is June 5, 2013, the service instance will be retired or released on June 25, 2013.

  4. Click Apply.

13.2.3 Setting Up Quotas

Quota is the aggregate amount of resources that can be granted to each self service user belonging to a certain role. This quota applies only to the databases provisioned through the Database Cloud Self Service Portal. To set up quotas, follow these steps:

  1. Log into Enterprise Manager as a user with the EM_SSA_ADMINISTRATOR role.

  2. From the Setup menu, select Cloud, then select Database. The Database Cloud Self Service Portal Setup page appears.

  3. Click the Quotas tab and then click Create.

    Note:

    Quota validation ensures that a request is executed only if the user's current usage is within the limits specified for the roles to which the user belongs. Only the direct roles are considered for the quota determination, and not nested ones.
  4. In the Create New Quota window, select the Role Name for which the quota is to be granted. Only roles that have the EM_SSA_USER privileges are displayed in the Select Roles dialog box. After you have selected the role, enter the following details:

    • Memory: Total allocated memory that can be assigned for all the databases owned by a specific user. This should be the total memory used by all:

      • Databases

      • Schemas requested

      • Pluggable Databases

    • Storage: Total allocated storage that can be assigned for all the databases owned by a user. This should be total storage used by all:

      • Databases

      • Schemas requested

      • Pluggable Databases

        Note:

        Storage used for backups is not included here.
    • Number of Database Requests: The number of databases that can be requested by a user at any point in time. The standby databases created as part of database requests will not be included in this quota. But the storage and memory values for the standby databases will be added to the total allocated storage and memory.

    • Number of Schema Service Requests: The number of database services that can be requested by the user.

    • Number of Pluggable Database Service Requests: The number of PDBs that can be requested by the user.

    For example, if a user has 3 roles and the quota defined for each role is as follows:

    Role Name Attribute Value
    Dev Role Memory 30 GB
      Storage 40 GB
      DB Requests 10
      Schema Requests 2
      PDB Requests 3
    Test Role Memory 40 GB
      Storage 60 GB
      DB Requests 12
      Schema Requests 3
      PDB Requests 5
    PM Role Memory Quota not set
      Storage Quota not set
      DB Requests Quota not set
      Schema Requests Quota not set
      PDB Requests Quota not set

    The quota limits for each of the attributes would be determined based on all the roles to which a user directly belongs. For example, if a user has 3 roles with quota setup for each role as shown in the table below:

    The quota is calculated as the absolute maximum across the roles for each attribute value. For the user who belongs to the Dev, Test, and PM Role, the Quota is calculated as:

    Value for Memory = MAX (Dev, Test, PM) = MAX (2, 5, NA) = 5 GB

    Value for Storage = MAX (Dev, Test, PM) = MAX (15, 10, NA) = 15 GB

    Value for DB Requests = MAX (Dev, Test, PM) = MAX (10, 12, NA) = 12 Databases

    Value for Schema Requests = MAX (Dev, Test, PM) = MAX (2, 3, NA) = 5 Database Services

    Value for PDB Requests = MAX (Dev, Test, PM) = MAX (3, 5, NA) = 8 PDB Services

    A sample quota validation log generated by the user request follows:

    Quota validation:
    ==================================================================
                Quota Details
    ==================================================================
    Total resources avaialble
    Memory: 15
    Storage: 20
    Number of Database Instances: 5
    Number of Schema Services: 5
    Number of Pluggable Databases: 10
     
    ==================================================================
                Current Usage
    ==================================================================
    Memory: 0.0
    Storage: 0.0
    Number of Database Instances: 0.0
    Number of Database Services: 0.0
     
    ==================================================================
                Requested Resource
    ==================================================================
    Memory: 0.681640625
    Number Of Databases: 1
    Storage: 0.681640625
     
    -----------------------------------------------------------
                Quota validation for 'Memory'
    -----------------------------------------------------------
    Allocated Resource: 15.0
    Current Usage: 0.0
    Requested: 0.681640625
    ------------------
    Remaining Resource After Allocation: 14.318359375
    -------------------
     
    Result: Passed
    -----------------------------------------------------------
                Quota validation for 'Storage'
    -----------------------------------------------------------
    Allocated Resource: 20.0
    Current Usage: 0.0
    Requested: 0.681640625
    ------------------
    Remaining Resource After Allocation: 19.318359375
    -------------------
     
    Result: Passed
    -----------------------------------------------------------
                Quota validation for 'Number of Database Instances'
    -----------------------------------------------------------
    Allocated Resource: 5.0
    Current Usage: 0.0
    Requested: 1.0
    ------------------
    Remaining Resource After Allocation: 4.0
    -------------------
    

13.2.4 Creating a Database Provisioning Profile

A database provisioning profile is an entity that captures source database information for provisioning. It contains software bits and configuration. A profile can represent a complete database or a set of related schemas that form an application. A single profile can be used to create multiple service templates.

When a provisioning profile is created from an existing installation, it provides the flexibility to clone Grid Infrastructure (with software or configuration) and Oracle Database (with software or configuration).

An administrator can create a database provisioning profile as a one-time activity, which can be used by operators for mass deployments.

Using provisioning profile enables standardization in deployments and reduces need for rescheduling deployments by avoiding errors while configuring deployment procedures.

You can create a database provisioning profile, by using any of the following methods:

Note:

Before you create a provisioning profile, follow these prerequisites:
  • Ensure that the host has a reference database installed on it, for creating a database provisioning profile.

  • Ensure that the host is connected to a Management Agent installed and monitored in Enterprise Manager Cloud Control for communication.

  • Ensure that you have EM_STORAGE_ADMINISTRATOR privilege for Snap Clone based profiles.

  • Ensure that you have connect privileges to the target.

13.2.4.1 Creating a Database Provisioning Profile Using Snapshots

Prerequisites for Creating a Database Provisioning Profile Using Snapshots

Before you create a database provisioning profile, follow these prerequisites:

  • Ensure that the storage server you want to register for storage is available on the network.To register a storage server, refer to Registering and Managing Storage Servers.

    Note:

    NetApp ,Sun ZFS, and Solaris ZFS storage servers are supported in Enterprise Manager Cloud Control 12c.
  • Ensure that the storage server is connected to a Management Agent installed and monitored in Enterprise Manager Cloud Control for communication.

  • Ensure that the storage server is registered, and at least one database should be present which is enabled for Snap Clone.

Creating a Database Provisioning Profile Using Snapshots

To create a database provisioning profile, follow these steps:

  1. You can access the Database Provisioning page using either of the following ways:

    • From the Setup menu, select Cloud, and then select Database. On the Database Cloud Self Service Portal Setup, select Profiles and Service Templates. In the Profiles section, 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.

  2. On the Reference Target page, click the search icon to select a target.

    Reference Target page
  3. In the Search and Select:Targets display box, select the database you want to create a profile for, and then, click Select.

    Search and Select Targets display box

    Note:

    Ensure that the database you select is enabled for Snap Clone. For information refer to Enabling or Disabling Snap Clone.
  4. On the Reference Target page, select the following:

    • Data Content

    • Structure and Data to include physical and structural files from the database

    • Create

    • Snapshots

  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.

    Credentials
  6. On the Profile page, do the following:

    • In the Profile Information section, enter a unique profile name of your choice.

      For example:
      Snap Clone Profile for HR database 
      

      You can also enter a description of the profile, and notes for your reference.

    • In the Schedule section, you can choose to start the profile creation immediately, or you can schedule it for a later time.

    • Click Next.

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

    Review page for Snap Clone Profile

    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, from the Enterprise menu, select Provisioning and Patching, and then select Procedure Activity.

13.2.4.2 Creating a Database Provisioning Profile Using RMAN Backup

To create a database provisioning profile, follow these steps:

  1. You can access the Database Provisioning page using either of the following ways:

    • From the Setup menu, select Cloud, and then select Database. On the Database Cloud Self Service Portal Setup, select Profiles and Service Templates. In the Profiles section, 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.

  2. On the Reference Target page, click the search icon to select a target.

    Reference Target page for RMAN Backup
  3. In the Search and Select:Targets display box, select the database you want to create a profile for, and then, click Select.

    Search and Select Targets display box
  4. On the Reference Target page, select the following:

    • Data Content

    • Structure and Data to include physical and structural files from the database.

    • Create

    • RMAN Backup

    Reference Target page
  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.

    Credentials
  6. On the Content Options page, do the following:

    • Select Online Backup or Offline Backup.

    • Enter the number of channels.

      Note:

      A channel is the connection between the RMAN and the database. The usage of channels in RMAN backups sets the degree of parallelism. Each channel represents one stream of data to the device type. The more number of channels you allocate, the faster the backup jobs run. The maximum number of channels you can use is 25.
    • (optional) Select Compress files and then select High, Medium, or Low strength of compression.

    • (optional) Select Use File Encryption and then, enter the password and confirm the password.

    • Select Directory for the Backup location, and enter the directory path (or) select Fast Recovery Area, which already contains a backup location.

      Note:

      Ensure that the given location is accessible to the nodes in the database pool.
    • Enter the backup file name format. This will be used to generate backup files.

      backup file tag, control file name, and control file tag.

    • Enter the backup file tag. Backup files will be tagged with this tag.

    • Enter the control file name. The control file backup will be generated with this name.

    • Click Next.

    Content Options page
  7. On the Profile page, do the following:

    • In the Profile Information section, enter a unique profile name of your choice.

      For example:
      RMAN Provisioning Profile for HR database
      

      You can also enter a description of the profile, and notes for your reference.

    • In the Schedule section, you can choose to start the profile creation immediately, or you can schedule it for a later time.

    • Click Next.

    Profile page for RMAN Backup
  8. 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.

    Review page for RMAN Backup

    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, from the Enterprise menu, select Provisioning and Patching, and then select Procedure Activity.

13.2.4.3 Creating a Database Provisioning Profile Using Existing RMAN Backup

To create a database provisioning profile, follow these steps:

  1. You can access the Database Provisioning page using either of the following ways:

    • From the Setup menu, select Cloud, and then select Database. On the Database Cloud Self Service Portal Setup, select Profiles and Service Templates. In the Profiles section, 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.

  2. On the Reference Target page, click the search icon to select a target.

    Reference Target page
  3. In the Search and Select:Targets display box, select the database you want to create a profile for, and then, click Select.

    Search and Select Targets display box
  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.

    • Use Existing RMAN Backup

    Reference Target page for existing RMAN backup
  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.

    Credentials
  6. On the Content Options page, select an existing RMAN backup from the list provided.

    Note:

    The list of existing RMAN backups are fetched from the database.

    Click Next.

  7. On the Profile page, do the following:

    • In the Profile Information section, enter a unique profile name of your choice.

      For example:
      Existing RMAN Provisioning Profile mydb.example.com
      

      You can also enter a description of the profile, and notes for your reference.

    • In the Schedule section, you can choose to start the profile creation immediately, or you can schedule it for a later time.

    • Click Next.

    Creating Profile with Existing RMAN backup
  8. 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.

    Review page for existing RMAN

    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, from the Enterprise menu, select Provisioning and Patching, and then select Procedure Activity.

13.2.4.4 Creating a Database Provisioning Profile Using Database Template

To create a database provisioning profile, follow these steps:

  1. You can access the Database Provisioning page using either of the following ways:

    • From the Setup menu, select Cloud, and then select Database. On the Database Cloud Self Service Portal Setup, select Profiles and Service Templates. In the Profiles section, 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.

  2. On the Reference Target page, click the search icon to select a target.

    Reference Target page
  3. In the Search and Select:Targets display box, select the database you want to create a profile for, and then, click Select.

    Search and Select Targets display box
  4. On the Reference Target page, select the following:

    • Data Content

    • Structure Only to include only the structural files in the template.

    • Create

    • Database Template

    Reference Target page for database template
  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.

    Credentials
  6. On the Profile page, do the following:

    • In the Profile Information section, enter a unique profile name of your choice.

      For example:
      Database Template Provisioning Profile for HR database
      

      You can also enter a description of the profile, and notes for your reference.

      Profile page for database template
    • In the Schedule section, you can choose to start the profile creation immediately, or you can schedule it for a later time.

    • Click Next.

    Creating DB profile using database template
  7. 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.

    Review DB profile using database template

    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, from the Enterprise menu, select Provisioning and Patching, and then select Procedure Activity.

13.2.4.5 Creating a Database Provisioning Profile Using Export Schema Objects

To create a database provisioning profile, follow these steps:

  1. You can access the Database Provisioning page using either of the following ways:

    • From the Setup menu, select Cloud, and then select Database. On the Database Cloud Self Service Portal Setup, select Profiles and Service Templates. In the Profiles section, 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.

  2. On the Reference Target page, click the search icon to select a target.

    Reference Target page
  3. In the Search and Select:Targets display box, select the database you want to create a profile for, and then, click Select.

    Search and Select Targets display box
  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

    Reference Target page for 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.

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

      Content Options page

      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.

      Degree of Parallelism section

      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.
      Select Directory window

      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.

      Log subsection

      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 Profile page, do the following:

    • In the Profile Information section, enter a unique profile name of your choice.

      For example:
      Schema Objects Provisioning Profile for HR database
      

      You can also enter a description of the profile, and notes for your reference.

    • In the Schedule section, you can choose to start the profile creation immediately, or you can schedule it for a later time.

    • Click Next.

  8. 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, from the Enterprise menu, select Provisioning and Patching, and then select Procedure Activity.

13.2.4.6 Creating a Database Provisioning Profile Using Clone DB

To create a database provisioning profile, follow these steps:

  1. You can access the Database Provisioning page using either of the following ways:

    • From the Setup menu, select Cloud, and then select Database. On the Database Cloud Self Service Portal Setup, select Profiles and Service Templates. In the Profiles section, 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.

  2. On the Reference Target page, click the search icon to select a target.

    Reference Target page
  3. In the Search and Select:Targets display box, select the database you want to create a profile for, and then, click Select.

    Search and Select Targets display box
  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.

    • Create

    • RMAN Database Image

    Create provisioning profile using RMAN database image
  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.

    Credentials
  6. On the Content Options page, specify the backup location for the RMAN image mode. By default, the backup location selected is Offline Backup. You can choose Online Backup only if it is enabled.

    Then, select Directory for the backup location and enter the directory path, or select Fast Recovery Area, which already contains a backup location.

    Note:

    Ensure that the given location is accessible to the nodes in the database pool.

    Click Next.

  7. On the Profile page, do the following:

    • In the Profile Information section, enter a unique profile name of your choice.

      For example:
      RMAN Database Image for HR Database
      

      You can also enter a description of the profile, and notes for your reference.

    • In the Schedule section, you can choose to start the profile creation immediately, or you can schedule it for a later time.

    • Click Next.

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

    Review page for RMAN database image

    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, from the Enterprise menu, select Provisioning and Patching, and then select Procedure Activity.

13.2.5 Setting Up a Service Template

A service template is a standardized service definition that is offered to self service users to create databases or schemas. Self service users can create one or databases or schemas based on the service template definition. You can create a service template for:

The following figure shows a list of database profiles and service templates that have been created.

Figure 13-3 Profiles and Service Templates

Profiles and Service Templates

You can do the following:

13.2.5.1 Creating a Database Service Template

Service templates are standardized service definitions that allow self service users to create databases or schemas. Self service users can create one or more databases based on the service template definition. The service template can be based on:

  • Snap Clone Based Profile

  • RMAN Backup Based Profile

  • DBCA Template Based Profile

  • Clone DB Based Profile

13.2.5.1.1 Creating Service Template Using Snap Clone Profile

To create a snap clone based service template, follow these steps:

  1. Log into Enterprise Manager as a user with the EM_SSA_ADMINISTRATOR role. The EM_SSA_ADMINISTRATOR role you select must also have the EM_STORAGE_OPERATOR privileges.

  2. From the Setup menu, select Cloud, then select Database. The Database Cloud Self Service Portal Setup page appears.

  3. Click Profiles and Service Templates. From the Create menu, select For Database. The Create Service Template: General page appears.

    Figure 13-4 Create Service Template: General (Snap Clone)

    Create Service Template: General (Snap Clone)
  4. 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.

  5. Click the Search icon next to the Profile field and select a snap clone profile from the list.

  6. In the Database Definition region, specify the following:

    • Type: This can be Single Instance or Real Application Cluster (RAC). If you select RAC, specify the number of nodes.

    • Database SID: This is an optional field. You can select Specify Prefix or Specified by User at Request Time.

      • Specify Prefix: If you choose this option, enter a prefix that is to be used to generate a unique System Identifier (SID) at the time of database creation. The prefix helps to identify databases created using this service template. The prefix can be a maximum of 6 characters.

        The new database name generated will be based on the SID Prefix specified here. For example, if the prefix is specified as MYDB, the SID for the new database is generated as MYDB0000, MYDB0001, MYDB0002, and so on.

        For existing databases (running databases and in progress requests), a unique SID name is generated for single instance databases, or a unique name is generated for real application cluster databases. For example, if the existing SIDs running on a host are MYDB0000, MYDB0001, MYDB0002 And In progress are MYDB0003, MYDB0004, the new SID or database name generated for the new request is MYDB0005.

      • Specified by User at Request Time: If you choose this option, you can leave this field blank and specify the SID when you are making a database request.

    • Domain Name: This is an optional field. Enter a Domain Name to be used for the new database being created. You must ensure that the domain name does not contain a preceding "." (dot).

  7. In the Zones region, click Add to select a PaaS Infrastructure Zone into which the database instance is to be provisioned. Click Assign Pool. Select a pool from the list and assign this pool to the PaaS Infrastructure Zone. The database will be provisioned into this pool.

  8. After you have selected the zone and the pool, the host target is populated in the Reference Host field.

  9. Click Next. The Database Cloud Self Service Portal Setup: Database page appears.

    Figure 13-5 Create Service Template: Database (Snap Clone)

    Surrounding text describes Figure 13-5 .
  10. In the Reference Host region, the name of the PaaS Infrastructure zone, the database pool, and the reference host you have selected in the Database Cloud Self Service Portal Setup: General page are displayed.

    The database values such as a Automatic Storage Management (ASM) disk group, location of the file system, and listener port you select must be available on the reference host.

  11. Specify the following details:

    • Storage: You can configure the volumes that will be used by the database:

      • Mount Point Prefix: The mount point prefix can be the Same for All Volumes or Different for Each Volume.

        Specify the prefix for the new mount point for the database being provisioned. This value would be prefixed to an auto-generated mount point where a clone of this volume will be mounted. The volume will be mounted on /<mount-prefix>_<unique-suffix-generated-by-EM>/<source-path>. If the Mount Point Prefix is different for each volume, specify a different value for each volume,

      • Writable Space: The Writable Space can be the Same for All Volumes or Different for Each Volume.

        Specify the amount of space required for block changes. The value specified here cannot exceed the Storage Ceiling specified for the server. For example, for minimal data changes, you specify the value as 1% of the original volume size.

    • Snapshot Policy: Snapshots are sets of historical data for specific time periods. By default, Oracle Database automatically generates snapshots of the performance data once every hour and retains the statistics in the workload repository for 8 days. Select the Allow the user to take snapshots for the new database checkbox and specify the Maximum Number of Snapshots that can be taken.

      Snapshots can be created for a specific point in time. The number of snapshots is determined by the value specified by the self service administrator in the Maximum Number of Snapshots field. Once the snapshot has been taken, the database can be restored to a specific snapshot taken a particular point in time. For example, if there are several snapshots such as snap1, snap2, and snap3, if the database is restored to snap2, snap3 will be deleted.

    • In the Listener Port field, specify listener port number that is to be associated with the new database. If you have selected a 11.2 or later RAC database, you must specify the scan port number.

    • Administrator Credentials: Specify passwords for the system schemas of the new database. These schemas will not be available to the EM_SSA_USERS. You can choose to use the same password for all the schemas or different passwords for each schema. If these values are not specified, default values will be used and the EM_ADMINISTRATOR can change them.

    • Non Administrator Credentials: Apart from the system schemas, if you want to restrict access to other schemas, you can select them in the Non-Administrator Credentials region and specify the password.

  12. Click Next. The Create Service Template: Initialization Parameters page appears.

    Figure 13-6 Create Service Template: Initialization Parameters (Snap Clone)

    Create Service Template: Initialization Parameters
  13. 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: Scripts page appears. Specify the custom scripts that need to be executed before and after the database is created. See Section 16.2, "Pre and Post Request Creation / Deletion Scripts" for details.

  15. Click Next. The Create Service Template: Roles page appears.

    Figure 13-7 Create Service Template: Roles (Snap Clone)

    Create Service Template: Roles
  16. Click Add to select the 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.

  17. The Create Service Template: Review page appears. Click Create. The newly created service template will appear in the Database Cloud Self Service Portal Setup: Service Templates page.

13.2.5.1.2 Create Service Template Using RMAN Backup Profile
  1. Log into Enterprise Manager as a user with the EM_SSA_ADMINISTRATOR role.

  2. From the Setup menu, select Cloud, then select Database. The Database Cloud Self Service Portal Setup page appears.

  3. Click Profiles and Service Templates. From the Create menu, select For Database. The Create Service Template: General page appears.

    Figure 13-8 Create Service Template (RMAN Backup)

    Surrounding text describes Figure 13-8 .
  4. 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.

  5. Click the Search icon next to the Source Identification field and select a RMAN Backup profile from the list.

  6. In the Database Definition region, specify the following:

    • Type: This can be Single Instance or Real Application Cluster (RAC). If you select RAC, specify the Number of Nodes.

    • Database SID: This is an optional field. You can select Specify Prefix or Specified by User at Request Time.

      • Specify Prefix: If you choose this option, enter a prefix that is to be used to generate a unique System Identifier (SID) at the time of database creation. The prefix helps to identify databases created using this service template. The prefix can be a maximum of 6 characters.

        The new database name generated will be based on the SID Prefix specified here. For example, if the prefix is specified as MYDB, the SID for the new database is generated as MYDB0000, MYDB0001, MYDB0002, and so on.

        For existing databases (running databases and in progress requests), a unique SID name is generated for single instance databases, or a unique name is generated for real application cluster databases. For example, if the existing SIDs running on a host are MYDB0000, MYDB0001, MYDB0002 And In progress are MYDB0003, MYDB0004, the new SID or database name generated for the new request is MYDB0005.

      • Specified by User at Request Time: If you choose this option, you can leave this field blank and specify the SID when you are making a database request.

    • Domain Name: This is an optional field. Enter a Domain Name to be used for the new database being created. You must ensure that the domain name does not contain a preceding "." (dot).

    • Enable Standby Database: Select this checkbox if you want to provision standby databases using this service template. If this checkbox is selected, you have to add standby databases. See Section 13.2.5.3, "Creating a Service Template for Standby Databases" for details.

  7. In the Zones region, click Add to select a PaaS Infrastructure Zone into which the database instance is to be provisioned. Click Assign Pool. Select a pool from the list and assign this pool to the PaaS Infrastructure Zone. The database will be provisioned into this pool.

  8. After you have selected the zone and the pool, the host target is populated in the Reference Host field.

  9. Specify a Shared Location and click Next.

  10. In the Listener Port field, specify listener port number that is to be associated with the new database. If you have selected a 11.2 or later RAC database, you must specify the scan port number. Click Next. The Create Service Template: Database page appears.

    Figure 13-9 Create Service Template: Database (RMAN Backup)

    Create Service Template: Database (RMAN Backup)
  11. In the Reference Host region, the name of the PaaS Infrastructure zone, the database pool, and the reference host you have selected in the Database Cloud Self Service Portal Setup: General page are displayed.

    The database values such as a Automatic Storage Management (ASM) disk group, location of the file system, and listener port you select must be available on the reference host.

  12. Specify the following:

    • Storage Type: This can be:

      • Automatic Storage Management: The Oracle Automatic Storage Management (ASM) is a volume manager and a file system for database files that supports single-instance and RAC configurations. ASM groups the disks in your storage system into one or more disk groups. If you select ASM, select the Disk Group here.

      • File System: The Oracle Database File System creates a standard file system interface on top of files and directories that are stored in database tables. If you select this option, you must specify or select the Location of the File System.

    • Fast Recovery (Optional): To simplify the management of backup and recovery files, you can create a fast recovery area for your database. Select the Enable Fast Recovery Area checkbox to specify the location in which recovery related files must be stored. The fast recovery area can be a ASM disk group or a file system that provides a centralized disk location for backup and recovery file. Specify the location of the Fast Recovery Area and the Fast Recovery Size. The amount of disk space to allocate for the fast recovery area depends on the size and activity levels of your database.

      Select the Enable Archiving check box if the backups are to be archived.

  13. In the Listener Port field, specify listener port number that is to be associated with the new database. If you have selected a 11.2 or later RAC database, you must specify the scan port number.

  14. Specify the Administrator Credentials. Specify passwords for the system schemas of the new database. These schemas will not be available to the EM_SSA_USERS. You can choose to use the same password for all the schemas or different passwords for each schema. If these values are not specified, default values will be used and the EM_ADMINISTRATOR can change them.

  15. Apart from the system schemas, if you want to restrict access to other schemas, you can select them in the Non-Administrator Credentials region and specify the password. These schemas will be locked and the EM_SSA_USERS cannot access them. Click Next.

  16. Follow steps 10 to 17 in the Section 13.2.5.1.1, "Creating Service Template Using Snap Clone Profile" section to create the RMAN Backup based service template.

13.2.5.1.3 Create Service Template Using DBCA Template Profile
  1. Log into Enterprise Manager as a user with the EM_SSA_ADMINISTRATOR role.

  2. From the Setup menu, select Cloud, then select Database. The Database Cloud Self Service Portal Setup page appears.

  3. Click Profiles and Service Templates. From the Create menu, select For Database. The Create Service Template: General page appears.

    Figure 13-10 Create Service Template: General (DBCA Template)

    Create Service Template: General (DBCA Template)
  4. 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.

  5. Click the Search icon next to the Source Identification field and select a DBCA template based profile from the list.

  6. In the Database Definition region, specify the following:

    • Type: This can be Single Instance or Real Application Cluster (RAC). If you select RAC, specify the Number of Nodes.

    • Database SID: This is an optional field. You can select Specify Prefix or Specified by User at Request Time.

      • Specify Prefix: If you choose this option, enter a prefix that is to be used to generate a unique System Identifier (SID) at the time of database creation. The prefix helps to identify databases created using this service template. The prefix can be a maximum of 6 characters.

        The new database name generated will be based on the SID Prefix specified here. For example, if the prefix is specified as MYDB, the SID for the new database is generated as MYDB0000, MYDB0001, MYDB0002, and so on.

        For existing databases (running databases and in progress requests), a unique SID name is generated for single instance databases, or a unique name is generated for real application cluster databases. For example, if the existing SIDs running on a host are MYDB0000, MYDB0001, MYDB0002 And In progress are MYDB0003, MYDB0004, the new SID or database name generated for the new request is MYDB0005.

      • Specified by User at Request Time: If you choose this option, you can leave this field blank and specify the SID when you are making a database request.

    • Domain Name: This is an optional field. Enter a Domain Name to be used for the new database being created. You must ensure that the domain name does not contain a preceding "." (dot).

    • Enable Standby Database: Select this checkbox if you want to provision standby databases using this service template. If this checkbox is selected, you have to add standby databases. See Section 13.2.5.3, "Creating a Service Template for Standby Databases" for details.

  7. In the Zones region, click Add to select a PaaS Infrastructure Zone into which the database instance is to be provisioned. Click Assign Pool. Select a pool from the list and assign this pool to the PaaS Infrastructure Zone. The database will be provisioned into this pool.

  8. After you have selected the zone and the pool, the host target is populated in the Reference Host field.

  9. Click Next. The Create Service Template: Database page appears.

    Figure 13-11 Create Service Template: Database (DBCA Template)

    Create Service Template: Database (DBCA Template)
  10. In the Reference Host region, the name of the PaaS Infrastructure zone, the database pool, and the reference host you have selected in the Database Cloud Self Service Portal Setup: General page are displayed.

    The database values such as a Automatic Storage Management (ASM) disk group, location of the file system, and listener port you select must be available on the reference host.

  11. Specify the following:

    • Storage Type: This can be:

      • Automatic Storage Management: The Oracle Automatic Storage Management (ASM) is a volume manager and a file system for database files that supports single-instance and RAC configurations. ASM groups the disks in your storage system into one or more disk groups. If you select ASM, select the Disk Group here.

      • File System: The Oracle Database File System creates a standard file system interface on top of files and directories that are stored in database tables. If you select this option, you must specify or select the Location of the File System.

    • Fast Recovery (Optional): To simplify the management of backup and recovery files, you can create a fast recovery area for your database. Select the Enable Fast Recovery Area checkbox to specify the location in which recovery related files must be stored. The fast recovery area can be a ASM disk group or a file system that provides a centralized disk location for backup and recovery file. Specify the location of the Fast Recovery Area and the Fast Recovery Size. The amount of disk space to allocate for the fast recovery area depends on the size and activity levels of your database.

      To allow self service users to schedule backups and perform restore operations, configure a Fast Recovery Area and select the Enable Archiving check box.

  12. In the Listener Port field, specify listener port number that is to be associated with the new database. If you have selected a 11.2 or later RAC database, you must specify the scan port number.

  13. Specify the Administrator Credentials. Specify passwords for the system schemas of the new database. These schemas will not be available to the EM_SSA_USERS. You can choose to use the same password for all the schemas or different passwords for each schema. If these values are not specified, default values will be used and the EM_ADMINISTRATOR can change them.

  14. Apart from the system schemas, if you want to restrict access to other schemas, you can select them in the Non-Administrator Credentials region and specify the password. These schemas will be locked and the EM_SSA_USERS cannot access them. Click Next.

  15. Follow steps 10 to 17 in the Section 13.2.5.1.2, "Create Service Template Using RMAN Backup Profile" section to create the DBCA service template.

13.2.5.1.4 Creating a Service Template Using CloneDB Profile

CloneDB allows you to clone a database multiple times without copying the data into different locations. Instead Oracle Database creates the files in the Clone DB database using copy-on-write technology, so that only the blocks that are modified in the Clone DB database require additional storage on disk. Clone DB reduces the amount of storage required for testing purposes and enables rapid creation of multiple database clones. Clone DB is supported for database 11.2.0.3 or later versions.

To use the Clone DB feature, the following requirements must be met:

  • Each CloneDB database must use Direct NFS Client, and the backup of the production database must be located on an NFS volume. Direct NFS Client enables an Oracle database to access network attached storage (NAS) devices directly, rather than using the operating system kernel NFS client.

  • DNFS library must be enabled in all Oracle Home in the Database Pool. To enable the DNFS library, enter the following commands:

    $ cd $ORACLE_HOME/rdbms/lib

    $ make -f ins_rdbms.mk dnfs_on

  • The data file cannot be of the ASM type.

  • The file system location must be an NFS only location.

    Note: If the database version is 12.1.0.2, the data file can be present on any local location.

  1. Log into Enterprise Manager as a user with the EM_SSA_ADMINISTRATOR role.

  2. From the Setup menu, select Cloud, then select Database. The Database Cloud Self Service Portal Setup page appears.

  3. Click Profiles and Service Templates. From the Create menu, select For Database. The Create Service Template: General page appears.

    Figure 13-12 Create Service Template: General (CloneDB)

    Surrounding text describes Figure 13-12 .
  4. 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.

  5. Click the Search icon next to the Profile field and select an RMAN Image profile from the list.

  6. In the Database Definition region, specify the following:

    • Create: You can either create a CloneDB Database or a Full Copy of the Database.

      • CloneDB: If you select this option, then each file is copied as an image copy which is a bit-for-bit copy of a database file created on disk. Image copies are identical to copies created with operating system commands such as cp on Linux or COPY on Windows, but are recorded in the RMAN repository and so are usable by RMAN. This option allows you reduce the amount of storage and enables rapid creation of multiple database clones.

      • Full Copy of the Database: You can create a full online or offline backup copy of the database.

        If you are doing an online backup, you must ensure that your Test Master database is in ARCHIVELOG mode and that all of the necessary archived redo log files are saved and accessible to the CloneDB database environment.

        If you are doing an offline backup, you must ensure that the backup copies are accessible to the CloneDB database environment.

    • Type: This can be Single Instance or Real Application Cluster (RAC). If you select RAC, specify the Number of Nodes.

    • Database SID: This is an optional field. You can select Specify Prefix or Specified by User at Request Time.

      • Specify Prefix: If you choose this option, enter a prefix that is to be used to generate a unique System Identifier (SID) at the time of database creation. The prefix helps to identify databases created using this service template. The prefix can be a maximum of 6 characters.

        The new database name generated will be based on the SID Prefix specified here. For example, if the prefix is specified as MYDB, the SID for the new database is generated as MYDB0000, MYDB0001, MYDB0002, and so on.

        For existing databases (running databases and in progress requests), a unique SID name is generated for single instance databases, or a unique name is generated for real application cluster databases. For example, if the existing SIDs running on a host are MYDB0000, MYDB0001, MYDB0002 And In progress are MYDB0003, MYDB0004, the new SID or database name generated for the new request is MYDB0005.

      • Specified by User at Request Time: If you choose this option, you can leave this field blank and specify the SID when you are making a database request.

    • Domain Name: This is an optional field. Enter a Domain Name to be used for the new database being created. You must ensure that the domain name does not contain a preceding "." (dot).

  7. In the Pools and Zones region, click Add to select a PaaS Infrastructure Zone into which the database instance is to be provisioned. Click Assign Pool. Select a pool from the list and assign this pool to the PaaS Infrastructure Zone. The database will be provisioned into this pool.

  8. After you have selected the zone and the pool, the host target is populated in the Reference Host field.

  9. Specify a Shared Location and click Next. If you have chosen to create a CloneDB database, the following page is displayed.

    Figure 13-13 Create Service Template: Database (CloneDB)

    Surrounding text describes Figure 13-13 .
  10. In the Reference Host region, the name of the PaaS Infrastructure zone, the database pool, and the reference host you have selected in the Database Cloud Self Service Portal Setup: General page are displayed.

  11. In the Location field, specify the location for the database files. This must be an NFS location.

  12. To simplify the management of backup and recovery files, you can optionally create a fast recovery area for your database. Select the Enable Fast Recovery Area checkbox to specify the location in which recovery related files must be stored. The fast recovery area can be a file system that provides a centralized disk location for backup and recovery file. Specify the location of the Fast Recovery Area and the Fast Recovery Size. The amount of disk space to allocate for the fast recovery area depends on the size and activity levels of your database.

    To allow self service users to schedule backups and perform restore operations, configure a Fast Recovery Area and select the Enable Archiving check box.

  13. If you have chosen to create a CloneDB database, you can optionally allow the user to take a backup copy of the database. Select the Allow the user to take backup copy for the new database checkbox. Specify the maximum number of backups allowed and the backup location.

  14. In the Listener Port field, specify listener port number that is to be associated with the new database. If you have selected a 11.2 or later RAC database, you must specify the scan port number.

  15. Specify the Administrator Credentials. Specify passwords for the system schemas of the new database. These schemas will not be available to the EM_SSA_USERS. You can choose to use the same password for all the schemas or different passwords for each schema. If these values are not specified, default values will be used and the EM_ADMINISTRATOR can change them.

  16. Apart from the system schemas, if you want to restrict access to other schemas, you can select them in the Non-Administrator Credentials region and specify the password. These schemas will be locked and the EM_SSA_USERS cannot access them. Click Next.

    Note:

    If you have chosen to create a full copy of the database, follow the steps 11 to 16 listed in Section 13.2.5.1.2, "Create Service Template Using RMAN Backup Profile".
  17. Follow steps 10 to 17 in the Section 13.2.5.1.1, "Creating Service Template Using Snap Clone Profile" section to create the CloneDB profile based service template.

13.2.5.2 Creating a Service Template for PDB as a Service

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:

  1. Log into Enterprise Manager as a user with the EM_SSA_ADMINISTRATOR role.

  2. From the Setup menu, select Cloud, then select Database. The Database Cloud Self Service Portal Setup page appears.

  3. Click Profiles and Service Templates. In the Service Templates region, select For Pluggable Database from the Create menu. The Create Service Template: Name page appears.

    Figure 13-14 Create Service Template: General (PDB)

    Surrounding text describes Figure 13-14 .
  4. 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.

  5. In the Pluggable Databases region, you can choose to:

    • Create Empty Pluggable Database: Select this option to create an empty PDB that can be configured by the user.

    • Create Pluggable Databases from Profile: Select a database provisioning profile from which the schema is to be imported. Click the Search icon next to the Profile field and select an export schema objects based profile from the list. If a profile does not exist, you must create one. See Section 13.2.4.5, "Creating a Database Provisioning Profile Using Export Schema Objects".

      Note:

      Apart from these two options, 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.

  6. In the 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.
  7. 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.

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

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

  10. Click Next. The Create New Service Template: Configurations page appears.

    Figure 13-15 Create Service Template: Configurations (PDB)

    Surrounding text describes Figure 13-15 .

    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: If you have selected the Create Pluggable Databases from Profile option, the list of tablespaces are displayed.

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

    Figure 13-16 Create Service Template: Initialization Parameters (PDB)

    Surrounding text describes Figure 13-16 .
  12. Click Next. The Create Service Template: Scripts page appears. On this page, you can optionally specify the following:

    • Custom scripts that need to be executed before or after the PDB has been created.

    • Custom scripts that need to be executed before or after the PDB has been deleted.

    See Section 16.2, "Pre and Post Request Creation / Deletion Scripts" for details.

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

  14. Click Next. The Create Service Template: Review page appears where you can review the details entered so far.

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

13.2.5.3 Creating a Service Template for Standby Databases

Service templates are standardized service definitions that allow self service users to create standby databases. Self service users can create one or more standby databases based on the service template definition. To create a database service template, follow these steps:

  1. Log into Enterprise Manager as a user with the EM_SSA_ADMINISTRATOR role.

  2. From the Setup menu, select Cloud, then select Database. The Database Cloud Self Service Portal Setup page appears.

  3. Click Profiles and Service Templates. From the Create menu, select For Database. The Create Service Template: General page appears.

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

  5. Click the Search icon next to the Profile field and select a database provisioning profile.

  6. You can select the following types of profiles:

    • RMAN Backup Based Database Provisioning Profile.

    • DBCA Template Based Database Provisioning Profile.

  7. In the Database Definition region, specify the following:

    • Type: This can be Single Instance or Real Application Cluster (RAC). If you select RAC, specify the Number of Nodes.

    • Database SID: This is an optional field. You can select Specify Prefix or Specified by User at Request Time.

      • Specify Prefix: If you choose this option, enter a prefix that is to be used to generate a unique System Identifier (SID) at the time of database creation. The prefix helps to identify databases created using this service template. The prefix can be a maximum of 6 characters.

        The new database name generated will be based on the SID Prefix specified here. For example, if the prefix is specified as MYDB, the SID for the new database is generated as MYDB0000, MYDB0001, MYDB0002, and so on.

        For existing databases (running databases and in progress requests), a unique SID name is generated for single instance databases, or a unique name is generated for real application cluster databases. For example, if the existing SIDs running on a host are MYDB0000, MYDB0001, MYDB0002 And In progress are MYDB0003, MYDB0004, the new SID or database name generated for the new request is MYDB0005.

      • Specified by User at Request Time: If you choose this option, you can leave this field blank and specify the SID when you are making a database request.

    • Domain Name: This is an optional field. Enter a Domain Name to be used for the new database being created. You must ensure that the domain name does not contain a preceding "." (dot).

    • Enable Standby Database: Select this checkbox if you want to provision standby databases using this service template. The database lock icon and the Add Standby Database region appears. Click the database lock icon to lock the database. This forces the self service user to request standby databases. If unlocked, the self service user can deselect the standby database while submitting the database request.

    Figure 13-17 Create Service Template: General (Standby Database)

    Surrounding text describes Figure 13-17 .
  8. Click Add Standby Database. In the Add Standby Database window that appears, specify the following details:

    Figure 13-18 Add Standby Database

    Add Standby Database
    • Standby Name: The name used to identify the standby database.

    • Type: This can be Single Instance or Real Application Cluster (RAC). If you select RAC, you must specify the Number of Nodes.

    • Standby Domain Name: Enter a domain name for the new standby database that is to be created.

    • Standby Protection Mode: Specify the protection mode which can be:

      • Maximize Protection: Provides the highest level of data protection with no data loss. If this mode is selected, you must set the SYNC Redo Transport Mode on at least one standby database.

      • Maximize Availability: Provides very high data protection. If this mode is selected, you must set the SYNC Redo Transport Mode on at least one standby database.

      • Maximize Performance: Provides high data protection with the ASYNC Redo Transport Mode. If you select this mode, there is no performance impact on the primary database.

    • Enable Real Time Query: Select this option to enable real time data query on the database. This feature requires an active data guard license.

    • Apply Delay: Specifies the delay period before which the archived redo log data is applied on the standby database. When the property is set to 0 minutes, the redo log data is applied immediately on the standby database.

    Note:

    You can use a single service template to provision multiple standby databases.
  9. In the Pools and Zones (Primary Pools) region, click Add to add one or more PaaS Infrastructure zones into which the database instance is to be provisioned. Click Assign Pool and select a database pool which will be the primary database pook for the standby database.

  10. In the Standby Pools region, you will see the list of standby databases that you have defined. From the drop down list, select the standby pool with which the standby database is to be associated. You can associate multiple standby pools with one primary pool.

    Note:

    If the Primary Pool is of single instance type, both single instance and RAC database pools are listed. But if the Primary Pool is RAC, only RAC database pools are listed in the Standby Pools region.

    Figure 13-19 Create Service Template: General (Standby Database­)

    Surrounding text describes Figure 13-19 .
  11. Click Search in the Reference Host field to select a host target.

  12. Specify the Shared Location and click Next to continue to the Database Cloud Self Service Portal Setup: Database page.

  13. The name of the Zone, Pool, and Reference Host you have selected is displayed. You can select the ASM Disk Group, File System Location, and Listener Port that is available on the Reference Host.

    • Storage Type: Storage type can be:

      • Automatic Storage Management: The Oracle Automatic Storage Management (ASM) is a volume manager and a file system for database files that supports single-instance and RAC configurations. ASM groups the disks in your storage system into one or more disk groups. If you select ASM, specify the Disk Group here.

      • File System: The Oracle Database File System creates a standard file system interface on top of files and directories that are stored in database tables. If you select this option, you must specify the Location of the File System.

    • Fast Recovery: To simplify the management of backup and recovery files, you can create a fast recovery area for your database. The fast recovery area can be a ASM disk group or a file system that provides a centralized disk location for backup and recovery file. Specify the location of the Fast Recovery Area and the Fast Recovery Size. The amount of disk space to allocate for the fast recovery area depends on the size and activity levels of your database.

      To allow self service users to schedule backups and perform restore operations, configure a Fast Recovery Area and select the Enable Archiving check box.

  14. In the Port Number field, specify listener port number that is to be associated with the new database. If you have selected a 11.2 or later RAC database, you must specify the scan port number.

  15. In the Location fields, specify the RMAN Duplicate Backup location. This directory must be present on all members of the Primary and Standby pools. The free space available in this location must be equal to or more than the size of the database from which the profile has been created.

  16. Specify the Administrator Credentials. Specify passwords for the system schemas of the new database. These schemas will not be available to the EM_SSA_USERS. You can choose to use the same password for all the schemas or different passwords for each schema. If these values are not specified, default values will be used and the EM_ADMINISTRATOR can change them.

  17. Apart from the system schemas, if you want to restrict access to other schemas, you can select them in the Non-Administrator Credentials region and specify the password. These schemas will be locked and the EM_SSA_USERS cannot access them.

  18. Click Next. The Database Cloud Self Service Portal Setup: 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.

  19. Click Next. The Database Cloud Self Service Portal Setup: Scripts page appears. Specify the custom scripts that need to be executed before and after the database is created.

  20. Click Next. The Database Cloud Self Service Portal Setup: Roles page appears. Click Add to select the SSA user roles to which this service template will be available. All users belonging to the selected role can use this service template.

  21. Click Next. The Database Cloud Self Service Portal Setup: Review page appears. Review the information you have entered so far and click Create. 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.

13.2.5.4 Creating a Service Template for Schema as a Service

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

  1. Log into Enterprise Manager as a user with the EM_SSA_ADMINISTRATOR role.

  2. From the Setup menu, select Cloud, then select Schema. The Database Cloud Self Service Portal Setup page appears.

  3. Click Profiles and Service Templates. In the Service Templates region, select For Schema from the Create menu. The Create Service Template: Name page appears.

    Figure 13-20 Create Service Template: Name (Schema)

    Create New Service Template: Name
  4. 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.

  5. In the Source region, you can choose to:

    • Create User Defined Schemas: Select this option to create empty schemas which can be configured by the user. If you select this option, you can specify the Maximum Number of Schemas that can be created.

    • Import Schemas from Profile: Select a database provisioning profile from which the schema is to be imported. Click the Search icon next to the Profile field and select an export schema objects based profile from the list. If a profile does not exist, you must create one. See Section 13.2.4.5, "Creating a Database Provisioning Profile Using Export Schema Objects".

      • Master Account: If you select the Import Schemas from Profile option, you must select the Master Account that has privileges on all the schemas. If the Master Account is not selected, the EM_SSA_USER will select it when requesting a schema.

  6. In the Zones region, click Add to select a PaaS Infrastructure Zone into which the service instance is to be provisioned. Click Assign Pool to add a Database Pool for the zone.

  7. After you have selected the zone and the pool, the host target is populated in the Reference Host field. If you have added multiple zones and pools, you must click the Search icon and select a host target from the list.

  8. If you creating a service template based on an export schema objects profile, in the Shared Location region, specify the Path or the Shared Location in which the schema dumps are present. The Shared Location must be accessible by all the databases.

  9. Click Next. The Create New Service Template: Configurations page appears. Specify the following details:

    • Workload Size: Workload represents the total CPU, memory, and storage requirements for each service. You can define workload sizes such as small, medium, and large for the schema service. Click Create and in the Create Workload window, enter the name, CPU, Memory, and Storage limit for each service. Select a workload size and click Default to designate it as the default workload size.

    • Assign Schema Privileges: You can select existing roles or create a role that will be assigned to all the schemas. All database privileges such as CREATE_SESSION, CREATE DIMENSION, and so on can be granted to the role. Enter the name of the user, description, and the privileges that will be granted to the user.

      Note:

      • If the role with the name specified already exists in the database, the database privileges cannot be modified.

      • The Master Account will have the CREATE SESSION, CREATE DIMENSION, CREATE INDEXTYPE, CREATE OPERATOR, CREATE PROCEDURE, CREATE SEQUENCE, CREATE TABLE, CREATE TRIGGER, CREATE TYPE, CREATE VIEW, and CREATE SYNONYM privileges over all the schemas created as part of this service request.

    • Tablespace: Specify the tablespace storage configuration. Enter the following details:

      • Maximum Size: The maximum size of the tablespace can be Unlimited or Specified by the workload size selected at request time.

      • Auto Extend: Select this check box to automatically extend the new data file.

        Note:

        If you are creating an empty schema, the tablespaces are not listed in the Tablespace Details section. In this case, you must specify the Initial Size and the Increment value for the tablespace and only one tablespace is created.
    • Tablespace Details: Based on the profile you have selected, one or more tablespaces are listed here. You can edit the following values in the table:

      • Initial Size: If you selected Specified by the workload size selected at request time in the Maximum Size field, enter the initial size of the tablespace.

      • Increment: If you have selected the Auto Extend checkbox, specify the size by which the data file is to be automatically incremented.

      • Maximum Size: If the tablespace storage is Specified by workload size specified at request time, enter the maximum size here that can be distributed across tablespaces.

  10. Click Next. The Create Service Template: Scripts page appears. Specify the custom scripts that need to be executed before and after the service instance has been created. See Pre and Post Scripts section for details.

    Figure 13-21 Create Service Template: Scripts (Schema)

    Create Service Template: Scripts Page
  11. Click Next. The Create Service Template: Roles page appears. Click Add to select the SSA user roles to which this service template will be available. All users belonging to the selected role can use this service template.

  12. Click Next to go to the Review page. Review the details entered so far and 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.

13.2.5.5 Making a Copy of an Existing Database Service Template

You can make a copy of an existing database service template. To do so, follow these steps:

  1. Log into Enterprise Manager as a user with the EM_SSA_ADMINISTRATOR role.

  2. From the Setup menu, select Cloud, then select Database. The Database Self Service Portal Setup page appears.

  3. Click Profiles and Service Templates. Select a template from the list and click Create Like.

  4. Follow the steps of the Create Like wizard to make a copy of the selected template.

13.2.5.6 Editing Database Service Template

You can modify an existing database service template. To do so, follow these steps:

  1. Log into Enterprise Manager as a user with the EM_SSA_ADMINISTRATOR role.

  2. From the Setup menu, select Cloud, then select Database. The Database Self Service Portal Setup page appears.

  3. Click Profiles and Service Templates. Select a template from the list and click Edit.

  4. Follow the steps of the Edit wizard to make a copy of the selected template.

Note:

You can select a different profile for the template only if the selected profile is for the same database.

13.2.5.7 Deleting a Database Service Template

  1. Log into Enterprise Manager as a user with the EM_SSA_ADMINISTRATOR role.

  2. From the Setup menu, select Cloud, then select Database. The Database Self Service Portal Setup page appears.

  3. Click Profiles and Service Templates. Select a template from the list and click Delete.

  4. A confirmation message is displayed. Click OK to confirm. The selected service template will be deleted.

13.2.6 Configuring Chargeback

Click the Chargeback tab to add the database pools to the Chargeback Application. On this page, you can determine chargeback zones, services, items and prices. After the Chargeback is setup, you can view charges and plan details. For more details on setting up the Chargeback Service, see Section 26, "Chargeback Administration".

13.3 Provisioning Databases Using Database Template

You can create database (DBCA) templates that can be used to provision single instance, RAC, and standby databases.

Table 13-1 Provisioning Databases Using DBCA Template

Step Task Role

1

Follow the steps in the Getting Started section to enable DBaaS.

See Section 12.2, "Getting Started"

2

Set up one or more PaaS Infrastructure Zones.

See Section 10.3, "Creating a PaaS Infrastructure Zone"

3

Create a database pool.

See Section 13.2.1, "Creating a Database Pool"

4

Configure the request settings.

See Section 13.2.2, "Configuring Request Settings"

5

Define quotas for each self service user.

See Section 13.2.3, "Setting Up Quotas"

6

Create a DBCA template based database provisioning profile.

See Section 13.2.4.4, "Creating a Database Provisioning Profile Using Database Template"

7

Create a service template based on the profile you have created.

See Section 13.2.5.1.3, "Create Service Template Using DBCA Template Profile"

8

Configure the Chargeback Service.

See Section 26, "Chargeback Administration"

9

While deploying a database, select the service template (associated with the DBCA template based profile) you have created.

See Section 14.2, "Requesting Databases, Pluggable Databases, and Schemas"


13.3.1 Provisioning Standby Databases

A data guard configuration consists of one primary database and one or more standby databases. The databases in a Data Guard configuration are connected by Oracle Net and may be dispersed geographically. There are no restrictions on where the databases are located, provided they can communicate with each other.

Oracle Data Guard ensures high availability, data protection, and disaster recovery for enterprise data. It provides a comprehensive set of services that create, maintain, manage, and monitor one or more standby databases to enable production Oracle databases to survive disasters and data corruptions. Oracle Data Guard maintains these standby databases as copies of the production database. If the production database becomes unavailable due to a planned or an unplanned outage, the Oracle Data Guard can switch any standby database to the production role, minimizing the downtime associated with the outage.

The production database, also referred to as the primary database an be either a single-instance Oracle database or an Oracle Real Application Clusters (RAC) database. A standby database is a transactionally consistent copy of the primary database. Using a backup copy of the primary database, you can create one or more standby databases and incorporate them in a Data Guard configuration. Using Enterprise Manager Database as a Service, users with the EM_SSA_ADMINISTRATOR role can setup the DBaaS Cloud with single instance of RAC standby databases.

Table 13-2 Provisioning Standby Databases

Step Task Role

1

Follow the steps in the Getting Started section to enable DBaaS.

See Section 12.2, "Getting Started"

2

Set up one or more PaaS Infrastructure Zones.

See Section 10.3, "Creating a PaaS Infrastructure Zone"

3

Define a database pool for provisioning standby databases.

See Section 13.3.1.1, "Defining Database Pools for Provisioning Standby Databases"

4

Configure the request settings.

See Section 13.2.2, "Configuring Request Settings"

5

Define quotas for each self service user.

See Section 13.2.3, "Setting Up Quotas"

6

Create either of the following types of profiles:

DBCA template based database provisioning profile.

RMAN Backup based database provisioning profile.

See Section 13.2.4.4, "Creating a Database Provisioning Profile Using Database Template".

See Section 13.2.4.2, "Creating a Database Provisioning Profile Using RMAN Backup"

7

Create a service template based on the profile you have created.

See Section 13.2.5.3, "Creating a Service Template for Standby Databases"

8

Configure the Chargeback Service.

See Section 26, "Chargeback Administration"

9

While deploying a database, select the service template (associated with the DBCA template based profile) you have created. Additionally, you can also specify the standby database information while requesting the database.

See Section 14.2, "Requesting Databases, Pluggable Databases, and Schemas"


13.3.1.1 Defining Database Pools for Provisioning Standby Databases

A Data Guard configuration consists of one production database and one or more standby databases. To define a database pool for provisioning standby databases, you must follow these steps:

  1. Create a database pool and designate it as the primary database pool. See Section 13.2.1, "Creating a Database Pool".

  2. Create a standby database pool that contains standby databases. See Section 13.3.1.1.1, "Creating a Database Pool to Host Standby Databases".

  3. Associate the standby database pool with the primary database pool. See Section 13.3.1.1.2, "Associating a Standby Database Pool with a Primary Database Pool"

13.3.1.1.1 Creating a Database Pool to Host Standby Databases

A standby database pool must contain one or more physical standby databases. To create a database pool that contains one or more standby databases, follow these steps:

  1. Log into Enterprise Manager as a user with the EM_SSA_ADMINISTRATOR role.

  2. From the Setup menu, select Cloud, then select Database. The Database Cloud Self Service Portal Setup page appears.Click the Database Pools link. In the Database Pools region, select For Database from the Create menu.

    Figure 13-22 Create Pool for Standby Database

    Surrounding text describes Figure 13-22 .
  3. Enter a name and description for the database pool.

  4. In the Credentials region, specify the following credentials:

    • Host: Required for creating and starting the database.

    • Root: This is an optional field. It is required if you plan to use this database pool for database requests based on snap clone profile. See Section 13.6, "Using Snap Clone to Provision Databases".

    • Grid Infrastructure: This is an optional field. It is required if you plan to use this database pool for live cloning using of a database using ASM.

  5. Specify the following details:

    • PaaS Infrastructure Zone: Select the PaaS Infrastructure Zone on which the database instance is to be provisioned.

    • Database Configuration: Specify the configuration of the database being provisioned. This can be Single Instance or Cluster Database (RAC).

    • Platform and Version: Specify the platform and version of the database being deployed.

  6. Click Add and select one or more Oracle Homes to be added to the database pool.

  7. In the Maximum Number of Database Instances (per host), enter the maximum number of database instances that can be running on each host in the pool.

    Note:

    For RAC databases. the value specified in this field is used to ensure that the nodes on which the database is be created meet the instance criteria.
  8. Click Submit to create a database pool for standby databases. The newly created pool will appear in the Database Cloud Self Service Portal Setup: Database Pools page.

13.3.1.1.2 Associating a Standby Database Pool with a Primary Database Pool

To include standby support, you must add one or more pre-created database pools on which the standby databases will be created by following these steps:

  1. Log into Enterprise Manager as a user with the EM_SSA_ADMINISTRATOR role.

  2. From the Setup menu, select Cloud, then select Database. The Database Cloud Self Service Portal Setup page appears.Click the Database Pools link. Select the database pool that has been designated as the primary database pool and click Edit. The Edit Pool: Setup page appears.

    Figure 13-23 Edit Database Pool

    Surrounding text describes Figure 13-23 .
  3. The pool details and the Oracle homes in the pool are displayed. You can now add one or more standby database pools and associate it with the primary database pool. Click Add in the Standby Pools region. The Add Standby Pools window appears.

    Figure 13-24 Add Standby Pools

    Surrounding text describes Figure 13-24 .
  4. Select one or more standby pools and click Select. The selected pools appear in the Standby Pools region. These pools are now associated with the primary database pool and can be used to provision standby databases.

    Note:

    The primary database pool and the standby pool must meet the following conditions:
    • They must both be present in the same PaaS Infrastructure Zone.

    • The OS user name and password for the primary and standby pool must be the same.

  5. Specify the Placement Constraints that will allow the self service administrator to set the maximum limits for resource utilization. For example, if you are using the database pool to provision standby databases, you can specify a higher value in the Maximum Number of Database Instances Per Host field, since the standby database may not used for active operations all the time.

  6. Click Submit. The primary pool is now associated with the standby database pool and can be used to provision standby databases.

13.4 Provisioning Schemas

Enterprise Manager Schema as a Service feature allows you to create one or more schemas on a running database.

Table 13-3 Provisioning Schemas

Step Task Role

1

Follow the steps in the Getting Started section to enable DBaaS.

See Section 12.2, "Getting Started"

2

Set up one or more PaaS Infrastructure Zones.

See Section 10.3, "Creating a PaaS Infrastructure Zone"

3

Define a database pool for schema as a service.

See Section 13.4.1, "Creating a Database Pool for Schema as a Service"

4

Configure the request settings.

See Section 13.2.2, "Configuring Request Settings"

5

Define quotas for each self service user.

See Section 13.2.3, "Setting Up Quotas"

6

Create a database provisioning profile. This step is optional and is required if you are importing schemas from a profile.

See Section 13.2.4.5, "Creating a Database Provisioning Profile Using Export Schema Objects"

7

Create a service template based on:

  • User Defined Schema: In this case, the service template is created with an empty schema.

  • Schema 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 Section 13.2.5.4, "Creating a Service Template for Schema as a Service"

8

Configure the Chargeback Service.

See Section 26, "Chargeback Administration"

9

Create the schema based on the service template.

See Section 14.2, "Requesting Databases, Pluggable Databases, and Schemas"


13.4.1 Creating a Database Pool for Schema as a Service

You can create a database service with one or more schemas with or without seed data and database objects. To do so, follow these steps:

  1. Log into Enterprise Manager as a user with the EM_SSA_ADMINISTRATOR role.

  2. From the Setup menu, select Cloud, then select Database. The Database Cloud Self Service Portal Setup page appears.

    Figure 13-25 Create Database Pool (Schema as a Service)

    Surrounding text describes Figure 13-25 .
  3. From the Create menu, select For Schema.

  4. Enter a name and description for the database pool.

  5. In the Credentials region, specify the credentials that will be used for performing database operations. Specify the following credentials:

    • Host: Required for starting the database.

    • Database: Required for creating schemas on the database. The database credentials must have SYSDBA privileges.

    • Grid Infrastructure: Required for cluster databases.

  6. Specify the following details:

    • PaaS Infrastructure Zone: Select the PaaS Infrastructure Zone in which the databases are present. The schemas will be created on the databases selected for the pool.

    • Target Type: Specify the configuration of the target database on which the schema 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.

  7. Click Add and select one or more 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.
  8. Click Next. The Create New Pool: Policies page appears.

    Figure 13-26 Create Database Pool: Policies (Schema as a Service)

    Surrounding text describes Figure 13-26 .

    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:

    • Services: If you select this check box, you must specify the Maximum Number of Database Services that can be running on each database.

    • Workloads Associated with Service Requests: The amount of resources (such as CPU and memory) to manage the workload can be specified here. Specify the total workload for each 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.

  9. 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 ensure that EM_SSA_USER will not exceed the maximum allocated value.

  10. Click Submit to create a database pool. The newly created database pool will appear in the Database Cloud Self Service Portal Setup: Database Pools page.

13.5 Provisioning Pluggable Databases

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 13-4 Provisioning Pluggable Databases

Step Task Role

1

Follow the steps in the Getting Started section to enable DBaaS.

See Section 12.2, "Getting Started"

2

Set up one or more PaaS Infrastructure Zones.

See Section 10.3, "Creating a PaaS Infrastructure Zone"

3

Create a database pool for PDB as a service.

See Section 13.5.1, "Creating a Database Pool for PDB as a Service"

4

Configure the request settings.

See Section 13.2.2, "Configuring Request Settings"

5

Define quotas for each self service user.

See Section 13.2.3, "Setting Up Quotas"

6

Create a database provisioning profile. This step is optional and is not required if you are creating an empty pluggable database.

See Section 13.2.4, "Creating a Database Provisioning Profile"

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 Section 13.2.5.2, "Creating a Service Template for PDB as a Service"

8

Configure the Chargeback Service.

See Section 26, "Chargeback Administration"

9

While deploying a database, select the service template that you have created.

See Section 14.2, "Requesting Databases, Pluggable Databases, and Schemas"


13.5.1 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:

  1. Log into Enterprise Manager as a user with the EM_SSA_ADMINISTRATOR role.

  2. From the Setup menu, select Cloud, then select Database. The Database Cloud Self Service Portal Setup page appears.In the Database Pools page, select For Pluggable Database from the Create menu.

    Figure 13-27 Create Database Pool: Setup Page (PDB)

    Surrounding text describes Figure 13-27 .
  3. Enter a name and description for the database pool.

  4. 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 for cluster databases.

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

  5. 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 Section 12.6, "Creating a Container Database".

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

  6. 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.
  7. Click Next. The Create New Pool: Policies page appears.

    Figure 13-28 Create Database Pool: Policies (PDB)

    Surrounding text describes Figure 13-28 .

    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 S­­GA / memory limit for each pluggable database is 3.2

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

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

13.6 Using Snap Clone to Provision Databases

You can create a snap clone of a large database which will allow to quickly provision the database. The snap clone is stored in the Software Library and can be used to create service templates and provision databases. Snap Clone is a storage agnostic and self service approach to creating rapid and space efficient clones of large databases. The main features of snap clone are:

  • Storage Agnostic Support: All storage vendors are supported (NAS and SAN).

  • Self Service Driven Approach: Empowers the self service user to clone databases as required on an ad-hoc basis.

  • Rapid Cloning: Databases can be cloned in minutes and not in days or weeks.

  • Space Efficient: This features allows users to significantly reduce the storage footprint.

Table 13-5 Using Snap Clone to Provision Databases

Step Task Role

1

Follow the steps in the Getting Started section to enable Snap Clone.

See Section 12.2, "Getting Started"

2

Register storage servers.

See Section 12.10, "Registering and Managing Storage Servers"

3

Set up one or more PaaS Infrastructure Zones.

See Section 10.3, "Creating a PaaS Infrastructure Zone"

4

Create a database pool.

See Section 13.2.1, "Creating a Database Pool"

5

Configure the request settings.

See Section 13.2.2, "Configuring Request Settings"

6

Define quotas for each self service user.

See Section 13.2.3, "Setting Up Quotas"

7

Set up the Test Master Database and enable snap clone.

See

Section 12.8, "Setting Up the Test Master for DBaaS Snap Clone"

Section 12.9, "Enabling or Disabling Snap Clone"

8

Create a database provisioning profile using a snap clone.

See Section 13.2.4.1, "Creating a Database Provisioning Profile Using Snapshots"

9

Create a service template based on the profile you have created.

See Section 13.2.5.1.1, "Creating Service Template Using Snap Clone Profile"

10

Configure the Chargeback Service. (this step is optional)

See Section 26, "Chargeback Administration"

11

While deploying a database, select the service template you have created.

See Section 14.2, "Requesting Databases, Pluggable Databases, and Schemas"


13.6.1 Provisioning Databases Using Clone DB Provisioning Profile

Using Clone DB, you can clone a database multiple times without copying the data files into several different locations. Instead, Oracle Database creates the files in the CloneDB database using copy-on-write technology, so that only the blocks that are modified in the CloneDB database require additional storage on disk.

The CloneDB databases use the data files of a database backup. Using the backup data files ensures that the production data files are not accessed by the CloneDB instances and that the CloneDB instances do not compete for the production database's resources, such as CPU and I/O resources.

Table 13-6 Provisioning Databases Using Clone DB Provisioning Profile

Step Task Role

1

Follow the steps in the Getting Started section to enable DBaaS.

See Section 12.2, "Getting Started"

2

Set up one or more PaaS Infrastructure Zones.

See Section 10.3, "Creating a PaaS Infrastructure Zone"

3

Create a database pool.

See Section 13.2.1, "Creating a Database Pool"

4

Configure the request settings.

See Section 13.2.2, "Configuring Request Settings"

5

Define quotas for each self service user.

See Section 13.2.3, "Setting Up Quotas"

6

Create a database provisioning profile using a RMAN Image profile.

See Section 13.2.4.6, "Creating a Database Provisioning Profile Using Clone DB"

7

Create a service template based on the profile you have created.

See Section 13.2.5.1.4, "Creating a Service Template Using CloneDB Profile"

8

Configure the Chargeback Service.

See Section 26, "Chargeback Administration"

9

While deploying a database, select the service template you have created.

See Section 14.2, "Requesting Databases, Pluggable Databases, and Schemas"


13.7 Performing Full Clone Using RMAN Backup

Database backups created by RMAN (Recovery Manager) are stored as image copies or backup sets.

Table 13-7 Provisioning Databases Using Clone DB Provisioning Profile

Step Task Role

1

Follow the steps in the Getting Started section to enable DBaaS.

See Section 12.2, "Getting Started"

2

Set up one or more PaaS Infrastructure Zones.

See Section 10.3, "Creating a PaaS Infrastructure Zone"

3

Create a database pool.

See Section 13.2.1, "Creating a Database Pool"

4

Configure the request settings.

See Section 13.2.2, "Configuring Request Settings"

5

Define quotas for each self service user.

See Section 13.2.3, "Setting Up Quotas"

6

Create one of the following database provisioning profiles:

  • RMAN Backup

  • Existing RMAN Backup

See Section 13.2.4.2, "Creating a Database Provisioning Profile Using RMAN Backup"

Section 13.2.4.3, "Creating a Database Provisioning Profile Using Existing RMAN Backup"

7

Create a service template based on the profile you have created.

See Section 13.2.5.1.2, "Create Service Template Using RMAN Backup Profile"

8

Configure the Chargeback Service.

See Section 26, "Chargeback Administration"

9

While deploying a database, select the service template you have created.

See Section 14.2, "Requesting Databases, Pluggable Databases, and Schemas"