Destination Database Is Read-only: super-read-only

Scenario

An error occurred while DTS was migrating full data based on a task that contains full data migration or synchronization. The error log information contains "The MySQL server is running with the --super-read-only option so it cannot execute this statement".

Keywords

--super-read-only

Possible Causes

The storage of the destination database is insufficient, which causes the destination database to be in the read-only state.

Solutions

1. Run the following command on the destination database to cancel the read-only state for the database:

   content_copy

   set global read_only=0

2. Check whether a process restart occurs due to out of memory (OOM) errors in the destination database. If so, increase the memory of the database.

3. After the database becomes writable, restart the task.