Data Management:Log on to a database

How do I find the correct database account and password?

The database account and password in DMS correspond to the user account and password on the database instance itself. The following steps use an ApsaraDB RDS for MySQL instance as an example.

Step 1: Get the account name

1. Go to the ApsaraDB RDS console and click the instance name on the Instances page.

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

Step 2: Log on to the database

1. At the top of the instance details page, click Log On to Database. The Log on to Database Instance dialog box opens in the DMS console.

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

3. Enter the password in the Database Password field.

   Note

   Type the password manually. Do not copy and paste it.

   

4. Click Login in the upper-right corner.

Why does DMS say "database access is denied"?

This error has three common causes:

• Wrong credentials: Re-enter the database account and password, then click Login.

• Insufficient permissions: Contact your DMS administrator to grant the required database permissions to your account.

• IP address not allowed: Add the current IP address to the instance whitelist, or add the DMS IP addresses and CIDR blocks to the whitelist. For details, see Authorize an account to access its authorized databases from specified IP addresses and Configure an IP address whitelist.

Why does the "Communications link failure" error appear when DMS connects to a MySQL database?

The fix depends on how long DMS spent trying to connect:

• 0 milliseconds: The connection was blocked immediately. Check for invalid credentials, a missing whitelist entry, or an incorrectly configured whitelist. For whitelist configuration, see Add DMS IP addresses and CIDR blocks to security settings.

• A few to tens of milliseconds: The connection reached the database but failed. Check whether SSL is enabled and whether the SSL certificate has expired.

Why does DMS say "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"?

Check the three most common causes in order:

1. Verify the database account password is correct.

2. Verify the DMS IP addresses are added to the instance whitelist. For the full list of IP addresses and CIDR blocks, see Add DMS IP addresses and CIDR blocks to security settings.

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

If the issue persists, try logging on using the endpoint of the instance directly, or remove the instance from DMS and try to log on to the instance again.

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

Click Configure Whitelist in the Whitelist issues dialog box. DMS automatically adds its server IP address to the ApsaraDB instance whitelist. If the automatic addition fails, add the IP addresses manually. For the complete list, see Add DMS IP addresses and CIDR blocks to security settings.

Why does DMS say "the instance has been disabled"?

The Security Collaboration mode purchased for the instance has expired. Handle this based on your requirements:

• To continue using Security Collaboration mode: Purchase the mode again, then log on to the instance. For details, see Purchase a feature of DMS.

• To switch to a different control mode: In the DMS console, right-click the instance in the left-side navigation pane and choose Control Mode > Flexible Management. Then log on to the instance again.

What do I do if the SSL certificate expires?

Update the certificate's validity period. Refer to the documentation for your database type:

Why does DMS say "SSL connection must be used" after I enable TLS or SSL for an ApsaraDB for Redis instance?

SSL is enabled on the Redis instance but not yet enabled in DMS. Enable SSL in DMS:

1. Log on to the DMS console V5.0.

2. In the left-side navigation pane, choose Database Instances > Instances Disconnected.

3. Right-click the ApsaraDB for Redis instance and click Edit.

4. In the Advanced Information section, set Enable SSL to Enable.

5. Click Test Connectivity.

6. After the test passes, click Save.

For details, see Modify database instances.

Why does DMS say "the access source is invalid" when I log on to an ApsaraDB RDS instance as a Resource Access Management (RAM) user?

1. Confirm that you can log on to DMS.

2. Add the DMS IP addresses to the instance whitelist. For details, see Add DMS IP addresses and CIDR blocks to security settings.

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

Why do I see a long Java stack trace starting with "NULL: com.ali.idbcloud..." when logging on?

This error appears in the old version of DMS Personal Edition, which has been discontinued. Click Go to New DMS in the upper-right corner to switch to the current version.

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)

Why does DMS say the ApsaraDB RDS for MySQL instance does not exist?

Log on to the ApsaraDB RDS console and check the instance status on the Instances page:

• Status is normal: Refresh the DMS console to synchronize the instance metadata.

• Status is abnormal: Troubleshoot the instance before logging on.

Why does DMS say I temporarily cannot access the instance?

The instance owner or DMS administrator has not granted you logon permissions for that instance. Contact your DMS administrator to grant the required permissions. For details, see the Manage permissions as a DMS administrator section in "Manage permissions."

Why does DMS say "InvalidDBInstanceName.NotFound: The specified DB instance name does not exist"?

Go to the instance console and verify that the instance exists and the instance name is correct. If the instance is running properly and the name is correct, contact DMS technical support.