Provisioning Exadata Cloud@Customer Systems

Learn how to provision an Exadata Cloud@Customer system.

3.1 About Provisioning Oracle Exadata Cloud@Customer Systems

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

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

  1. You create the Oracle Exadata Cloud@Customer infrastructure.
  2. You generate a file containing the infrastructure configuration details, and provide it to Oracle.
  3. The Oracle Exadata 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 Cloud@Customer infrastructure by using the supplied activation file.

When the provisioning process is complete, the Oracle Exadata 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.

3.2 Required IAM Policy for Provisioning Servers

Review the identity access management (IAM) policy for provisioning Oracle Exadata Cloud@Customer systems.

A policy is An IAM document that specifies who has what type of access to your resources. It is used in different ways: to mean an individual statement written in the policy language; to mean a collection of statements in a single, named "policy" document (which has an Oracle Cloud ID (OCID) assigned to it); and to mean the overall body of policies your organization uses to control access to resources.

A compartment is a collection of related resources that can be accessed only by certain groups that have been given permission by an administrator in your organization.

To use Oracle Cloud Infrastructure, you must be given the required type of access in a policy written by an administrator, whether you're using the Console, or the REST API with a software development kit (SDK), a command-line interface (CLI), or some other tool. If you try to perform an action, and receive a message that you don’t have permission, or are unauthorized, then confirm with your administrator the type of access you've been granted, and which compartment you should work in.

For administrators: The policy in "Let database admins manage DB systems" lets the specified group do everything with databases, and related database resources.

If you're new to policies, then see "Getting Started with Policies" and "Common Policies". If you want to dig deeper into writing policies for databases, then see "Details for the Database Service".

3.3 Prerequisites for Provisioning Oracle Exadata Cloud@Customer Servers

Before you provision your X8-2 and X7-2 servers, you must set up tenancy, and your network and other infrastructure must meet requirements.

  • Before you can provision Exadata Cloud@Customer infrastructure, your Oracle Cloud Infrastructure tenancy must be enabled to use Oracle Exadata Cloud@Customer. Review the information in this publication, and contact Oracle for further details.
  • In preparation for the provisioning process, ensure that your corporate data center and network infrastructure meet the requirements described in this publication.

3.4 Using the Console to Provision Oracle Exadata Cloud@Customer

Learn how to use the console to create your infrastructure, and to edit, download a configuration file, activate, and check the status of your infrastructure for Oracle Exadata Cloud@Customer.

3.4.1 Using the Console to Create Infrastructure

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

  1. Open the navigation menu. Under Database, click Exadata 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.

      See also 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 details, 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.
    • Configure the cloud control plane network

      Each Oracle Exadata 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 is address 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.
      • HTTPS Proxy: (Optional) You can choose to use this field to specify your corporate HTTPS 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 HTTPS proxy.

    • Configure the Oracle Exadata system networks

      Each Oracle Exadata 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 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. 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 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 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 corresponging Time zone.

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

    • Show Advanced Options

      You have the option to configure advanced options.

      • Tags: (Optional) You can choose to apply tags. If you have permissions to create a resource, then you also have permissions to apply free-form tags to that resource. To apply a defined tag, you must have permissions 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.

3.4.2 Using the Console to Edit Oracle Exadata Cloud@Customer Infrastructure

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

You can only edit Oracle Exadata Cloud@Customer infrastructure networking 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 Database, click Exadata 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 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.
      • HTTPS Proxy: (Optional) You can use this field to specify your corporate HTTPS 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 HTTPS proxy.

    2. Configure the Exadata system networks

      Each Oracle Exadata 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 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 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 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 corresponging 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.

3.4.3 Using the Console to Download a File Containing Configuration Data

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

  1. Open the navigation menu. Under Database, click Exadata 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.

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.

3.4.4 Using the Console to Activate Exadata Cloud@Customer Infrastructure

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

  • Locate the activation file. This file is supplied to you by Oracle after installation and initial configuration of your Oracle Exadata Cloud@Customer system.
  • Ensure that your infrastructure current state 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 Database, click Exadata 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.

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

3.4.5 Using the Console to Check the Status of Exadata Cloud@Customer Infrastructure

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

  1. Open the navigation menu. Under Database, click Exadata 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.

3.4.6 Using the Console to Move Exadata Cloud@Customer Infrastructure

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

You can change the compartment that contains your Exadata 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 Cloud@Customer infrastructure:

  1. Open the navigation menu. Under Database, click Exadata 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.

3.4.7 Using the Console to Delete Exadata Cloud@Customer Infrastructure

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

Deleting Exadata 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.

In 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 Database, click Exadata 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.

3.5 Using the API for Oracle Exadata Cloud@Customer

Oracle Exadata 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 Cloud@Customer infrastructure:

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