Help Center> Data Replication Service> Troubleshooting> Solutions to Failed Check Items> Destination DB Instance Statuses> Checking Whether the Destination Database Is Read-Only
Updated on 2022-09-21 GMT+08:00
View PDF

Checking Whether the Destination Database Is Read-Only

MySQL Migration, Synchronization, and Backward DR

Table 1 Checking whether the destination database is read-only

Check Item

Whether the destination database is read-only

Description

The destination database is read-only, and data cannot be written to the destination database.

Failure Cause and Handling Suggestion

Failure cause: The destination database is read-only.

Handling suggestion: Run the following commands to change the destination database to read/write and then, restart the database.

Sample commands:

set global read_only=0;

set global super_read_only=0;