Manage Exadata Database Service on Cloud@Customer Infrastructure

Use the provided tools to manage the Infrastructure.

About Provisioning Oracle Exadata Database Service on Cloud@Customer Systems

To provision an Oracle Exadata Database Service on Cloud@Customer system, you must work with Oracle to set up and configure the system.

Provisioning an Oracle Exadata Database Service on Cloud@Customer system is a collaborative process. The process is performed in the following sequence:

  1. You create the Oracle Exadata Database Service on Cloud@Customer infrastructure.
  2. You generate a file containing the infrastructure configuration details, and provide it to Oracle.
  3. The Oracle Exadata Database Service on Cloud@Customer system is physically installed in your data center.
  4. Oracle uses the infrastructure configuration file to perform initial system configuration. At the end of this task, Oracle supplies you with an activation file.
  5. You activate the Exadata Database Service on Cloud@Customer infrastructure by using the supplied activation file.

When the provisioning process is complete, the Oracle Exadata Database Service on Cloud@Customer system is ready for you to use. You can then create a virtual machine (VM) cluster, and later create some databases.

Caution:

Avoid entering confidential information when assigning descriptions, tags, or friendly names to your cloud resources through the Oracle Cloud Infrastructure Console, the APIs, or the command-line interface.

Overview of Elastic Storage Expansion

With elastic storage expansion, you can dynamically increase your storage capacity to meet your growing workload requirements.

Expand the storage capacity on-demand by scaling up the infrastructure with additional storage servers without being constrained by the standard supported shapes. You can allocate additional storage capacity available from the newly added storage servers to the already deployed VM Cluster without disrupting the current running workloads. Additional storage capacity from newly added storage servers is also available for provisioning new VM Clusters on the infrastructure.

With the elastic storage expansion capability, you can now:
  • Provision new Exadata Infrastructure with custom storage capacity.
  • Start with a smaller storage footprint for the Exadata Infrastructure at install time.
  • Expand the storage capacity on existing deployed Exadata Infrastructure on-demand in an automated, elastic fashion.
  • Allocate additional storage capacity available from newly added storage servers to already deployed VM clusters and/or use them for provisioning new VM clusters on the infrastructure.

Table 5-1 Key Additional Resources

Specification Exadata Base System Storage Server X7-2 Exadata Storage Server X7-2

Additional Raw Flash Storage Capacity

6.4 TB

25.6 TB

Additional Raw Disk Storage Capacity

48 TB

120 TB

Additional Usable Storage Capacity

14 TB

35.3 TB

Table 5-2 Key Additional Resources

Specification Exadata Base System Storage Server X8-2 Exadata Storage Server X8-2

Additional Raw Flash Storage Capacity

12.8 TB

25.6 TB

Additional Raw Disk Storage Capacity

84 TB

168 TB

Additional Usable Storage Capacity

24.6 TB

49.6 TB

Table 5-3 Key Additional Resources

Specification Exadata Base System Storage Server X8M-2 Exadata Storage Server X8M-2

Additional Raw Flash Storage Capacity

12.8 TB

25.6 TB

Additional Raw Disk Storage Capacity

84 TB

168 TB

Additional Usable Storage Capacity

24.6 TB

49.6 TB

Additional Persistent Memory

-

1.5 TB

Table 5-4 Key Additional Resources

Specification Exadata Base System Storage Server X9M-2 Exadata Storage Server X9M-2

Additional Raw Flash Storage Capacity

12.8 TB

25.6 TB

Additional Raw Disk Storage Capacity

84 TB

216 TB

Additional Usable Storage Capacity

24.6 TB

63.6 TB

Additional Persistent Memory

-

1.5 TB

Elastic scaling of Exadata Storage Servers is subject to the following conditions:
  • The Exadata Cloud@Customer system configuration must be based on Oracle Exadata X7 hardware, Oracle Exadata X8 hardware, Oracle Exadata X8M hardware, or Oracle Exadata X9M hardware.
  • Each Exadata Cloud@Customer system configuration can have an absolute maximum of 12 Exadata Storage Servers.
  • Exadata Infrastructure deployed with base configuration shape can only be expanded using base expansion SKU storage servers.
  • Exadata Infrastructures deployed with X7 generation at install time can be scaled with X8 generation storage servers. X8 storage servers used to scale X7 infrastructure will only present the same total usable capacity as all other X7 storage servers that are already part of the infrastructure.

  • Exadata Infrastructures deployed with X8M generation at install time can only be scaled with X8M or higher generation storage servers.

Exadata Infrastructures deployed with additional storage servers will be configured as an Elastic shape with the total number of storage servers and usable capacity clearly called out for the given infrastructure.

Before you can scale the number of Exadata storage servers, review the site and network requirements, and the checklists to prepare and deploy Exadata Cloud@Customer. Ensure that you have worked with sales and followed the procurement process. The following figure provides you an overview of the order and deployment process.

Figure 5-1 Overview of Order and Deployment Process

This image illustrates an overview of order and deployment process

Using the Console to Provision Exadata Database Service on Cloud@Customer Infrastructure

Learn how to provision an Exadata Database Service on Cloud@Customer system.

Using the Console to Create Oracle Exadata Database Service on Cloud@Customer Infrastructure

To create your Oracle Exadata Database Service on Cloud@Customer infrastructure, be prepared to provide values for the fields required for configuring the infrastructure.

  1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  2. Under Region, select the region that you want to associate with the Oracle Exadata infrastructure.

    The region that is associated with your Oracle Exadata infrastructure cannot be changed after the Oracle Exadata infrastructure is created. Therefore, ensure that you select the most appropriate region for your infrastructure. Consider the following factors:

    • Consider any business policies or regulations that preclude the use of a particular region. For example, you can be required to maintain all operations within national boundaries.
    • Consider the physical proximity of the region to your data center. Needless extra physical separation adds unnecessary latency to network communications between Oracle Cloud Infrastructure and your corporate data center.
  3. Click Exadata Infrastructure.
  4. Click Create Exadata Infrastructure.
  5. In the Create Exadata Infrastructure page, provide the requested information:

    • Oracle Cloud Infrastructure region: The region that is associated with your Oracle Exadata infrastructure cannot be changed after the Oracle Exadata infrastructure is created. Therefore, check the displayed region to ensure that you are using the most appropriate region for your infrastructure.

      See step 2 (earlier in this procedure) for further considerations. To switch regions now, use the Region menu at the top of the console.

    • Choose a compartment: From the list of available compartments, choose the compartment that you want to contain the Oracle Exadata infrastructure.

      For more information, see Understanding Compartments.

    • Provide the display name: The display name is a user-friendly name that you can use to identify the Exadata infrastructure. The name doesn't need to be unique, because an Oracle Cloud Identifier (OCID) uniquely identifies the Oracle Exadata infrastructure.
    • Select the Exadata system model: From the list, choose the model of the Oracle Exadata hardware that is being used.

      The Oracle Exadata system model and system shape combine to define the amount of CPU, memory, and storage resources that are available in the Exadata infrastructure. For more information, see System Configuration.

    • Select an Exadata system shape: Together with the Oracle Exadata system model, the Oracle Exadata system shape defines the amount of CPU, memory, and storage resources that are available in the Oracle Exadata infrastructure.

      • Base System: includes two compute nodes and three Oracle Exadata Storage Servers. A Base System is an entry-level configuration. Compared to other configurations, a Base System contains Oracle Exadata Storage Servers with significantly less storage capacity, and compute nodes with significantly less memory and processing power.
      • Quarter Rack: includes two compute nodes and three Oracle Exadata Storage Servers.
      • Half Rack: includes four compute nodes and six Oracle Exadata Storage Servers.
      • Full Rack: includes eight compute nodes and 12 Oracle Exadata Storage Servers.
    • Storage Configuration: You can add a minimum of 3 and extend up to a maximum of 12 storage servers. For each storage server you add, the storage capacity that will be added is displayed on the right.
    • Configure the cloud control plane server network

      Each Oracle Exadata Database Service on Cloud@Customer system contains two control plane servers, which enable connectivity to Oracle Cloud Infrastructure. The control plane servers are connected to the control plane network, which is a subnet on your corporate network. The following settings define the network parameters:

      • Control Plane Server 1 IP Address: Provide the IP address for the first control plane server. This IP address is for the network interface that connects the first control plane server to your corporate network using the control plane network.
      • Control Plane Server 2 IP Address: Provide the IP address for the second control plane server. This IP address is for the network interface that connects the second control plane server to your corporate network using the control plane network.
      • Netmask: Specify the IP netmask for the control plane network.
      • Gateway: Specify the IP address of the control plane network gateway.
      • HTTP Proxy: (Optional) You can choose to use this field to specify your corporate HTTP proxy. The expected format is as follows, where server is the server name, domain is the domain name, and port is the assigned port:
        http://server.domain:port
        For example:
        http://proxy.example.com:80

        For enhanced security, when possible, Oracle recommends that you use an HTTP proxy.

      • Enable Control Plane Server Offline Report: Enabling the Control Plane Server (CPS) offline report helps in diagnosing connectivity issues between the CPS and OCI endpoints, should they arise.
        To view the report, do the following:
        1. Find the CPS IP addresses.

          For more information, see Using the Console to View Exadata Infrastructure Network Configuration Details.

        2. From your local network, access the report over HTTP.

          To view the report in HTML format, use http://<CPSPublicIP>:18080/report

          To view the report in JSON format, use http://<CPSPublicIP>:18080/report/json

        For more information, see ExaCC gen2: Troubleshooting VPN/WSS connection from Customer Side.

    • Configure the Oracle Exadata system networks

      Each Oracle Exadata Database Service on Cloud@Customer system contains two system networks, which are not connected to your corporate network. The following settings define IP address allocations for these networks:

      • Administration Network CIDR Block: Specifies the IP address range for the administration network using CIDR notation. The administration network provides connectivity that enables Oracle to administer the Exadata system components, such as the Exadata compute servers, storage servers, network switches, and power distribution units. You can accept the suggested default, or specify a custom value.

        The maximum CIDR block prefix length is /23, which defines the smallest block of IP addresses that are required for the network. To allow for possible future expansion within Exadata Database Service on Cloud@Customer, a smaller CIDR block prefix length is recommended, which reserves more IP addresses for the network. The minimum CIDR block prefix length is /16.

      Ensure that the IP address range does not conflict with other hosts of your corporate network, and does not overlap with the InfiniBand network CIDR block.

    • InfiniBand Network CIDR Block: Specifies the IP address range for the Exadata InfiniBand network using CIDR notation. The Exadata InfiniBand network provides the high-speed low-latency interconnect used by Exadata software for internal communications between various system components. You can accept the suggested default, or specify a custom value.

      The maximum CIDR block prefix length is /22, which defines the smallest block of IP addresses that are required for the network. To allow for possible future expansion within Exadata Database Service on Cloud@Customer, a smaller CIDR block prefix length is recommended, which reserves more IP addresses for the network. The minimum CIDR block prefix length is /19.

      Ensure that the IP address range does not conflict with other hosts your corporate network, and does not overlap with the administration network CIDR block.

    • Configure DNS and NTP services

      Each Exadata Database Service on Cloud@Customer system requires access to Domain Names System (DNS) and Network Time Protocol (NTP) services. The following settings specify the servers that provide these services to the Exadata infrastructure:

      • DNS Servers: Provide the IP address of a DNS server that is accessible using the control plane network. You may specify up to three DNS servers.
      • NTP Servers: Provide the IP address of an NTP server that is accessible using the control plane network. You may specify up to three NTP servers.
      • Time Zone: The default time zone for the Exadata Infrastructure is UTC, but you can specify a different time zone. The time zone options are those supported in both the Java.util.TimeZone class and the Oracle Linux operating system.
        Note

        If you want to set a time zone other than UTC or the browser-detected time zone, then select the Select another time zone option, select a Region or country, and then select the corresponding Time zone.

        If you do not see the region or country you want, then select Miscellaneous, and then select an appropriate Time zone.

    • Provide maintenance details
      • Configure automatic maintenance

        Click Edit Maintenance Preferences.

        Edit Maintenance Preferences dialog is displayed.

        In the Edit Maintenance Preferences dialog, configure the following:
        • Choose a maintenance method:

          • Rolling: By default, Exadata Infrastructure is updated in a rolling fashion, one server at a time with no downtime.

          • Non-rolling: Update database and storage servers at the same time. The non-rolling maintenance method minimizes maintenance time but incurs full system downtime.

        • Enable custom action before performing maintenance on DB servers: Enable custom action only if you want to perform additional actions outside of Oracle’s purview. For maintenance configured with a rolling software update, enabling this option will force the maintenance run to wait for a custom action with a configured timeout before starting maintenance on each DB server. For maintenance configured with non-rolling software updates, the maintenance run will wait for a custom action with a configured timeout before starting maintenance across all DB servers.

          • Custom action timeout (in minutes): Timeout available to perform custom action before starting maintenance on the DB Servers.

            Default: 30 minutes

            Maximum: 120 minutes

        • Maintenance schedule:

          • No preference: The system assigns a date and start time for infrastructure maintenance.

          • Specify a schedule: Choose your preferred month, week, weekday, start time, and lead time for infrastructure maintenance.

          • Lead Time: Specify the minimum number of weeks ahead of the maintenance event you would like to receive a notification message.

        Click Save Changes.

        If you switch from rolling to non-rolling maintenance method, then Confirm Non-rolling Maintenance Method dialog is displayed.

        Enter the name of the infrastructure in the field provided to confirm the changes.

        Click Save Changes.

        Note

        After creating the infrastructure, you can find the maintenance method, maintenance schedule, DB Server version, and Storage Server version details under the Maintenance and Version sections on the Infrastructure Details page.

      • Provide maintenance contacts

        Maintenance contacts are required for service request-based communications for hardware replacement and other maintenance events.

        You can skip adding maintenance contacts while creating your infrastructure. However, you must add a primary contact prior to activating your infrastructure. Ensure that you provide the details of the contact that you used while registering the Customer Support Identifier (CSI) associated with this infrastructure, as a primary contact.

        Optionally, you can add a maximum of nine secondary contacts. Both the primary and secondary contacts receive all notifications about hardware replacement, network issues, and software maintenance runs. Note that you can promote any secondary contacts as the primary anytime you want. When you promote a secondary contact to primary, the current primary contact will be demoted automatically to secondary.

    • Show Advanced Options

      You have the option to configure advanced options.

      • Tags: (Optional) You can choose to apply tags. If you have permission to create a resource, then you also have permission to apply free-form tags to that resource. To apply a defined tag, you must have permission to use the tag namespace. For more information about tagging, see Resource Tags. If you are not sure if you should apply tags, then skip this option (you can apply tags later) or ask your administrator.
  6. Click Create Exadata Infrastructure.

    If all of your inputs are valid, then the Infrastructure Details page appears. The page outlines the next steps in the provisioning process. Initially, after creation, the state of the Oracle Exadata infrastructure is Requires-Activation.

Using the Console to View Exadata Infrastructure Network Configuration Details

To view network configuration details, follow these steps. Save this information for later use to troubleshoot if you face network issues.

  1. Open the navigation menu. Under Oracle Database, click Exadata Cloud@Customer.
  2. Under Region, select the region that you want to associate with the Oracle Exadata infrastructure.

  3. Click Exadata Infrastructure.
  4. From the list of infrastructures, click the name of the infrastructure that you're interested in. Note that the infrastructure must be in Active state.
  5. On the Infrastructure Details page, find the network configuration details under the Network section.

Using the Console to Edit Oracle Exadata Database Service on Cloud@Customer Infrastructure Networking Configuration

To edit your Oracle Exadata Database Service on Cloud@Customer infrastructure networking configuration, be prepared to provide values for the infrastructure configuration.

You can only edit Oracle Exadata Database Service on Cloud@Customer infrastructure networking configuration only if the current state of the Oracle Exadata infrastructure is Requires Activation. Also, ensure that you do not edit the Exadata infrastructure after you download the configuration file and provide it to Oracle.

  1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  2. Select Region and Compartment, and provide the region and the compartment where the Oracle Exadata infrastructure you want to edit is located.
  3. Click Exadata Infrastructure.
  4. Click the name of the Exadata infrastructure that you want to edit.

    The Infrastructure Details page displays information about the selected Oracle Exadata infrastructure.

  5. Click Edit Infrastructure Networking.
  6. Use the Edit Infrastructure Networking dialog to edit the Oracle Exadata infrastructure networking:

    1. Configure the cloud control plane network

      Each Oracle Exadata Database Service on Cloud@Customer system contains two Control Plane Servers, which enable connectivity to Oracle Cloud Infrastructure. The Control Plane Servers are connected to the control plane network, which is a subnet on your corporate network. The following settings define the network parameters:

      • Control Plane Server 1 IP Address: Provide the IP address for the first control plane server. This IP address is for the network interface that connects the first Control Plane Server to your corporate network using the control plane network.
      • Control Plane Server 2 IP Address: Provide the IP address for the second control plane server. This IP address is for the network interface that connects the second Control Plane Server to your corporate network using the control plane network.
      • Netmask: Specify the IP netmask for the control plane network.
      • Gateway: Specify the IP address of the control plane network gateway.
      • HTTP Proxy: Optionally, you can use this field to specify your corporate HTTP proxy to use for the HTTPS connection from the Control Plane Server to Oracle Cloud Infrastructure. The expected format is:
        http://server.domain:port

        For example:

        http://proxy.example.com:80

        For enhanced security, when possible, Oracle recommends that you use an HTTP proxy.

    2. Configure the Exadata system networks

      Each Oracle Exadata Database Service on Cloud@Customer system contains two system networks, which are not connected to your corporate network. The following settings define IP address allocations for these networks:

      • Administration Network CIDR Block: Specifies the IP address range for the administration network using CIDR notation. The administration network provides connectivity that enables Oracle to administer the Exadata system components, such as the Exadata compute servers, storage servers, network switches, and power distribution units.

        The maximum CIDR block prefix length is /23, which defines the smallest block of IP addresses that are required for the network. To allow for possible future expansion within Oracle Exadata Database Service on Cloud@Customer, a smaller CIDR block prefix length is recommended, which reserves more IP addresses for the network. The minimum CIDR block prefix length is /16.

        Ensure that the IP address range does not conflict with other hosts your corporate network, and does not overlap with the InfiniBand network CIDR block.

      • InfiniBand Network CIDR Block: Specifies the IP address range for the Exadata InfiniBand network using CIDR notation. The Exadata InfiniBand network provides the high-speed low-latency interconnect used by Exadata software for internal communications between various system components.

        The maximum CIDR block prefix length is /22, which defines the smallest block of IP addresses that are required for the network. To allow for possible future expansion within Oracle Exadata Database Service on Cloud@Customer, a smaller CIDR block prefix length is recommended, which reserves more IP addresses for the network. The minimum CIDR block prefix length is /19.

        Ensure that the IP address range does not conflict with other hosts your corporate network, and does not overlap with the administration network CIDR block.

    3. Configure DNS and NTP services

      Each Oracle Exadata Database Service on Cloud@Customer system requires access to Domain Names System (DNS) and Network Time Protocol (NTP) services. The following settings specify the servers that provide these services to the Exadata infrastructure:

      • DNS Servers: Provide the IP address of a DNS server that is accessible using the control plane network. You can specify up to three DNS servers.
      • NTP Servers: Provide the IP address of an NTP server that is accessible using the control plane network. You may specify up to three NTP servers.
      • Time zone: The default time zone for the Exadata Infrastructure is UTC, but you can specify a different time zone. The time zone options are those supported in both the Java.util.TimeZone class and the Oracle Linux operating system.
        Note

        If you want to set a time zone other than UTC or the browser-detected time zone, then select the Select another time zone option, select a Region or country, and then select the corresponding Time zone.

        If you do not see the region or country you want, then select Miscellaneous, and then select an appropriate Time zone.

  7. Click Save Changes.

Using the Console to Download a File Containing Configuration Data

To download an Oracle Exadata Database Service on Cloud@Customer configuration file, complete this procedure.

  1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  2. Choose the Region and Compartment that contains the Oracle Exadata infrastructure for which you want to download a file containing the infrastructure configuration details.
  3. Click Exadata Infrastructure.
  4. Click the name of the Oracle Exadata infrastructure for which you want to download a file containing the infrastructure configuration details.

    The Infrastructure Details page displays information about the selected Oracle Exadata infrastructure.

  5. Click Download Configuration.

    Your browser downloads a file containing the infrastructure configuration details.

The generated configuration file includes all the relevant configuration details for the additional storage servers included as part of the create infrastructure flow.

When you provide the generated infrastructure configuration file to Oracle, ensure that it has not been altered in any way. Also, ensure that you do not edit the Oracle Exadata infrastructure after you download the configuration file and provide it to Oracle.

Using the Console to Activate Exadata Database Service on Cloud@Customer Infrastructure

To activate Oracle Exadata Database Service on Cloud@Customer infrastructure, ensure that you meet the prerequisites, and complete this procedure.

  • Ensure that you have added a primary contact. You cannot activate your infrastructure without adding a primary maintenance contact.
  • Locate the activation file. This file is supplied to you by Oracle after installation and initial configuration of your Oracle Exadata Database Service on Cloud@Customer system.
  • Ensure that the current state of your infrastructure is Requires Activation. You can only activate Oracle Exadata if its state is Requires Activation.
  1. Download the activation file.
  2. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  3. Choose Region and Compartment, and select the region and compartment that contains the Oracle Exadata infrastructure that you want to activate.
  4. Click Exadata Infrastructure.
  5. Click the name of the Oracle Exadata infrastructure that you want to activate.

    The Infrastructure Details page displays information about the selected Oracle Exadata infrastructure.

  6. Click Activate.

    The Activate button is only available if the Oracle Exadata infrastructure requires activation. You cannot activate Oracle Exadata infrastructure multiple times.

  7. Use the Activate dialog to upload the activation file, and then click Activate Now.

    The activation file includes all the relevant details for the additional storage servers included as part of the create infrastructure flow.

    After activation, the state of the Oracle Exadata infrastructure changes to Active.

Using the Console to Check the Status of Exadata Database Service on Cloud@Customer Infrastructure

To find the status of your Oracle Exadata Database Service on Cloud@Customer infrastructure, use this procedure to check the Infrastructure Details page.

  1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  2. Choose the Region and Compartment that contains the Oracle Exadata infrastructure that you are interested in.
  3. Click Exadata Infrastructure.
  4. Click the name of the Oracle Exadata infrastructure that you are interested in.

    The Infrastructure Details page displays information about the selected Oracle Exadata infrastructure.

  5. Check the icon on the Infrastructure Details page. The color of the icon and the text below it indicates the status of the Oracle Exadata infrastructure.

    • Creating: Yellow icon. The Oracle Exadata infrastructure definition is being created in the control plane.
    • Requires Activation: Yellow icon. The Oracle Exadata infrastructure is defined in the control plane, but it must be provisioned and activated before it can be used.
    • Active: Green icon. The Oracle Exadata infrastructure is successfully provisioned and activated.
    • Deleting: Gray icon. The Oracle Exadata infrastructure is being deleted by using the Console or API.
    • Deleted: Gray icon. The Oracle Exadata infrastructure is deleted, and is no longer available. This state is transitory. It is displayed for a short time, after which the Oracle Exadata infrastructure is no longer displayed.
    • Activation Failed: Red icon. An error condition currently prevents the activation of the Oracle Exadata infrastructure. Typically, this state is auto-correcting, and does not require user intervention.

Using the Console to Scale Infrastructure Storage

To scale infrastructure storage, complete this procedure.

You can scale infrastructure storage when the current state of the Oracle Exadata infrastructure is Active or Requires Activation.

  1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  2. Choose the Region and Compartment that contains the Oracle Exadata infrastructure that you are interested in.
  3. Click Exadata Infrastructure.
  4. Click the name of the Oracle Exadata infrastructure for which you want to download a file containing the infrastructure configuration details.

    The Infrastructure Details page displays information about the selected Oracle Exadata infrastructure.

  5. Click Scale Infrastructure Storage.
  6. Select the number of storage servers from the Additional storage servers field.
  7. Click Scale Infrastructure.

Using the Console to Download Scale Infrastructure Storage Configuration File

To download an Oracle Exadata Cloud@Customer scale configuration file, complete this procedure.

  1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  2. Choose the Region and Compartment that contains the Oracle Exadata infrastructure that you are interested in.
  3. Click Exadata Infrastructure.
  4. Click the name of the Oracle Exadata infrastructure for which you want to download a file containing the infrastructure configuration details.

    The Infrastructure Details page displays information about the selected Oracle Exadata infrastructure.

  5. Click Download New Configuration.

    Your browser downloads a file containing the infrastructure configuration details.

    Note

    When you provide the generated infrastructure configuration file to Oracle, ensure that it has not been altered in any way. Also, ensure that you do not edit the Oracle Exadata infrastructure after you download the configuration file and provide it to Oracle.

Using the Console to Activate New Storage Servers

To download an Oracle Exadata Cloud@Customer scale configuration file, complete this procedure.

Upload the activation file once the field engineer finishes deploying the storage servers and shares the activation file with you.
Note

Once the activation file is uploaded and the activate process is initiated, you cannot change the Scale Infrastructure request or cancel this whole operation. If there is an activation failure, then contact the field engineer to resolve the issue.

  1. Download the activation file.
  2. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  3. Choose the Region and Compartment that contains the Oracle Exadata infrastructure that you are interested in.
  4. Click Exadata Infrastructure.
  5. Click the name of the Oracle Exadata infrastructure that you want to activate.

    The Infrastructure Details page displays information about the selected Oracle Exadata infrastructure.

  6. Click Activate New Storage Server(s).

    The Activate button is only available if the Oracle Exadata infrastructure requires activation. You cannot activate Oracle Exadata infrastructure multiple times.

  7. Use the Activate New Server dialog to upload the activation file, and then click Activate Now.

    After activation, the state of the Oracle Exadata infrastructure changes to Active.

Using the Console to Make Storage Capacity from New Server Available for VM Clusters Consumption

To make storage capacity from the new servers for VM clusters consumption, complete this procedure.

  1. Download the activation file.
  2. Open the navigation menu. Under Oracle Databases, click Exadata Database Service on Cloud@Customer.
  3. Choose the Region and Compartment that contains the Oracle Exadata infrastructure that you are interested in.
  4. Click Exadata Infrastructure.
  5. Click the name of the Oracle Exadata infrastructure that you want to activate.

    The Infrastructure Details page displays information about the selected Oracle Exadata infrastructure.

  6. Click Add Storage Capacity.
  7. Review the advisory on the Add Storage Capacity dialog, and then click Add Storage Capacity.
Note

While Add Storage Capacity operation is in progress,
  • The system rebalances the storage to ensure that the capacity from the newly added storage servers is available for VM Cluster consumption. This rebalance will run with a ASM power limit of 4 independent of what you have set within your ASM configuration. If you would like the rebalance to complete faster, you can update the power limit after the rebalance process has begun. Monitor the ASM rebalance process to ensure it successfully completes (which will allow the add storage capacity workflow to complete).
  • You cannot create or delete VM Clusters.
  • Existing VM Clusters provisioned are in the Available life cycle state. However, they do not support scale up or down of resources allocated to the VM cluster, except for OCPU allocation. OCPU allocation changes are allowed even while Add Storage Capacity operation is in progress.

Using the Console to View Details of Exadata Cloud@Customer Infrastructure with Scaled Storage Capacity

To view the storage capacity from the new storage server use this procedure.

  1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  2. Choose the Region and Compartment that contains the Oracle Exadata infrastructure that you are interested in.
  3. Click Exadata Infrastructure.

    After changing the storage capacity, Shape will change to either Elastic or Elastic Base.

    Note

    When you perform scale VM Cluster Exadata storage operation, newly added Exadata storage capacity is also available for consumption. Similarly, when you create a VM cluster, the Console displays the newly added Exadata storage capacity (shared Exadata storage) as available storage.

Using the Console to Move Exadata Database Service on Cloud@Customer Infrastructure

To relocate Oracle Exadata Database Service on Cloud@Customer infrastructure to another compartment, use this procedure.

You can change the compartment that contains your Exadata Database Service on Cloud@Customer infrastructure by moving it.

When you move Exadata infrastructure, the compartment change is also applied to the associated VM cluster networks. However, the compartment change does not affect any other associated resources, such as the VM clusters, which remain in their current compartment.

To move Oracle Exadata Database Service on Cloud@Customer infrastructure:

  1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  2. Select Region and Compartment, and provide the region and compartment that contains the Oracle Exadata infrastructure that you want to move.
  3. Click Exadata Infrastructure.
  4. Click the name of the Exadata infrastructure that you want to move.

    The Infrastructure Details page displays information about the selected Oracle Exadata infrastructure.

  5. Click Move Resource.
  6. In the resulting dialog, choose the new compartment for the Oracle Exadata infrastructure, and click Move Resource.

Using the Console to Delete Exadata Database Service on Cloud@Customer Infrastructure

To delete Oracle Exadata Database Service on Cloud@Customer infrastructure, complete the prerequisites, and then complete this procedure.

Deleting Exadata Database Service on Cloud@Customer infrastructure removes it from the Cloud Control Plane.

If you are deleting Oracle Exadata infrastructure before activation, then if required, you can create replacement Oracle Exadata infrastructure without any input from Oracle.

If you are deleting active Oracle Exadata infrastructure, then to create replacement Oracle Exadata infrastructure, you must repeat the full provisioning process, including the tasks that Oracle performs.

Before you can delete active Exadata infrastructure, you must:

  • Terminate all of the resources that it contains, including the databases, VM cluster, and VM cluster network.
  • Lodge a service request (SR) with Oracle indicating your intention to delete the Oracle Exadata infrastructure. In response to the SR, Oracle flags the Oracle Exadata infrastructure as ready for deletion.

After Oracle has flagged the Oracle Exadata infrastructure, delete the Exadata infrastructure by using the following process:

  1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  2. Select Region and Compartment, and provide the region and compartment that contains the Oracle Exadata infrastructure that you want to delete.
  3. Click Exadata Infrastructure.
  4. Click the name of the Oracle Exadata infrastructure that you want to delete.

    The Infrastructure Details page displays information about the selected Oracle Exadata infrastructure.

  5. Click Delete.
  6. In the resulting dialog, enter the Oracle Exadata infrastructure name and click Delete Exadata Infrastructure to confirm the action.

Using the Console to Manage Tags for Your Exadata Cloud@Customer Resources

  1. Open the navigation menu. Under Oracle Database, click Exadata Cloud@Customer.
  2. Choose your Compartment.
  3. Find the Exadata Infrastructure, VM Cluster Network, VM Cluster, Backup Destination, Database Home, or Database resource you're interested in, and click the name.
  4. Click the Tags tab to view or edit the existing tags. Or, click More Actions and then Apply Tags to add new ones.

Managing Infrastructure Maintenance Contacts

Learn to manage your Exadata infrastructure maintenance contacts.

View Primary Maintenance Contact

You must associate primary contact with the Customer Support Identifier (CSI).

  1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  2. Select Region and Compartment, and provide the region and compartment that contains the Oracle Exadata infrastructure for which you want to view contact details.
  3. Click Exadata Infrastructure.
  4. Click the name of the Oracle Exadata infrastructure for which you want to view contact details.

    The Infrastructure Details page displays information about the selected Oracle Exadata infrastructure.

  5. Find the CSI and the primary contact under Maintenance.
    The operations team sets the infrastructure maintenance Service Level Objective (SLO) to Degraded:
    • If the primary contact CSI verification has failed.
    • If the primary contact is missing.
    • If the primary contact is verified and unresponsive.
    Also, a warning message is displayed on the Console as follows:
    "Ensure that the primary contact associated with your Customer Support Identifier (CSI) is available for Oracle support to coordinate maintenance-related activities. 
    The infrastructure maintenance Service Level Objective (SLO) is set to degraded status without proper primary contact."

    Add a primary contact before you activate the infrastructure.

Add Secondary Contacts

You can add up to nine secondary contacts.

  1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  2. Select Region and Compartment, and provide the region and compartment that contains the Oracle Exadata infrastructure for which you want to add secondary contacts.
  3. Click Exadata Infrastructure.
  4. Click the name of the Oracle Exadata infrastructure for which you want to add secondary contacts.

    The Infrastructure Details page displays information about the selected Oracle Exadata infrastructure.

  5. Click Manage Contacts.
  6. In the Manage Exadata Infrastructure Contacts window, click Add Contact.
  7. In the Add Contacts window, add contact details.
  8. Click Add Contacts.
Edit Maintenance Contacts

Edit maintenance contacts to update details.

  1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  2. Select Region and Compartment, and provide the region and compartment that contains the Oracle Exadata infrastructure for which you want to edit maintenance contact details.
  3. Click Exadata Infrastructure.
  4. Click the name of the Oracle Exadata infrastructure for which you want to edit maintenance contact details.

    The Infrastructure Details page displays information about the selected Oracle Exadata infrastructure.

  5. Click Manage Contacts.
  6. In the Manage Exadata Infrastructure Contacts window, click the actions button, and then select Edit Contact.
  7. In the Edit Contacts window, edit the details.
  8. Click Save.
Promote a Secondary Contact to Primary

You can promote a secondary contact to primary. The current primary is automatically demoted to secondary.

  1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  2. Select Region and Compartment, and provide the region and compartment that contains the Oracle Exadata infrastructure for which you want to promote a secondary contact to primary.
  3. Click Exadata Infrastructure.
  4. Click the name of the Oracle Exadata infrastructure for which you want to promote a secondary contact to primary.

    The Infrastructure Details page displays information about the selected Oracle Exadata infrastructure.

  5. Click Manage Contacts.
  6. In the Manage Exadata Infrastructure Contacts window, click the actions button, and then select Make Primary.
  7. In the Promote to Primary Contact dialog, click Promote.
Remove a Secondary Contact

You can remove a secondary contact anytime you want to.

  1. Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
  2. Select Region and Compartment, and provide the region and compartment that contains the Oracle Exadata infrastructure for which you want to remove a secondary contact.
  3. Click Exadata Infrastructure.
  4. Click the name of the Oracle Exadata infrastructure for which you want to remove a secondary contact.

    The Infrastructure Details page displays information about the selected Oracle Exadata infrastructure.

  5. Click Manage Contacts.
  6. In the Manage Exadata Infrastructure Contacts window, click the actions button, and then select Remove.
  7. In the Remove Infrastructure Contact dialog, click Remove.

Using the API to Manage Exadata Cloud@Customer Infrastructure

Oracle Exadata Database Service on Cloud@Customer uses the same API as Oracle Cloud Infrastructure.

For information about using the API and signing requests, see "REST APIs" and "Security Credentials". For information about SDKs, see "Software Development Kits and Command Line Interface".

Use these API operations to manage Exadata Database Service on Cloud@Customer infrastructure:

  • ActivateExadataInfrastructure
  • CreateExadataInfrastructure
  • DeleteExadataInfrastructure
  • DownloadExadataInfrastructureConfigFile
  • GenerateRecommendedVmClusterNetwork
  • GetExadataInfrastructure
  • ListExadataInfrastructure
  • UpdateExadataInfrastructure
  • AddStorageCapacityExadataInfrastructure