Checking Whether the Source Database Name Is Valid
MySQL Migration
Check Item |
Whether the source database name is valid |
---|---|
Description |
The source database name cannot contain invalid characters. It must contain 1 to 64 characters, including only lowercase letters, digits, hyphens (-), and underscores (_). If the source database name contains any invalid character, the migration fails. |
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: The source database name cannot contain invalid characters. It must contain 1 to 64 characters, including only lowercase letters, digits, hyphens (-), and underscores (_). Handling suggestion: Change the source database names that contain unsupported characters or go back to the previous page and select the databases that do not contain unsupported characters. |
MongoDB Migration
Check Item |
Whether the source database name is valid |
---|---|
Description |
If the source database name contains invalid characters, the migration fails. |
Failure cause: The source database names cannot contain the following special characters: .<>' Handling suggestion: Change the source database names that contain unsupported characters or go back to the previous page and select the databases that do not contain unsupported characters. |
Oracle Migration
Check Item |
Whether the source database name is valid |
---|---|
Description |
The source database names cannot contain non-ASCII characters or special characters .><\`|,?'!" If the source database name contains invalid characters, the migration fails. |
Failure cause: The source database names contain unsupported characters. Handling suggestion: Change the source database names that contain unsupported characters or go back to the previous page and select the databases that do not contain unsupported characters. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.