14 Enabling the DBaaS Cloud

This chapter covers the initial configuration required to enable a DBaaS Cloud.

It contains the following sections:

• Getting Started

• Setting Up Credentials for Provisioning

• Provisioning Database Software for Database as a Service

• Provision the Database for Schema as a Service

• Provision a Container Database for PDB as a Service

• Configuring the Oracle Listener

14.1 Getting Started

This section helps you get started by providing a list of steps that must be performed to get started in setting up a private database cloud. Before you set up the database cloud, you must have completed the common setup tasks described in Common Setup Tasks.

Table 14-1 Getting Started with DBaaS

Step	Task	Role
1	Configure Privilege Delegation Settings on your managed hosts. See Configuring Privilege Delegation Settings	Super Administrator
2	Set up provisioning credentials. See Setting Up Credentials for Provisioning	Self Service Administrator
3	Setting up Database as a Service, you must provision the database software or create Oracle Homes. See Provisioning Database Software for Database as a Service. Setting up Schema as a Service, you must provision the database. See Provision the Database for Schema as a Service. Setting up Pluggable Database as a Service, you must create a container database (CDB) with one or more pluggable databases (PDBs). See Provision a Container Database for PDB as a Service.	Self Service Administrator
4	Configure the Listener. See Configuring the Oracle Listener.	Self Service Administrator
5	If you are using the Snap Clone profile, you must register the storage servers. See Registering and Managing Storage Servers.	Self Service Administrator

14.2 Setting Up Credentials for Provisioning

Before you perform any operations on the Managed Servers or databases, you must define the credentials that will be used by Enterprise Manager to connect to the targets.

You need to set up the following types of credentials:

• Normal credentials are the host operating system credentials used to provision the database software and create databases. For example, oracle/<login password>. These credentials are saved when the Database Pool is created and are used when the EM_SSA_USER requests a database or a schema.

• Privileged credentials are the host operating system credentials used to perform privileged actions like executing root scripts. These credentials are used deploying software (for running root.sh during deployment), for mounting and unmounting storage volumes (for databases created with snapshots) and so on. These credentials are saved along with the Database Pool if the pool is used for creating databases using snapshots.

• Database SYSDBA credentials are used and saved for schema as a service database pool. These credentials are required only for schema as a service.

Note:

It is recommended that the same OS user who owns the Oracle Home on the host, creates the database.

To create named credentials, follow these steps:

1. Log in to Enterprise Manager as an administrator with the EM_SSA_ADMINISTRATOR role.
2. From the Setup menu, select Security, then select Named Credentials.
3. Click Create in the Named Credentials page.
4. Enter the Credential Name and Credential Description. Set the Authenticating Target Type field to Host and Scope field to Global. Enter the user name and password in the Credential Properties section. If you need to set privileged credentials, select Sudo or PowerBroker in the Run Privilege field and enter values in the Run As and Profile fields.
5. Click Test and Save.
6. Verify these credentials against a host target and click OK.

14.3 Provisioning Database Software for Database as a Service

Before you can enable database as a service, the database software must already be provisioned on all hosts. Database software can be provisioned by an administrator with the EM_SSA_ADMINISTRATOR role in the following ways:

• Provisioning Profile

  • Capture a gold image of an existing database using a Provisioning Profile. See the Enterprise Manager Lifecycle Management Administrator's Guide for details.

  • Use the Provisioning Profile to provision the Clusterware/ASM or Grid Infrastructure (for Real Application Cluster databases), and Database Oracle Home. This method ensures that the necessary database plug-in (monitoring part of the database plug-in) is deployed onto the Management Agent as part of the database provisioning Oracle Home installation.

    To create a provisioning profile, from the Enterprise menu, select Provisioning and Patching, then select Database Provisioning and select the database provisioning deployment procedure to be used. You can select either Provision Oracle Database or Provisioning Oracle RAC Database deployment procedure.

    Note: Do not create a new database as part of this deployment procedure.

• Using the Database Installer

  • From the Setup menu, select Extensibility, then select Plug-ins. and deploy the complete SSA (Enterprise Manager for Oracle Cloud) plug-in on all the Management Agents in a PaaS Infrastructure Zone.

  • Run the Clusterware/ASM or Grid Infrastructure installer to set up the cluster and ASM (for RAC databases).

  • Run the Database Installer and ensure you select the Install Database Software Only option on all hosts.

  • Discover the cluster. From the Setup menu, select Add Target, then Add Targets Manually, and then select Add Non-Host Targets Using Guided Process (Also Adds Related Targets).

    Select:

    • Oracle Cluster and High Availability Service to discover the cluster.

    • Oracle Database, Listener and Automatic Storage Management to discover ASM and listeners.

  • From the Enterprise menu, you can also select Job, then select Library and submit the Discover Promote Oracle Home Target job to add the Oracle Home.

For more details on provisioning the database software, see the Enterprise Manager Lifecycle Management Administrator's Guide.

14.4 Provision the Database for Schema as a Service

For schema as a service, you must deploy a single instance or RAC database. To deploy a database, you must use the Provision Oracle Database deployment procedure. See the Enterprise Manager Lifecycle Management Administrator's Guide for details.

14.5 Provision a Container Database for PDB as a Service

Note:

If pluggable databases (PDBs) need to be provisioned, you must be create container 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.

You can create a CDB either by using the Database Configuration Assistant (DBCA) or the CREATE_DATABASE SQL statement. See the Oracle Database Administrator's Guide for details. After the CDB is created, it consists of the root and the seed. The root contains minimal user data or no user data, and the seed contains no user data.

PDBs contain user data. After the CDB has been created, you can add PDBs to the CDB by using either of the following options:

• Create a new PDB. See the Enterprise Manager Lifecycle Management Administrator’s Guide for details.

• Plug in an unplugged PDB into a CDB. See the Enterprise Manager Lifecycle Management Administrator’s Guide for details.

14.6 Configuring the Oracle Listener

You need to configure an Oracle Home and the Oracle Listener before you can add them as Enterprise Manager targets.

To set up the Oracle Listener (Listener) for the database hosts, follow these steps:

1. Log in as a user with the EM_SSA_ADMINISTRATOR role and perform mass deployment of database homes on the newly added hosts as described in Adding Hosts

2. To configure a Listener running from the same Oracle Home on which the database instance is to be created, launch a Bash shell and enter the following commands:

   1. <AGENT_BASE>/agent_inst/bin/emctl stop agent

   2. export TNS_ADMIN=<DB_HOME_LOCATION>/network/admin

   3. export ORACLE_HOME=<DB_HOME_LOCATION>

   4. Run $ORACLE_HOME/bin/netca and create the listener. Make sure you have the same Listener name and Listener port on all the hosts.

3. To configure a Listener running from the Single Instance High Availability (SIHA) Oracle Home, launch a Bash shell and enter the following commands:

   1. export ORACLE_HOME=<SIHA_HOME_LOCATION>

   2. Run $ORACLE_HOME/bin/netca and create the listener. Make sure you have the same listener name and listener port on all the hosts

4. Log in as the user with the DBAAS_ADMIN_ROLE and discover the newly added Listener target on all the hosts. From the Setup menu, select Add Target, then select Add Target Manually.

5. Select the Add Non-Host Targets Using Guided Process option and select Target Type as Oracle Database, Listener, and Automatic Storage Management and click Add Guided Discovery and follow the steps in the wizard. Before you add the new Listener target, ensure the ORACLE_HOME for the Listener is pointing to the correct ORACLE_HOME location. This process adds the Oracle Home target which is used when a database pool is created.