Data Management:FAQ about database logon

How do I enter the valid database account and password?

The following steps show how to log on to a database in the DMS console. In this example, an ApsaraDB RDS for MySQL instance is used. The database account is the user account. The database password is the password of the user account.

1. Obtain the database account and password.

   1. Go to the Instances page in the ApsaraDB RDS console, find the instance to which you want to log on, and then click its name.

   2. In the left-side navigation pane, click Accounts to view the account name.

      

      Note

      If you forget the password, click Reset Password in the Actions column of the account. For more information, see Reset the password of an account on an ApsaraDB RDS for MySQL instance.

2. Log on to the database.

   1. In the upper part of the instance details page, click Log On to Database. You are navigated to the DMS console. The Log on to Database Instance dialog box appears.

   2. Enter the account name in the Database Account field.

      

   3. Enter the password in the Database Password field.

      Note

      Do not copy and paste the database password.

   4. In the upper-right corner of the page, click Login.

What do I do if I fail to log on to the database in DMS and the message indicating that the database access is denied appears?

This error occurs for the following reasons:

• The database account or password is invalid.

  In this case, re-enter the database account and password and then click Login.

• The current account does not have the required permissions on databases.

  In this case, check whether your account has database permissions. If not, contact the administrator to grant database permissions to your account.

• The instance cannot be accessed from the current IP address.

  In this case, you must allow the current IP address to be used to access the instance or add the IP addresses and CIDR blocks of DMS to the IP address whitelist of the database instance. For more information, see Authorize an account to access its authorized databases from specified IP addresses or Configure an IP address whitelist.

What do I do when I log on to the instance in DMS and the message indicating that the instance has been disabled appears?

This message appears when the Security Collaboration mode that you purchased for your instance has expired. You can handle this issue by using one of the following methods based on your business requirements:

• To continue using the Security Collaboration mode, purchase the Security Collaboration mode and log on to the instance again. For more information, see Purchase a feature of DMS.

• If you no longer need to use the Security Collaboration mode, log on to the DMS console. In the left-side navigation pane, right-click the instance and choose Control Mode > Flexible Management. Then, log on to the instance again.

  

What do I do if the SSL certificate expires?

If the SSL certificate expires, update the expiration time. For more information about how to update the validity period of a certificate, see the corresponding Alibaba Cloud database topics, such as Use a cloud certificate to enable SSL encryption, Configure a custom certificate to enable the SSL encryption feature, and Configure SSL encryption.

What do I do if I am prompted a whitelist issue when I register an ApsaraDB instance with DMS?

You can click Configure Whitelist in the Whitelist issues dialog box. DMS automatically adds the IP address of the DMS server to the whitelist of the ApsaraDB instance. If the IP address fails to be automatically added to the whitelist, you need to manually add it to the whitelist. For more information, see Add DMS IP addresses and CIDR blocks to security settings.

What do I do if I fail to log on to an ApsaraDB for Redis instance in DMS and the system prompts that SSL connection must be used to connect the database instance after I enable TLS or SSL encryption for the instance?

You must enable SSL for the instance in DMS. To enable SSL for the instance in DMS, perform the following steps:

What do I do if I fail to log on to an ApsaraDB RDS instance in DMS and the message indicating that the access source is invalid appears?

If you use a Resource Access Management (RAM) user, perform the following steps to troubleshoot the issue:

1. Check whether you can log on to DMS.

2. Add the IP addresses of DMS to the IP address whitelist of the database instance. For more information, see Add DMS IP addresses and CIDR blocks to security settings.

3. Refresh the page and log on to the instance again.

What do I do if the following error message occurs when I log on to an ApsaraDB RDS instance?

NULL: 
com.ali.idbcloud.commons.multi.instance.session
service.AbstractAliyunWhiteListUserSessionServi
ce.throwConnectDBFailReason(AbstractAliyunWhite
ListUserSessionService.java:97)com.ali.idbcloud
.commons.multi.instance.sessionservice.BaseUser
SessionService.doLoginCore(BaseUserSessionServi
ce.java:924)com.ali.idbcloud.commons.multi.inst
ance.sessionservice.BaseUserSessionService.worl
dLogin(BaseUserSessionService.java:968)

In most cases, this error occurs in the old version of DMS Personal Edition. The old version of DMS Personal Edition is discontinued. To go to the DMS console of the new version, click Go to New DMS in the upper-right corner of the page.

What do I do if I fail to log on to an ApsaraDB RDS for MySQL instance and the system prompts that the instance does not exist?

Log on to the ApsaraDB RDS console. On the Instances page, check whether the instance to which you want to log on is in the normal state. If the instance status is normal, refresh the DMS console to synchronize the metadata of the instance. If the instance status is abnormal, troubleshoot the issue.

What do I do if the system prompts that I temporarily cannot access the instance by using DMS?

This error occurs because the instance owner or DMS administrator does not grant permissions on instance logon to your account. In this case, contact the DMS administrator to grant permissions on instance logon to your account. For more information, see the Manage permissions as a DMS administrator section of the "Manage permissions" topic.

What do I do if the "Communications link failure" message appears and the time consumed for connection is displayed when DMS connects to a MySQL database?

• If the time consumed for connection is 0 milliseconds, the "Communications link failure" error may occur for the following reasons: the database account or password is invalid, no whitelist is configured, and the whitelist is incorrectly configured. For more information about how to configure a whitelist, see Add DMS IP addresses and CIDR blocks to security settings.

• If the time consumed for connection is a few milliseconds or tens of milliseconds, check whether SSL is enabled for the instance and whether the SSL certificate expires.

What do I do if the "Failed to establish the connection, which may be due to an invalid database password, incorrect whitelist settings, or improper configuration of instance logon-free mode" message appears when I log on to the Alibaba Cloud instance in DMS?

Perform the following steps to troubleshoot the issue:

• Check whether the password of the database account is correct.

• Check whether the IP address of DMS is added to the whitelist of the instance. For more information about the IP addresses and CIDR blocks of DMS, see Add DMS IP addresses and CIDR blocks to security settings.

• Check whether security hosting (password-free logon) is enabled for the instance in DMS.

If the issue still persists, we recommend that you log on to the instance by using the endpoint of the instance or remove the instance from DMS and try to log on to the instance again.

What do I do if the "InvalidDBInstanceName.NotFound:The specified DB instance name does not exist." message appears when I log on to an ApsaraDB RDS instance in DMS?

This error message indicates that the instance name does not exist. Go to the instance console to check whether the instance exists and whether the instance name is correct. If the instance is running properly and the instance name is correct, contact DMS technical support.