Oracle Cloud Infrastructure Documentation

Exadata Use Cases

The following use case examples can get you started working with the Exadata operations available in the Oracle Cloud My Services API.

Important

These use cases are for use with Oracle Database Exadata Cloud Service. For more information, see Administering Oracle Database Exadata Cloud Service. These use cases DO NOT apply to Exadata DB Systems available in Oracle Cloud Infrastructure.

Exadata Firewall Whitelisting

To enable access to your Exadata Cloud Service instance, you can configure security rules and associate them with your instance. The security rules define a whitelist of allowed network access points.

The firewall provides a system of rules and groups. By default, the firewall denies network access to the Exadata Cloud Service instance. When you enable a security rule, you enable access to the Exadata Cloud Service instance. To enable access you must:

  • Create a security group and create security rules that define specific network access allowances.

  • Assign the security group to your Exadata Cloud Service instance.

You can define multiple security groups, and each security group can contain multiple security rules. You can associate multiple security groups with each Exadata Cloud Service instance, and each security group can be associated with multiple Exadata Cloud Service instances. You can dynamically enable and disable security rules by modifying the security groups that are associated with each Exadata Cloud Service instance.

To enable access to an Exadata Cloud Service instance:

Note

In the following examples, <domain> is the identity domain ID. An identity domain ID can be either the IDCS GUID that identifies the identity domain for the users within Identity Cloud Service (IDCS) or the Identity Domain name for a traditional Cloud Account.

To obtain the IDCS GUID
  1. Get the service instance IDs.

    Operation: GET ServiceInstances

    Example
  2. Get the service configuration IDs.

    Operation: GET SIServiceConfigurations

    Example
  3. Get the current security groups for the service entitlement.

    Operation: GET SEExadataSecurityGroups

    Example
  4. Get the current security group assignments for the service instance

    Operation: GET SIExadataSecurityGroupAssignments

    Example
  5. Create a security group with security rules.

    Operation: POST SEExadataSecurityGroups

    Example
  6. Assign the security group to a service instance.

    Operation: POST SIExadataSecurityGroupAssignments

    Example

Exadata Scaling with Bursting

You can temporarily modify the capacity of your Exadata environment by configuring bursting. Bursting is a method you can use to scale Exadata Cloud Service non-metered instances within an Exadata system.

To scale up your non-metered instances, increase the number of compute nodes by modifying the burstOcpu attribute of the host. When you no longer need the additional nodes, update the burstOcpu attribute back to its original setting.

Note

In the following examples, <domain> is the identity domain ID. An identity domain ID can be either the IDCS GUID that identifies the identity domain for the users within Identity Cloud Service (IDCS) or the Identity Domain name for a traditional Cloud Account.

To obtain the IDCS GUID
  1. Get the service instance IDs.

    Operation: GET ServiceInstances

    Example
  2. Get the service configuration IDs.

    Operation: GET SIServiceConfigurations

    Example
  3. Get the current compute node configuration.

    Operation: GET SIExadataBursting

    Example
  4. Modify the values for burstOcpu.

    Operation: PUT SIExadataBursting

    You can modify burstOcpu to a value that is up to the value of maxBurstOcpu. This example adds two compute nodes to each host.

    Example
  5. Verify the new compute node configuration.

    Operation: GET SIExadataBursting

    Example