Known Issues

This page lists known issues with Cloud SQL for MySQL, along with ways you can avoid or recover from these issues.

If you are experiencing issues with your instance, make sure you also review the Operational Guidelines, as well as the information in Diagnosing Issues.

Data durability and availability issues

  • Generated columns (MySQL 5.7 instances only)

    Due to an issue in MySQL, using generated columns might result in data corruption. For more information, see MySQL bug #82736.

Instance connection issues

  • Expired SSL/TLS certificates

    If your instance is configured to use SSL, go to the Cloud SQL Instances page in the GCP Console and open the instance. Open its SSL page and make sure that your server certificate is valid. If it has expired, you must add a new certificate and rotate to it. Learn more.

    For First Generation instances, you should also check your the expiration date of your client certificates, shown on the SSL page. If they have expired, you must create new client certificates before you can connect to your instance using SSL.

  • Cloud SQL Proxy version

    If you are connecting using the Cloud SQL Proxy, make sure you are using the most recent version. For more information, see Keeping the Cloud SQL Proxy up to date.

  • Not authorized to connect

    If you try to connect to an instance that does not exist in that project, the error message only says that you are not authorized to access that instance.

Administrative issues

  • Long-running operations cannot be cancelled or stopped

    When you start a long-running operation, such as an import or export operation, you cannot stop the operation before it completes. In addition, only one operation can run against an instance at at time.

    For this reason, make sure you do not need to do other work on an instance when you start a long-running operation.

  • Instance names cannot be reused immediately after instance deletion

    After you delete an instance, you cannot immediately reuse the instance name, because Cloud SQL reserves that name for a few days. If you need to quickly create and delete instances with the same name, consider using a timestamp as part of the name to avoid name conflicts.

  • Setting the time zone for MySQL instances

    It is possible to set the MySQL time zone to a named area, such as "Europe/Moscow", using a session variable. However, doing so is not supported, and is not guaranteed to provide up-to-date time settings. To change the default time zone for your instance, update the default_time_zone flag with the offset from UTC (for example, +10:00). Automatic adjustment to daylight savings time is not supported; you must update the default_time_zone flag manually to account for daylight savings time.

Issues with importing and exporting data

  • SQL dump files that contain views are not reimportable

    A SQL dump file that contains views cannot be imported into Cloud SQL, because views include a DEFINER clause, which requires the SUPER privilege. If you use Cloud SQL to export a database that includes views, that export cannot be imported back into a Cloud SQL for MySQL instance.

    To create a dump file from a database that has one or more views, with the goal of importing the dump file into Cloud SQL, you must exclude the views. For more information, see Exporting Data for Import into Cloud SQL.

  • CSV export does not format NULLs and newlines correctly

    When you export data as CSV using the Cloud SQL export feature, NULLs are exported as "N, which can cause the CSV file to contain unbalanced quotation marks. Additionally, if your text data contains a newline character, a trailing quote mark is added at the end of the line.

Was this page helpful? Let us know how we did:

Send feedback about...

Cloud SQL for MySQL