Editing a DB System

Use the Console to edit a DB system.

1. On the DB systems list page, select the DB system that you want to work with. If you need help finding the list page or the DB system, see Listing DB Systems - Using the Console.

   The details page opens and displays information about the DB system.

2. Select the Details tab.
3. Select Edit in any of the following fields:
   • Name
   • Description
   • Shape
   • Configuration
   • Delete protected
4. In the Edit DB system panel, update 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: Select 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: Select 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
     
     

     • If all changed variables are dynamic, the DB system incurs no downtime as no restart is required.
     • Changing one or more non-dynamic variables causes the DB system to restart. For a high availability DB system, it 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.
   • You can also update the advanced options such as Deletion Plan.
5. Click Update.
   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.