For certain deployments, you may want to expand beyond the maximum number of compute and storage servers supported within a single Exadata Infrastructure rack. With this enhancement to compute and storage expansion, you can now have additional compute and storage spanning multiple racks available for VM Clusters provisioned on the Exadata Infrastructure.

Base systems are not eligible for multirack expansion. Multi-rack applies only to the following shapes:

• X8M-2 standard shapes
• X9M-2 standard shapes

Note: Exadata Infrastructure with more than 8 compute or 12 storage servers require a multi-rack deployment.

The "multi-rack" selection will drive the maximum number of compute and storage servers you can specify in the server configuration.

• Single Rack:
  • All Systems: 8 compute and 12 storage
• Mulit-rack:
  • X7, X8, and all Base Systems: Not Applicable
  • X8M and X9M Sytems: 32 compute and 64 storage servers

Pre-deployment process:

• If multi-rack is required or desired, the FE will provide the customer with a JSON configuration file.
• The customer uploads the config file when creating or expanding the Exadata Infrastructure.

Deployment process:

• When the customer creates the infrastructure and selects multi-rack, they must upload the JSON so the control plane can correctly generate the config bundle for download. The JSON file will be used to properly configure the additional components. Uploading the JSON will only be mandatory for deployments identified as multi-rack.
• If a customer fails to identify an infrastructure as multi-rack and subsequently they determine it is multi-rack, they will have to delete that infrastructure and recreate it.
• If a customer expands an existing infrastructure and remains within a single rack (only adding servers), then there is no change to the current deployment process.
• When a customer expands an existing infrastructure and adds a new rack, or expands an infrastructure with an existing expansion rack, they will need to choose the multi-rack deployment type and upload a new Multi-Rack Configuration File (JSON).

For more information, see:

• Using the Console to Create Oracle Exadata Database Service on Cloud@Customer Infrastructure
• Using the Console to Download a File Containing Configuration Data
• Using the Console to Activate Exadata Database Service on Cloud@Customer Infrastructure
• Using the Console to Create a VM Cluster Network
• Using the Console to Validate a VM Cluster Network
• Using the Console to Scale Infrastructure Compute and Storage
• Using the Console to Download Scale Infrastructure Compute and Storage Configuration File
• Using the Console to Activate New Database and Storage Servers
• Using the Console to Add Another DB Server to the VM Cluster Network
• Using the Console to Add VMs to a Provisioned Cluster
• Using the Console to Remove a VM from a VM Cluster
• Using the Console to Remove DB Servers from a VM Cluster Network
• Using the Console to Edit a VM Cluster Network
• Using the Console to Make Storage Capacity from New Server Available for VM Clusters Consumption
• Using the Console to View Details of Exadata Cloud@Customer Infrastructure with Scaled Compute and Storage Capacity
• Compute Expansion Event Types