Supported Shapes
A shape is a template that determines the number of CPUs, amount of memory, and other resources that are allocated to a DB system, a HeatWave cluster node, or a read replica.
Both the DB system and the HeatWave cluster have their own shape. Read replicas can have the same or different shape as compared to the DB system.
- Standalone: Optimized for standalone DB systems and read replicas.
- HA: Optimized for highly available DB systems. See High Availability.
- ECPU Shapes
- OCPU Shapes (Deprecated as of Sept 5, 2024)
Related Topics
ECPU Shapes
Provide a pricing metric based on ECPU (Elastic Central Processing Unit) that is architecture-agnostic. Allow HeatWave clusters to be attached to any DB system based on ECPU shapes.
Table 5-1 ECPU Shapes for DB System and Read Replica
| ECPU Shape | ECPU Count | Memory (RAM in GB) | Max Network Bandwidth | Support Read Replica | Associated Configurations |
|---|---|---|---|---|---|
| MySQL.Free | 2 | 8 | 1 Gbps | No |
|
| MySQL.2 | 2 | 16 | 1 Gbps | No |
|
| MySQL.4 | 4 | 32 | 2 Gbps | No |
|
| MySQL.8 | 8 | 64 | 4 Gbps | Yes |
|
| MySQL.16 | 16 | 128 | 8 Gbps | Yes |
|
| MySQL.32 | 32 | 256 | 16 Gbps | Yes |
|
| MySQL.48 | 48 | 384 | 24 Gbps | Yes |
|
| MySQL.64 | 64 | 512 | 32 Gbps | Yes |
|
| MySQL.96 | 96 | 768 | 40 Gbps | Yes |
|
| MySQL.192 | 192 | 1326 | 40 Gbps | Yes |
|
| MySQL.256 | 256 | 1024 | 2 x 50 Gbps | Yes |
|
There is limited hardware availability for the MySQL.256 shape and customers should contact their Oracle sales representative for additional details. Customers who need help with provisioning and resolving issues with the MySQL.256 shape can contact Oracle Support.
All ECPU shapes support HeatWave cluster.
Table 5-2 Shapes for HeatWave cluster attached to an ECPU-shaped DB system
| Shape | Memory (RAM in GB) |
|---|---|
| HeatWave.Free (Supports 1 node only) | 16 |
| HeatWave.32GB (Supports a maximum of 16 nodes) | 32 |
| HeatWave.512GB (Recommended) | 512 |
OCPU Shapes
Provide architecture-specific shapes for DB systems, read replicas, and HeatWave clusters. Both AMD processors and Intel processors are available.
All OCPU shapes are deprecated and are not available to new users created after Sept 5, 2024.
All OCPU shapes become unavailable after March 13, 2026; existing users cannot use OCPU shape in new DB systems or read replicas and cannot change existing DB systems or read replicas to use OCPU shapes.
Table 5-3 OCPU Shapes for DB System and Read Replica (No HeatWave Cluster Support)
| OCPU Shapes | OCPUs | Memory (RAM in GB) | Max Network Bandwidth | Support Read Replica | Associated Configurations |
|---|---|---|---|---|---|
| MySQL.VM.Standard.E3.1.8GB | 1 | 8 | 1 Gbps | No |
|
| MySQL.VM.Standard.E3.1.16GB | 1 | 16 | 1 Gbps | No |
|
| MySQL.VM.Standard.E3.2.32GB | 2 | 32 | 2 Gbps | No |
|
| MySQL.VM.Standard.E3.4.64GB | 4 | 64 | 4 Gbps | Yes |
|
| MySQL.VM.Standard.E3.8.128GB | 8 | 128 | 8 Gbps | Yes |
|
| MySQL.VM.Standard.E3.16.256GB | 16 | 256 | 16 Gbps | Yes |
|
| MySQL.VM.Standard.E3.24.384GB | 24 | 384 | 24 Gbps | Yes |
|
| MySQL.VM.Standard.E3.32.512GB | 32 | 512 | 32 Gbps | Yes |
|
| MySQL.VM.Standard.E3.48.768GB | 48 | 768 | 40 Gbps | Yes |
|
| MySQL.VM.Standard.E3.64.1024GB | 64 | 1024 | 40 Gbps | Yes |
|
| MySQL.VM.Standard.E4.1.8GB | 1 | 8 | 1 Gbps | No |
|
| MySQL.VM.Standard.E4.1.16GB | 1 | 16 | 1 Gbps | No |
|
| MySQL.VM.Standard.E4.2.32GB | 2 | 32 | 2 Gbps | No |
|
| MySQL.VM.Standard.E4.4.64GB | 4 | 64 | 4 Gbps | Yes |
|
| MySQL.VM.Standard.E4.8.128GB | 8 | 128 | 8 Gbps | Yes |
|
| MySQL.VM.Standard.E4.16.256GB | 16 | 256 | 16 Gbps | Yes |
|
| MySQL.VM.Standard.E4.24.384GB | 24 | 384 | 24 Gbps | Yes |
|
| MySQL.VM.Standard.E4.32.512GB | 32 | 512 | 32 Gbps | Yes |
|
| MySQL.VM.Standard.E4.48.768GB | 48 | 768 | 40 Gbps | Yes |
|
| MySQL.VM.Standard.E4.64.1024GB | 64 | 1024 | 40 Gbps | Yes |
|
| MySQL.VM.Standard2.1.15GB | 1 | 15 | 1 Gbps | No |
|
| MySQL.VM.Standard2.2.30GB | 2 | 30 | 2 Gbps | No |
|
| MySQL.VM.Standard2.4.60GB | 4 | 60 | 4.1 Gbps | Yes |
|
| MySQL.VM.Standard2.8.120GB | 8 | 120 | 8.2 Gbps | Yes |
|
| MySQL.VM.Standard2.16.240GB | 16 | 240 | 16.4 Gbps | Yes |
|
| MySQL.VM.Standard3.1.8GB | 1 | 8 | 1 Gbps | No |
|
| MySQL.VM.Standard3.1.16GB | 1 | 16 | 1 Gbps | No |
|
| MySQL.VM.Standard3.2.32GB | 2 | 32 | 2 Gbps | No |
|
| MySQL.VM.Standard3.4.64GB | 4 | 64 | 4 Gbps | Yes |
|
| MySQL.VM.Standard3.8.128GB | 8 | 128 | 8 Gbps | Yes |
|
| MySQL.VM.Standard3.16.256GB | 16 | 256 | 16 Gbps | Yes |
|
| MySQL.VM.Standard3.24.384GB | 24 | 384 | 24 Gbps | Yes |
|
| MySQL.VM.Standard3.32.512GB | 32 | 512 | 32 Gbps | Yes |
|
| MySQL.VM.Optimized3.1.8GB | 1 | 8 | 4 Gbps | No |
|
| MySQL.VM.Optimized3.1.16GB | 1 | 16 | 4 Gbps | No |
|
| MySQL.VM.Optimized3.2.32GB | 2 | 32 | 8 Gbps | No |
|
| MySQL.VM.Optimized3.4.64GB | 4 | 64 | 16 Gbps | Yes |
|
| MySQL.VM.Optimized3.8.128GB | 8 | 128 | 32 Gbps | Yes |
|
| MySQL.VM.Optimized3.16.256GB | 16 | 256 | 40 Gbps | Yes |
|
These shapes do not support HeatWave cluster.
Table 5-4 OCPU Shapes for DB System with HeatWave Cluster Support
| Shape | OCPUs | Memory (RAM in GB) | Max Network Bandwidth | Associated Configuration |
|---|---|---|---|---|
| MySQL.HeatWave.VM.Standard (Recommended) | 16 | 512 | 16 Gbps |
|
| MySQL.HeatWave.VM.Standard.E3 (Not supported for new users created after 6 Nov 2023; existing users can still use it) | 16 | 512 | 16 Gbps |
|
| MySQL.HeatWave.BM.Standard | 128 | 2048 | 40 Gbps |
|
| MySQL.HeatWave.BM.Standard.E3 (Not supported for new users created after 6 Nov 2023; existing users can still use it) | 128 | 2048 | 40 Gbps |
|
These shapes support HeatWave cluster.
Table 5-5 Shapes for HeatWave Cluster attached to an OCPU-shaped DB system
| Shape | Memory (RAM in GB) |
|---|---|
| HeatWave.32GB (Supports a maximum of 16 nodes) | 32 |
| HeatWave.512GB (Recommended) | 512 |
| MySQL.HeatWave.VM.Standard | 512 |
| MySQL.HeatWave.VM.Standard.E3 (Not supported for new users; existing users can still use it) | 512 |
Converting a DB System from OCPU to ECPU
You can convert a DB system created with an OCPU shape to use an ECPU shape.
A DB system can have different setups. It can be a standalone or high availability DB system. It may have an attached HeatWave cluster and it may have one or more read replicas. These have to be taken into consideration when converting the DB system from OCPU to ECPU shape.
- Step 1: If the DB system has an attached HeatWave cluster that uses a HeatWave node based shape such as MySQL.HeatWave.VM.Standard, you need to convert the HeatWave cluster shape to a HeatWave capacity shape such as HeatWave.32GB or HeatWave.512GB.
- Step 2: If the DB system has an OCPU shape, you need to convert the DB system to use an ECPU shape. When you change the shape, you also need to change the configuration to a configuration that matches the shape. If the DB system uses a custom configuration, you should create a new custom configuration for the ECPU shape and copied the customized variables to the new configuration. See Creating a Custom Configuration for standalone DB system and Copying a Configuration for high availability DB system.
- Step 3: If the DB system has any read replica with overridden OCPU shapes, you need to convert each of them to ECPU shape. You also need to change the configuration to a configuration that matches the shape. Replicas that inherit the DB system shape will have its shape changed together with the DB system, in which case no replica specific action is required.
Alternatively, you can use the backup and restore method to create a new DB system with ECPU shape. If you have a custom configuration in the DB system or read replicas, you need to create a new custom configuration for the ECPU shape that you want to use. See Creating a Custom Configuration for standalone DB system and Copying a Configuration for high availability DB system.
Using the Console
Use the Console to convert a DB system from OCPU to ECPU.
- If you have a custom configuration for the OCPU shape, you should create a custom configuration for the ECPU shape with similar variable settings. See Creating a Custom Configuration for standalone DB system and Copying a Configuration for high availability DB system.
Using the CLI
Use the command-line interface to convert a DB system from OCPU to ECPU.
- A properly configured CLI installation and the requisite SSH keys. See Command Line Interface.
- The DB system Oracle Cloud Identifier (OCID).
- The configuration OCID of the ECPU shape.
Using Backup and Restore Method
Use the backup and restore method to convert a DB system from OCPU to ECPU.
The method cannot retain the IP addresses of the DB system and read replicas endpoints.
If you have a custom configuration for the OCPU shape, you should create a custom configuration for the ECPU shape with similar variable settings. See Creating a Custom Configuration for standalone DB system and Copying a Configuration for high availability DB system.