If a database deployment on Oracle Database Classic 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 Classic 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.

Scaling the Compute Shape for a Database Deployment

This topic does not apply to Oracle Cloud Infrastructure.

To scale the compute shape for a database deployment:

1. View the Overview page for the database deployment:

   1. Open the Oracle Database Classic Cloud Service console.

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

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

      The Oracle Database Classic Cloud Service Overview page is displayed.

2. Choose the scaling command:

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

   • For other deployments, click the 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.

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

When you scale up the storage for a database deployment, a 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.

Scale-up limits and constraints differ depending on the infrastructure underlying the deployment:

• Oracle Cloud Infrastructure supports 32 block storage volumes attached to a compute node, of which 4 are used when the database deployment is created. Thus, you have 28 opportunities to scale up storage.

  In each scale-up operation, you can create a storage volume of 50 GB to 16384 GB (16 TB) in 50 GB increments. The deployment is put into Maintenance status during the operation.

• Oracle Cloud Infrastructure Classic supports 10 block storage volumes attached to a compute node, of which 5 are used when the database deployment is created. Thus, you have only 5 opportunities to scale up storage. Consequently, each scale-up operation you perform can dramatically affect the maximum size your database can grow to.

  In each scale-up operation, you can create a storage volume of 1 GB to 2048 GB in 1 GB increments. The deployment is put into Maintenance status and restarted during the operation. As a result of the restarting, any resources you’ve manually added to the database deployment by using the Compute Classic console become detached from the deployment. For more information and for instructions on reattaching such resources, see About Stopping, Starting and Restarting a Database Deployment.

To scale up the storage for a database deployment:

1. View the Overview page for the database deployment:

   1. Open the Oracle Database Classic Cloud Service console.

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

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

      The Oracle Database Classic Cloud Service Overview page is displayed.

2. Choose the scaling command:

   • For database deployments in Oracle Cloud Infrastructure, click the next to the deployment name and choose Add Storage.

   • For database deployments in Oracle Cloud Infrastructure Classic that use Oracle RAC, click the next to the deployment name and choose Scale Up/Down.

   • For other deployments in Oracle Cloud Infrastructure Classic, click the 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.

   Note that up to 8% of this raw storage will be used for file system constructs and other overhead.

   Also note that, when adding storage to a database deployment that uses Oracle 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 RAC.

   • 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 RAC) 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 RAC) 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 while the scaling operation is in progress.