SQL Console

Q: I use Data Management Service (DMS) to log in to a MongoDB instance. When I execute an SQL statement, I receive the error 'Incomplete command. Please check.'

A: Some MongoDB commands require the new parser. Click Open Parser to switch to the new parser. For a complete list of commands supported by the new parser, see Supported MongoDB commands.

Q: After I log on to DMS and access the SQL Console, I receive the error "Authorization failed for the GetSqlConsoleExecutionHistory action on the acs:dms:*:*:sqlConsole/* resource. No permission policy matched."

A: This error indicates that your account does not have the GetSqlConsoleExecutionHistory permission. We recommend the following solutions:

• Use the Alibaba Cloud account (or an administrator account with management permissions) to grant the AliyunDMSFullAccess (DMS full management) permission to the current account. If you only need to query data in SQL Console, you can also grant the AliyunDMSReadOnlyAccess (DMS read-only) permission. Both permission policies include the GetSqlConsoleExecutionHistory permission. For more information about how to grant permissions, see Grant permissions to a RAM user.

• Create a custom permission policy that includes the GetSqlConsoleExecutionHistory permission and attach it to your account. The following example shows the required permission policy:

  {
  "Effect": "Allow",
  "Action": "dms:GetSqlConsoleExecutionHistory",
  "Resource": "acs:dms:::sqlConsole/*"
  }

  For more information about how to create a custom policy, see Create a custom policy.

Q: The SQL Console freezes, shows "Waiting for user action", or the connection is unstable when I execute an SQL statement. What should I do?

A: Refer to the following solutions based on your specific symptom:

• Frozen interface: Exit Simple mode and switch to Standard mode, or access DMS using your browser's incognito (private browsing) mode.

• "Waiting for user action" message: This typically means the SQL statement has not actually been sent to the database (no corresponding session exists in the real-time session list). Cancel the current task, re-execute the SQL statement, and verify that execution has started.

• Intermittent connection instability: Some features in the new DMS console have been taken offline due to known issues. We recommend switching back to the previous version of the DMS console and monitoring whether the connection becomes stable.

Q: How do I clear or edit the My SQL or Frequently Used SQL history?

A: The My SQL and Frequently Used SQL features in DMS SQL Console are still being improved. Clearing, deleting, or editing saved SQL history is not yet supported. If you need to clear the history, wait for a future version update or contact backend support for assistance.

Q: Selecting all SQL statements and executing them at once causes slow execution or a hang. What should I do?

A: Executing multiple SQL statements at once in the DMS SQL Console — for example, running CREATE TABLE and INSERT statements together — may cause slow processing or a hang. We recommend executing CREATE TABLE statements and INSERT statements separately.

Q: I cannot terminate a database process that was not created by me. What should I do?

A: For security reasons, DMS restricts users to terminating only the session threads they created themselves. You can use one of the following methods to terminate the process:

1. Ask the administrator or DBA who owns the account associated with the thread to log on to DMS or connect to the database directly to run the KILL command.

2. If you have management permissions for the ApsaraDB RDS instance, go to the ApsaraDB RDS console, navigate to Autonomy Service > Session Management for the target instance, search for the thread ID, and click End Session. This approach bypasses the DMS permission restrictions.