vpruthi/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
doc-exports/docs/drs/umn/drs_11_0014.html
Wang , Deng Ke 5523220f09 DRS UMN 20221102 version 
Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>
Co-authored-by: Wang , Deng Ke <wangdengke2@huawei.com>
Co-committed-by: Wang , Deng Ke <wangdengke2@huawei.com>
2022-12-08 10:16:13 +00:00

6.0 KiB
Raw Permalink Blame History

Checking Whether the Source Database Binlog Is Enabled

MySQL Migration

Table 1 Checking whether the source database binlog is enabled

Check Item

Whether the source database binlog is enabled

Description

Check whether binlog is enabled for the source database.

Failure Cause and Handling Suggestion

Failure cause: This item cannot be checked because the source database fails to be connected.

Handling suggestion: Check whether the source database is connected.

Failure cause: Insufficient user permissions

Handling suggestion: Check whether the database user permissions meet the migration requirements.

NOTE:

For details about the required MySQL permissions and authorized operations, see Which MySQL Permissions Are Required for DRS?

Failure cause: An internal error occurs.

Handling suggestion: Contact technical support.

Failure cause: The binlog function is disabled on the source database.

Handling suggestion:

  • If the source is an on-premises database, perform the following operations to enable binlog.
    1. Run the following command to check whether binlog is enabled:
      show variables like "log_bin"\G;

    2. If binlog is disabled, add log-bin = mysql-bin followed by [mysqld] in the MySQL configuration file my.cnf or my.ini.

    3. Restart the database.

  • If the source is an RDS instance, enable binlog by referring to the RDS official documentation.
Parent topic: Database Parameters