Create Database Deployment Procedure (Single Instance)

Database Deployment Procedures are a facility of EM12c that create the requested database(s) on behalf of the Cloud end user and will automatically return to the end user a connection string for the database that has been created.

The following example describes creating a deployment procedure for a single instance database.

This example demonstrates the creation of an Oracle 11gR2 RAC single instance database, however, the same approach applies to creating deployment procedures for RAC Cluster or RAC One Node.

Note that the database storage for Oracle Database 11gR2 will be on the Exadata Storage Cells of the SPARC SuperCluster. This storage will already be established during SuperCluster installation and further administered and provisioned using the SuperCluster/Exadata Zone tools.

1. Choose Enterprise -> Provisioning and Patching -> Database Provisioning.
2. Select Create Oracle Database from the Deployment Procedures panel, and then click Launch.

   The Create Database wizard is displayed.

3. In the Database and Version and Type window, enter the following values:
   
   1. Choose 11.2.0.3.0 from the Version menu, and choose Oracle Single Instance Database from the Select database type options.

      This deployment procedure will be available to cloud end users, so click the lock icons next to each selection so that these values can't be changed by the end users.

   2. Add the Host(s) where the database will be created.
      1. Click Add Hosts to launch the Search and Select: Targets pop-up window.
      2. Select the Oracle Solaris on SPARC (64-bit) platform and click Search.
      3. Highlight the appropriate host and click Select.
   3. Select the Oracle Home instance to use with the host.
      1. Click the magnifying glass icon in the Oracle Home column to launch the Select Oracle Home pop-up window.
      2. Highlight the appropriate Oracle Home and click Select.
   4. Select the Host Credentials column and type the credential name, then click Next.

      The example uses the ORACLE credential created earlier.

   5. Confirm entries, then click Next.

      This validates the Oracle Home.

4. In the Database Template window, click Select Template From Oracle Home, and click Next.
5. In the Identification and Placement window, enter the following values:
   
   1. Type values for the Global Database Name and SID boxes.

      When creating a template, these values are for validation purposes only and are not actually used. This is because the Global database name and SID are replaced by EM12c when it creates a unique database instance for the Database Cloud end user.

   2. Click the lock icon to unlock Database Credentials.

      Do not lock the Identification section, because these values are substituted when database as a service is used.

   3. Type and confirm the password, and then click Next.

   The verification window is displayed, and the Storage Locations window is displayed.

6. In the Storage Locations window, enter the following values:
   
   1. Under Storage Type, select Automatic Storage Management (ASM)
   2. Under Database Files Location, select Use Common Location for Database Files.
      1. Click the magnifying glass icon next to the Location box to launch the Select Disk Group pop-up window.
      2. Highlight the appropriate disk group and click Select.
   3. Under Recovery Files Location, select Use same storage type as database files location and Use Fast Recovery Area.
      1. Click the magnifying glass icon next to the Discovery Area Location box to launch the Select Disk Group pop-up window.
      2. Highlight the appropriate disk group and click Select.
   4. Confirm entries, and then click Next.

      The storage configuration is validated, and a pop-up window displays the progress of this validation. When the validation has finished successfully, the Create Database : Initialization Parameters window is displayed.

7. In the Initialization Parameters window, enter the following values:
   
   1. Select Automatic Shared Memory Management, check Specify Memory Settings as Percentage of Available Memory and adjust the slider for Percentage of Available Memory.

      Use this memory setting to control the amount of memory available to the database instances the cloud end user creates. The example uses percentage of available memory for ease of demonstration, but you can also uncheck this to limit each database to a specified amount. For instance, a useful strategy might be to create separate deployment procedures for small, medium, and large memory configurations, where the SGA is set to an absolute value and not a percentage of available memory.

   2. Configure the Host CPU count and set the other database configuration parameters to suit.
   3. Confirm your entries, and then click Next.

      A pop-up window indicates verification is run, then the Create Database : Additional Configurations Options window is displayed.

8. In the Additional Configuration Options window, click Next.
9. In the Schedule window, enter the following values.
   1. Type a name for the Deployment Procedure Instance Name, and then click Next.
   2. Type a descriptive name for this deployment procedure in the Name box of the pop-up window, and then click Save.
   3. Then in the next window, and click Cancel as you do not want to instantiate this procedure now.

      The new Deployment Procedure (in our example SI-Small-11gR2-Dedicated) is now visible in the list of deployment procedures.