Scaling a Database Deployment

If a database deployment on Oracle Database Cloud Service is performing poorly or is running out of storage, you can scale up the environment supporting the database deployment.

Usually, the need to scale arises as the result of analyzing database performance, as described in Tuning Oracle Database Performance on Database Cloud Service.

Occasionally, the need to scale arises from some change made to the database or backup configuration after it was created. For example, if the decision to use the In-Memory Database option was made after database creation, you might need to scale up the compute shape to one of the high-memory options, such as scaling from "OC4 - 2 OCPU, 15 GB RAM" to "OC2M - 2 OCPU, 30 GB RAM".

Scaling the Compute Shape for a Database Deployment

Note:

When you scale the compute shape of a database deployment on Database Cloud Service, the deployment is put into Maintenance status during the operation and it is restarted.

To scale the compute shape for a database deployment:

  1. View the overview page for the database deployment:
    1. Open the Oracle Database Cloud Service console.

      For detailed instructions, see Accessing the Oracle Database Cloud Service Console.

    2. Click the name of the deployment you want to scale.

      The Oracle Database Cloud Service Overview page is displayed.

  2. Choose the scaling command:

    • For database deployments that use Oracle RAC, click the Menu icon next to the deployment name and choose Scale Up/Down.

    • For other deployments, click the Menu icon menu in the box for the compute node and choose Scale Up/Down.

    The Scale Up/Down Service overlay is displayed. Note that the overlay includes information about the current compute shape.

  3. Select a new compute shape.

    Note:

    When scaling down a database deployment on Oracle Public Cloud Machine, do not scale down to the OC3 shape. Doing so can cause an out-of-memory condition and make the compute nodes of the deployment inaccessible.

  4. Click Yes, Scale Up/Down Service to scale the database deployment.

    The scaling operation begins. The database deployment is in Maintenance status and unavailable while the scaling operation is in progress.

Scaling Up the Storage for a Database Deployment

Note:

When you scale up the storage for a database deployment on Database Cloud Service , the deployment is put into Maintenance status during the operation and it is restarted.

When you scale up the storage for a database deployment, a Compute Cloud Service storage volume is created and attached to the deployment.

This storage volume remains attached and available to the deployment even after it is restarted or is stopped and then started. Also, the storage volume exists until you delete the database deployment, at which time the storage volume is also deleted.

Note:

A compute node can have a maximum of ten storage volumes attached to it.

Five of these ten are used when the database deployment is created, leaving you only five opportunities to scale up storage. Therefore, each scale-up operation you perform can dramatically affect the maximum size your database can grow to.

To scale up the storage for a database deployment:

  1. View the overview page for the database deployment:

    1. Open the Oracle Database Cloud Service console.

      For detailed instructions, see Accessing the Oracle Database Cloud Service Console.

    2. Click the name of the database deployment you want to scale.

      The Oracle Database Cloud Service Overview page is displayed.

  2. Choose the scaling command:

    • For database deployments that use Oracle RAC, click the Menu icon next to the deployment name and choose Scale Up/Down.

    • For other deployments, click the Menu icon menu in the box for the compute node and choose Scale Up/Down.

    The Scale Up/Down Service overlay is displayed.

  3. In the Additional Storage (GB) box, enter an amount raw storage to add to the database deployment, from 1 to 2048 GB in increments of 1 GB.

    An Oracle Compute Cloud Service storage volume of the indicated size will be created. Note that a small percentage of this raw storage will be used for file system constructs and other overhead.

    Note:

    When adding storage to a database deployment that uses Oracle Real Application Clusters (RAC), you should specify the same size as the other storage volume or volumes already in the Oracle ASM disk group you want to scale up: Data or Backup.

  4. Specify how the additional storage should be allocated in the Add Storage to list:

    • Create New Storage Volume: adds a new storage volume to the database deployment and mounts it as the next available /u0n mount point. This option is not available for deployments that use Oracle Real Application Clusters.

    • Extend Data Storage Volume: adds the storage volume to the existing Linux LVM disk group (or Oracle ASM disk group on deployments that use Oracle Real Application Clusters) for database data storage.

    • Extend Backup Storage Volume: adds the storage volume to the existing Linux LVM disk group (or Oracle ASM disk group on deployments that use Oracle Real Application Clusters) for backup and FRA storage.

  5. Click Yes, Scale Up/Down Service to scale the database deployment.

    The scaling operation begins. The deployment is in Maintenance status and unavailable while the scaling operation is in progress.