vpruthi/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
doc-exports/docs/drs/umn/drs_11_0019.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

7.8 KiB
Raw Permalink Blame History

Checking Whether the Source and Destination Database Table Names Are Consistent in Case Sensitivity

MySQL Migration

Table 1 Checking whether the source and destination database table names are consistent in case sensitivity

Check Item

Whether the source and destination database table names are consistent in case sensitivity

Description

Check whether the source and destination database names and table names are consistent in case sensitivity.

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.

Failure cause: The lower_case_table_names values in the source and destination databases must be the same.

Handling suggestion:

  • If you are migrating data out of the cloud, change the values of lower_case_table_names in the source and destination databases to the same.

    You are advised to change the parameter value in an empty database. For example, if the destination RDS DB instance is empty, run the following example command to change the lower_case_table_names value to the same as that in the source database: Sample command:

    set global lower_case_table_names=n;

    In the preceding command, n indicates the parameter value of the source database. After the modification, restart the database for the modification to take effect.

  • If you are migrating data out of the cloud, perform the following operations:

    If the destination database is a self-built database, modify the lower_case_table_names parameter of the destination database. Add lower_case_table_names=n under the [mysqld] tag in the MySQL configuration file my.cnf. n indicates the value of parameter same lower_case_table_names of the source database. The database must be restarted to make the change take effect.

    If the destination database is a cloud database, check whether the lower_case_table_names parameter can be modified. If not, contact technical support.

Failure cause: The lower_case_table_names parameter value of the destination database is different from that of the source database, and the source database contains uppercase database and table names.

Handling suggestion: Rectify the fault by referring to How Can I Migrate Databases or Tables Whose Names Contain Uppercase Letters?

Failure cause: The database is unavailable.

Handling suggestion: Contact technical support.

Failure cause: An internal error occurs.

Handling suggestion: Contact technical support.
Parent topic: Database Parameters