• Updating the Cloud Tooling on a Database as a Service Instance
• Maintaining the Manageability of Your Database as a Service Instance
• Administering Oracle REST Data Services (formerly Oracle APEX Listener)
• Administering Oracle GlassFish Server
• Loading Data into the Oracle Database in a Database as a Service Instance
• Tuning Performance of the Oracle Database in a Database as a Service Instance
• Monitoring and Managing the Database in a Database as a Service Instance
• Creating a Database on a Virtual Image Service Instance
Scaling a Database as a Service Instance
If an Oracle Database Cloud - Database as a Service instance is performing poorly or is running out of storage, you can scale up the instance.
Usually, the need to scale an instance arises as the result of analyzing database performance, as described in Tuning Performance of the Oracle Database in a Database as a Service Instance.
Occasionally, the need to scale an instance arises from some change made to the database or backup configuration after the instance was created. For example, if the decision to use the In-Memory Database option available in Enterprise Edition Extreme Performance was made after the instance was created, you might need to scale up the instance's 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 of a Service Instance
Note:
When you scale the compute shape of a Database as a Service instance, the service instance is put into Maintenance status during the operation and it is restarted. As a result of the restarting, any resources you’ve manually added to the service instance using the Compute Cloud Service console become detached from the service instance. For more information and for instructions on reattaching such resources, see About Stopping, Starting and Restarting a Service Instance.
To scale the compute shape of a service instance:
1. View the instance overview page for the service instance: a. Open the Oracle Database Cloud Service console.
For detailed instructions, see Accessing the Oracle Database Cloud Service Console.
b. Click the name of the instance you want to scale.
The Oracle Database Cloud Service Instance Overview page is displayed.
2. Choose the scaling command:
• For service instances that use Oracle RAC, click the next to the service instance name and choose Scale Up/Down.
• For other service instances, 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 instance's current compute shape.
3. Select a new compute shape.
4. Click Yes, Scale Up/Down Service to scale the service instance.
The scaling operation begins. The service instance is in Maintenance status and unavailable while the scaling operation is in progress.
Scaling Up the Storage of a Service Instance
Note:
When you scale up the storage of a Database as a Service instance, the service instance is put into Maintenance status during the operation and it is
restarted. As a result of the restarting, any resources you’ve manually added to the service instance using the Compute Cloud Service console become detached from the service instance. For more information and for instructions on reattaching such resources, see About Stopping, Starting and Restarting a Service Instance.
When you scale up the storage of a service instance, a Compute Cloud Service storage volume is created and attached to the service instance.
This storage volume remains attached and available to the service instance even after the service instance is restarted or is stopped and then started. Also, this storage volume exists until you delete the service instance, at which time the storage volume is also deleted.
Note:
A compute node in a service instance can have a maximum of ten storage volumes attached to it.
To scale up the storage of a service instance:
1. View the instance overview page for the service instance: a. Open the Oracle Database Cloud Service console.
For detailed instructions, see Accessing the Oracle Database Cloud Service Console.
b. Click the name of the service instance you want to scale.
The Oracle Database Cloud Service Instance page is displayed.
2. Choose the scaling command:
• For service instances that use Oracle RAC, click the next to the service instance name and choose Scale Up/Down.
• For other service instances, 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
service instance, from 1 to 1000 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 service instance 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 service instance and mounts it as the next available /u0n mount point. This option is
not available for service instances 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 service instances 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 service instances that use Oracle Real Application Clusters) for backup and FRA storage.
Note:
The Add Storage to list is not available for service instances created using the Oracle Database Cloud Service - Virtual Image service level. In this case, the Oracle Compute Cloud Service storage volume is added as a raw block device to the service instance. You need to format it, mount it, and update the /etc/ fstab file to make it usable in the service instance.
5. Click Yes, Scale Up/Down Service to scale the service instance.
The scaling operation begins. The service instance is in Maintenance status and unavailable while the scaling operation is in progress.