Editing a DB System
You can edit the name, description, shape, configuration, and various advanced options of a DB system.
Using the Console
Use the Console to edit a DB system.
- Open the navigation menu, and select Databases. Under HeatWave MySQL, click DB systems.
- Choose your compartment from the List scope.
- In the list of DB systems, find the DB system you want to edit and do one of
the following:
- Click the name of the DB system to open the DB system details page.
- Click the Actions menu present on the same line as your DB system.
- Click Edit.The Edit DB system is displayed.
- In the Edit DB system panel, edit the following information:
- Name: Specify a user-friendly display name for the DB system. The name need not be unique as the Oracle Cloud Identifier (OCID) uniquely identifies the DB system.
- Description: Specify a brief description of the DB system and its purpose.
- Select a shape: Click Change shape to change the shape of the DB system. See Supported Shapes.
Note
- Changing the shape restarts the database and causes the data of an active HeatWave cluster to be reloaded automatically.
- Changing the shape of a high availability DB system changes the current primary placement without changing the preferred primary placement.
- Changing the shape of a DB system with read replicas also changes the shape of all read replicas that inherit the DB system shape.
- Changing the shape of an Always Free DB system is not supported on an Always Free tenancy.
- Changing the shape of an Always Free DB system to a payable shape in a paid or trial tenancy will convert it to a chargeable DB system where metering will be enabled for all resources used by the DB system.
- Select a configuration: Click Change configuration to change the configuration of the DB system. You can see the difference in the variables of the existing and the selected configuration under Compare configurations.
Note
- Changing one or more non-dynamic variables causes a standalone DB system to restart. If all changed variables are dynamic, the standalone DB system has no downtime as no restart is required.
- Changing the configuration of a high availability DB system causes a brief downtime and a change in the current primary placement as it performs a rolling update. There is no change to the preferred primary placement.
- Changing the configuration of a DB system with read replicas also changes the configuration of all read replicas that inherit the DB system shape.
- A DB system restart or a rolling update of a high availability DB system also causes the data of an active HeatWave cluster to be reloaded automatically.
- Show advanced options: Click the option to view the advanced options such as Deletion Plan, Configuration, Maintenance, and Tags.
- (Optional) Select the Navigate to the DB system details page after closing the dialog check box to open the DB system details page after closing the Edit DB system dialog box. If you do not select the check box, you return to the list of the DB systems. This check box is available only if you choose Edit from the Actions menu.
- Click Save changes.Note
The DB system restarts only when you change the Shape or select a Configuration that changes non-dynamic variables and not when you change the Name or Description.
Note
If you encounter
If you encounter
OutOfHostCapacity
work request error when trying to change the shape, see Resolving OutOfHostCapacity Error.
Related Topics