Use the Console to check the state of a MySQL DB system.

1. Open the navigation menu, and select Databases. Under MySQL, click DB Systems.
2. Choose your compartment from the List Scope.
3. In the list of DB systems, find your DB system, and check the icon in the DB System State column. The color of the icon and the associated text indicate the status of the DB system. See DB System States.

Use the Console to start, stop, or restart a DB system.

1. Open the navigation menu, and select Databases. Under MySQL, click DB Systems.
2. Choose your compartment from the List Scope.
3. In the list of DB systems, find the DB system you want to start, stop, or restart, and do one of the following:
   • Choose the DB system by selecting the check box. Click the Actions button at the top of the page.
   • Click the Actions menu present on the same line as your DB system.
   • Click the name of the DB system to open the DB System Details page.
4. Click one of the following:
   • Start: Start a stopped DB system. After the DB system is started, the Stop action is enabled, and the Start option is disabled.
   • Stop: Stop a running DB system. After the DB system is powered off, the Start action is enabled.
   • Restart: Shut down a DB system, and restart it.
     Note
     
     Starting, stopping, or restarting a  DB system affects the attached HeatWave cluster. When a HeatWave cluster is stopped as a result of a stop or restart action on the DB system, the data loaded in the HeatWave cluster is lost and must be reloaded manually when the HeatWave cluster is restarted. The HeatWave recovery mechanism does not automatically reload data.
5. If you click Stop or Restart, the Stop (or Restart) DB System dialog box is displayed. Select one of the following shutdown types:
   • Fast: Flush dirty pages before shutting down the DB System. The DB system performs some flush operation during the next startup, increasing the duration of the startup.
   • Slow: Flush dirty pages and purge undo log pages for older transactions. The shutdown itself can take longer, but the subsequent startup is faster.
   • Immediate: Does not flush dirty pages and does not purge any undo log pages. It stops MySQL DB System immediately. Page flushing and log purging happen during the next startup, increasing the duration of the startup.
6. Click the Stop or Restart button, depending on the intended action.

Use the Console to edit your MySQL DB system.

1. Open the navigation menu, and select Databases. Under MySQL, click DB Systems.
2. Choose your compartment from the List Scope.
3. 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.
   The Edit DB System is displayed.
4. Click Edit.
5. 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.
     Note
     
     Changing the shape restarts the database.
   • 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.
   • Show advanced options: Click the option to view the advanced options such as Deletion Plan, Configuration, Management, and Tags.
6. (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.
   Note
   
   The Navigate to the DB System details page after closing the dialog check box is available only if you choose Edit from the Actions menu.
7. Click Save Changes.
   Note
   
   The DB system restarts only when you select a new configuration and not when you edit the Name or Description.

Use the Console to delete a DB system permanently.

1. Open the navigation menu, and select Databases. Under MySQL, click DB Systems.
2. Choose your compartment from the List Scope.
3. (Optional) If you have enabled Delete Protected on your DB system, click the name of the DB system to open the DB System Details page. Under Deletion Plan, click Disable present in front of the Delete Protected field.
4. In the list of DB systems, find the DB system you want to delete, and do one of the following:
   • Choose the DB system by selecting the check box, and click the Actions button at the top of the page.
   • Click the Actions menu present on the same line as your DB system.
   • Click the name of the DB system to open the DB System Details page, ánd click the More Actions button present at the top of the page.
5. Click Delete.
6. In the Delete DB Systems dialog box, select the Delete DB Systems permanently check box, and click Delete DB Systems.

MySQL Database Service tracks storage space utilization for a DB system and can warn you if there is a shortage of space on the disk. If you see these warnings, or know your storage needs will soon increase, take action to increase the storage space.

MySQL Health Monitor automatically sends warning messages if the free disk space for a DB system falls below 20%, 10%, and 5% of the available storage. If the DB system spends too long with too little free disk space or falls below its critical threshold, Health Monitor puts the MySQL server into a read-only fallback mode, which requires a reset. See Overview of Health Monitor.

You can also set up a custom alarm using the MySQL Database Service metric DbVolumeUtilization. The alarm sends a notification when disk space utilization reaches the level you set. See MySQL Database Service Metrics.

You can check the amount of disk space that is currently in use by these methods:

• Viewing the DbVolumeUtilization metric using the console. See Viewing Metrics of a DB System.
• Viewing Health Monitor's performance_schema.health_block_device table in MySQL Server's Performance Schema, using a command-line client such as MySQL Client or MySQL Shell. See Checking Health Monitor Data Using a Command-Line Client.

You can increase the amount of storage available to the DB system by these methods:

• For a DB system that is running MySQL Server 8.0.27-u3-cloud or a higher version (see MySQL Server Upgrades), by using an action in the console. See Increasing the Storage of a DB System Using the Console.
• For any MySQL Server version, by backing up the DB system and moving it to a new DB system that has a larger storage size. See Increasing the Storage of a DB System by Backup and Restore Using the Console.

Use the Console to manage tags on DB systems and resources.

1. Open the navigation menu, and select Databases. Under MySQL, select the resource you want to manage.
2. Choose your compartment from the List Scope.
3. In the list of resources, find the resource for which you want to manage tags, and do one of the following:
   • Choose the resource by selecting the check box. Click the Actions button at the top of the page.
   • Click the Actions menu present on the same line as your resource.
   • Click the name of the resource to open the Details page. For DB systems and channels, click More Actions present at the top of the page.
4. Click Add Tags.
5. On the Add Tags dialog box, specify the Tag Namespace, Tag Key, and Tag Value.
6. (Optional) If you want to add more tags, click +Another Tag.
7. Click Add Tags.

Use the Console to enable or disable high availability on your DB system.

• Enabling High Availability on a DB System Using the Console: Creates a highly available DB system using the existing MySQL instance as the primary, creating two secondary instances, and replicating the primary's data to the secondaries.
  Note
  
  You cannot enable high availability on HeatWave DB systems.
• Disabling High Availability Using the Console: Creates a standalone DB system from a highly available one using the preferred primary instance.

Use the Console to enable or disable crash recovery on a DB system.

1. To disable crash recovery on a DB system, do the following:
   1. Open the Disable crash recovery dialog box from one of the following locations:
      • The Disable crash recovery menu item from the More Actions menu on the DB systems list page.
      • The Disable crash recovery menu item from the More Actions drop-down menu on the DB system Details page.
      • The Disable link adjacent the crash recovery label on the DB system Details page. This link is only displayed if automatic backups are disabled.
      The Disable crash recovery dialog is displayed.
   2. Click Disable to disable crash recovery.
      The DB system enters the UPDATING state and crash recovery is disabled.
2. To enable crash recovery on a DB system, do the following:
   1. Open the Enable crash recovery dialog box from one of the following locations:
      • The Enable crash recovery menu item from the More Actions (3-dot) menu on the DB systems list page.
      • The Enable crash recovery menu item from the More Actions drop-down menu on the DB system Details page.
      • The Enable link adjacent the crash recovery label on the DB system Details page.
      The Enable crash recovery dialog is displayed.
   2. Click Enable to enable crash recovery.
      The DB system enters the UPDATING state and crash recovery is enabled.

      Note
      
      Automatic backups are not automatically enabled. You must enable them manually.

Use the command-line interface to view the details of a DB system.

1. Open a command prompt and run the following command:

   oci mysql db-system get --db-system-id <DBSystemOCID>

{
  "data": {
    "availability-domain": "fblN:US-ASHBURN-AD-2",
    "backup-policy": {
      "is-enabled": true,
      "retention-in-days": 7,
      "window-start-time": "00:00",
      "pitr-policy": {   
        "is-enabled": true
      },
    "compartment-id": "ocid1.compartment.oc1...<AlphaNumericString>",
    "configuration-id": "ocid1.mysqlconfiguration.oc1...<AlphaNumericString>",
    "data-storage-size-in-gbs": 50,
    "defined-tags": {
      "Oracle-Tags": {
        "CreatedBy": "userName",
        "CreatedOn": "2020-06-24T16:20:02.957Z"
      }
    },
    "description": "This is my DBSystem",
    "display-name": "MyDBSystem",
    "endpoints": [
      {
        "hostname": null,
        "ip-address": "10.0.1.15",
        "modes": [
          "READ",
          "WRITE"
        ],
        "port": 3306,
        "port-x": 33060,
        "status": "ACTIVE",
        "status-details": null
      }
    ],
    "fault-domain": "FAULT-DOMAIN-1",
    "freeform-tags": {
      "prod": "doc"
    },
    "hostname-label": null,
    "id": "ocid1.mysqldbsystem.oc1...<AlphaNumericString>",
    "ip-address": "10.0.1.28",
    "lifecycle-details": null,
    "lifecycle-state": "ACTIVE",
    "maintenance": {
      "window-start-time": "SUNDAY 13:40"
    },
    "mysql-version": "8.0.21",
    "point-in-time-recovery-details": {  
      "time-earliest-recovery-point": "2022-06-30T05:45:01+00:00",      
      "time-latest-recovery-point": "2022-06-30T06:30:01+00:00"
    },
    "port": 3306,
    "port-x": 33060,
    "shape-name": "VM.Standard.E2.1",
    "source": null,
    "subnet-id": "ocid1.subnet.oc1.iad...<AlphaNumericString>",
    "time-created": "2020-06-24T16:20:04.683000+00:00",
    "time-updated": "2020-07-05T13:56:15.851000+00:00"
  }
}

MySQL Database Service events enables you to create rules that send a notification whenever the state of a resource (such as DB system, backup, channel, configuration, and HeatWave) changes in your tenancy.

• MySQL Database: DB System Event Types
• MySQL Database: Backup Event Types
• MySQL Database: Channel Event Types
• MySQL Database: Configuration Event Types
• MySQL Database: HeatWave Event Types

Use the DB System Details page to see information about the DB system and the resources associated with it. You can get to this page by clicking the name of the DB system in the list of DB systems. To see the list, open the navigation menu, and select Databases, and under MySQL, click DB Systems. Choose your compartment from the List Scope.

The billing of the DB system starts at the end of the Creating state, and is billed during the Active, Updating, and Deleting state.

Stopping a DB system stops billing for all OCPUs associated with it. However, billing continues for storage. Billing for OCPUs resumes if you restart the DB system.

If you delete a DB system, the billing stops at the end of the Deleting state. You are not billed when the DB system is in the Inactive, Deleted, or Failed state.