- What's New
- Function Overview
- Service Overview
- Billing
- Getting Started
-
User Guide
- Permissions Management
- Logging in to a DB Instance
-
MySQL
- Account Management
- Database Management
- SQL Operations
- Table Management
- View Management
- Stored Procedure Management
- Event Management
- Trigger Management
- Function Management
- Data Import and Export
- Data Generator (Not Promoted)
- Tracking and Rolling Back Data (Not Promoted)
- Task Management
- Table Structure Comparison and Synchronization (Not Promoted)
- Intelligent O&M (New Version)
- Intelligent O&M (Old Version)
- RDS for SQL Server
- PostgreSQL
-
RDS for MariaDB
- Account Management
- Database Management
- SQL Operations
- Table Management
- View Management
- Stored Procedure Management
- Event Management
- Trigger Management
- Function Management
- Data Import and Export
- Data Generator (Not Promoted)
- Task Management
- Table Structure Comparison and Synchronization (Not Promoted)
- Intelligent O&M
- GaussDB
-
TaurusDB
- Account Management
- Database Management
- SQL Operations
- Table Management
- View Management
- Event Management
- Stored Procedure Management
- Function Management
- Trigger Management
- Data Import and Export
- Data Generator (Not Promoted)
- Task Management
- Table Structure Comparison and Synchronization (Not Promoted)
- Intelligent O&M
- GeminiDB Cassandra
- GaussDB(DWS) (Unavailable Soon)
- DDS
- DDM
- Audit
- Event Monitoring
- Best Practices
-
API Reference
- Before You Start
- API Overview
- Calling APIs
-
APIs (in OBT)
- API Version Queries
-
Cloud DBA
- Registering a Database User
- Modifying a Database User
- Deleting a Database User
- Querying Intelligent O&M Quotas
- Querying Database User Information
- Querying Database Users
- Killing Sessions
- Querying the SQL Execution Plan (GET Request)
- Querying the SQL Execution Plan (POST Request)
- Querying Metadata Locks
- Querying Instance Sessions
- Querying InnoDB Lock Waits
- Enabling or Disabling SQL Explorer and Slow Query Log
- Querying Whether SQL Explorer and Slow Query Log Are Enabled
- Exporting Slow Query Logs
- Exporting SQL Explorer Data
- Querying Whether SQL Statement Concurrency Control Is Enabled
- Enabling or Disabling SQL Statement Concurrency Control
- Querying Concurrency Control Rules of SQL Statements
- Generate Keywords of a Concurrency Control Rule from the Original SQL Statement
- Creating a Concurrency Control Rule for SQL Statements
- Deleting a Concurrency Control Rule of SQL Statements
- Querying SQL Statement Concurrency Control Tasks
- Exporting the Top SQL Template List
- Exporting SQL Execution Time Distribution
- Exporting the Slow SQL Template List
- Viewing the Instance List on the Intelligent O&M Page
- Setting a Shared Link
- Deleting a Shared Link
- Executing a SQL Diagnosis
- Obtaining Diagnosis Results
- Creating an Instance Diagnosis Task
- Querying Instance Diagnosis Reports
- Obtaining an Instance Diagnosis Report
- Synchronizing the Instance List
- Deprecated APIs
- Permissions Policies and Supported Actions
- Appendixes
-
FAQs
-
Product Consulting
- How Is DAS Billed?
- Which Data Sources Does DAS Support?
- Does DAS Support Multi-Region Access?
- Where Is SQL Execution Records Saved If I Enable This Function?
- What Should I Enter in the Database Column to Log In to a PostgreSQL DB Instance on the DAS Console?
- Will I Be Changed If I Enable Collect Metadata Periodically and Show Executed SQL Statements on the Add Login Page?
-
Managing connections
- What Should I Do If I Can't Connect to My DB Instance Due to Insufficient Permissions?
- What Should I Do If I Can't Connect to My RDS for MySQL Instance?
- What Should I Do If I Can't Connect to My ECS (MySQL) Instance?
- What Should I Do If I Can't Connect to My RDS for SQL Server Instance?
- What Should I Do If I Can't Connect to My ECS (Microsoft SQL Server) Instance?
- What Should I Do If I Can't Connect to My RDS for PostgreSQL Instance?
- What Should I Do If I Can't Connect to My ECS (PostgreSQL) Instance?
- What Should I Do If I Can't Connect to My DDS Instance?
- What Should I Do If I Can't Connect to My GaussDB(for MySQL) Instance?
- What Should I Do If I Can't Connect to My GaussDB Instance?
- What Should I Do If I Can't Connect to My DDM Instance?
- How Do I View and Modify ECS Security Group Rules?
- How Do I View and Modify Firewall Rules?
- What Should I Do If My Connection Fails?
-
Usage
- What Can I Do If Garbled Characters Are Displayed in the Exported Database Result Set?
- What Are the Precautions for Connecting DAS to a Third-Party Client?
- What Are the Username and Password for DAS?
- What Should I Do If Table Obtaining Times Out?
- How Do I Modify the Collation?
- When a user creates a data tracking task, an error message indicating that the current user does not have the OBS operator permissions is displayed.
- Resource Freezing, Release, Deletion, and Unsubscription
-
Product Consulting
- Glossary
- Videos
-
More Documents
-
User Guide (ME-Abu Dhabi Region)
- Service Overview
- Getting Started
-
User Guide
- Permissions Management
- Logging In to the DAS Console
- Adding Login Information
- Modifying Login Information
- Deleting Login Information
- Logging In to Databases Shared by Others
- MySQL DB Instance Management (Development Tool)
- Microsoft SQL Server DB Instance Management (Development Tool)
- PostgreSQL DB Instance Management (Development Tool)
- DDS DB Instance Management (Development Tool)
- Enterprise Change Approval
- Intelligent O&M
- FAQs
- Change History
-
User Guide (Kuala Lumpur Region)
- Service Overview
- Getting Started
-
User Guide
- Permissions Management
- Logging in to a DB Instance
-
MySQL
- Account Management
- Database Management
- SQL Operations
- Table Management
- View Management
- Stored Procedure Management
- Event Management
- Trigger Management
- Function Management
- Data Import and Export
- Data Generator (Not Promoted)
- Tracking and Rolling Back Data (Not Promoted)
- Task Management
- Table Structure Comparison and Synchronization (Not Promoted)
- Intelligent O&M (New Version)
- Intelligent O&M
- RDS for SQL Server
- PostgreSQL
- DDS
- DDM
- Audit
-
FAQs
-
Managing connections
- What Should I Do If I Can't Connect to My RDS for MySQL Instance?
- What Should I Do If I Can't Connect to My ECS (MySQL) Instance?
- What Should I Do If I Can't Connect to My RDS for PostgreSQL Instance?
- What Should I Do If I Can't Connect to My ECS (PostgreSQL) Instance?
- What Should I Do If I Can't Connect to My DDS Instance?
- What Can I Do If a GaussDB(for MySQL) Instance Fails to Be Connected?
- What Should I Do If I Can't Connect to My GaussDB Instance?
- What Should I Do If I Can't Connect to My DDM Instance?
- How Do I View and Modify ECS Security Group Rules?
- How Do I View and Modify Firewall Rules?
- What Should I Do If My Connection Fails?
- Usage
-
Managing connections
- Change History
-
User Guide (ME-Abu Dhabi Region)
- General Reference
Show all
Copied.
Error Codes
If an error occurs in API calling, no result is returned. Identify the error cause based on the error codes of each API. If an error occurs, an HTTP status code is returned. The response body contains the specific error code and information.
Status Code |
Error Code |
Error Message |
Description |
Solution |
---|---|---|---|---|
400 |
DAS.200002 |
Frequent requests. |
Too frequent requests. |
Try again later. |
400 |
DAS.200100 |
The parameter is invalid. |
Invalid parameters. |
Check whether the parameters are correctly specified. |
400 |
DAS.200101 |
The start_at parameter is invalid. |
Parameter start_at is invalid. |
Check whether parameter start_at is correctly specified. |
400 |
DAS.200102 |
The end_at parameter is invalid. |
Parameter end_at is invalid. |
Check whether parameter end_at is correctly specified. |
400 |
DAS.200103 |
The offset parameter is invalid. |
Parameter offset is invalid. |
Check whether parameter offset is correctly specified. |
400 |
DAS.200104 |
The limit parameter is invalid. |
Parameter limit is invalid. |
Check whether parameter limit is correctly specified. |
400 |
DAS.200105 |
The order parameter is invalid. |
Parameter order is invalid. |
Check whether parameter order is correctly specified. |
400 |
DAS.200106 |
The order_by parameter is invalid. |
Parameter order_by is invalid. |
Check whether parameter order_by is correctly specified. |
400 |
DAS.200107 |
The datastore_type is invalid. |
Parameter datastore_type is invalid. |
Check whether parameter datastore_type is correctly specified. |
400 |
DAS.200108 |
The database value is invalid! |
Parameter database is invalid. |
Check whether parameter database is correctly specified. |
400 |
DAS.200109 |
The script value is invalid! |
Parameter script is invalid. |
Check whether parameter script is correctly specified. |
400 |
DAS.200110 |
The lock_status value is invalid! |
Parameter lock_status is invalid. |
Check whether parameter lock_status is correctly specified. |
400 |
DAS.200111 |
The lock_type value is invalid! |
Parameter lock_type is invalid. |
Check whether parameter lock_type is correctly specified. |
400 |
DAS.200112 |
The db_user_id value is invalid! |
Parameter db_user_id is invalid. |
Check whether parameter db_user_id is correctly specified. |
400 |
DAS.200113 |
The project_id parameter is invalid. |
Parameter project_id is invalid. |
Check whether parameter project_id is correctly specified. |
400 |
DAS.200114 |
The instance_id parameter is invalid. |
Parameter instance_id is invalid. |
Check whether parameter instance_id is correctly specified. |
400 |
DAS.200115 |
The parameter of DeleteProcess is invalid! |
Parameters for killing sessions are invalid. |
Check whether the parameters are correctly specified. |
400 |
DAS.200116 |
The type parameter is invalid. |
Parameter type is invalid. |
Check whether the parameters are correctly specified. |
400 |
DAS.200117 |
The status parameter is invalid. |
Parameter status is invalid. |
Check whether the parameters are correctly specified. |
400 |
DAS.200118 |
The retention_days parameter is invalid. |
Parameter retention_days is invalid. |
Check whether the parameters are correctly specified. |
400 |
DAS.200119 |
The object_type parameter is invalid. |
Parameter object_type is invalid. |
Check whether the parameters are correctly specified. |
400 |
DAS.200120 |
This API is only available for paid instances. |
This API is available only for paid instances. |
Subscribe to Intelligent O&M and configure instances as paid. |
400 |
DAS.200121 |
The marker is only valid for three minutes. If the expiration time is exceeded, please re export. |
The marker is valid only within 3 minutes. If the marker is invalid, export it again. |
Export it again. |
400 |
DAS.220002 |
Failed to connect to the database. |
Failed to connect to the database. |
Check whether the instance is running properly and the database username and password are correct. |
400 |
DAS.220003 |
The database user does not exist. |
The database user does not exist. |
Check whether the parameters are correctly specified. |
400 |
DAS.220004 |
The database user already exists. |
The database user already exists. |
Check whether the database user exists. |
400 |
DAS.220029 |
Failed to operate the SQL limit switch. |
Failed to enable or disable the SQL concurrency control switch. |
Rectify the fault based on the information returned in error_msg. |
400 |
DAS.220030 |
Failed to operate the SQL limit rules. |
Failed to enable or disable the SQL concurrency control rules. |
Rectify the fault based on the information returned in error_msg. |
403 |
DAS.200050 |
Invalid token. |
The token is invalid. |
Check whether the token is correct, or obtain the token and try again. |
403 |
DAS.200051 |
Authentication failed. |
Authentication failed. |
Check whether you have the required permission. |
500 |
DAS.200001 |
Internal service error. |
Internal service error. |
Contact the customer service. |
500 |
DAS.200003 |
Internal service invoking error. |
Internal service invoking error. |
Contact the customer service. |
500 |
DAS.220005 |
Failed to kill process. |
Failed to kill sessions. |
Rectify the fault based on the information returned in error_msg. |
500 |
DAS.220006 |
Failed to Query Metadata Locks. |
Failed to query metadata locks. |
Rectify the fault based on the information returned in error_msg. |
500 |
DAS.220007 |
Failed to query InnoDB locks. |
Failed to query InnoDB lock waits. |
Rectify the fault based on the information returned in error_msg. |
500 |
DAS.220008 |
Failed to query process list. |
Failed to query instance sessions. |
Rectify the fault based on the information returned in error_msg. |
500 |
DAS.220009 |
Failed to query SQL execution plan. |
Failed to query the SQL execution plan. |
Rectify the fault based on the information returned in error_msg. |
500 |
DAS.220010 |
Failed to list slow query logs. |
Failed to obtain slow SQL details. |
Rectify the fault based on the information returned in error_msg. |
500 |
DAS.220011 |
Failed to list SQL statements. |
Failed to obtain the full SQL statement. |
Rectify the fault based on the information returned in error_msg. |
500 |
DAS.220012 |
Failed to enable/disable DAS SQL explorer. |
Failed to enable or disable DAS to collect full SQL statements. |
Try again. |
500 |
DAS.220013 |
Failed to enable/disable DAS Slow Query Log. |
Failed to enable or disable DAS to collect slow query logs. |
Try again later. |
500 |
DAS.220014 |
Failed to query the status. |
Failed to query the switch status. |
Rectify the fault based on the information returned in error_msg. |
500 |
DAS.220015 |
Failed to query space analysis data. |
Failed to query space analysis data. |
Rectify the fault based on the information returned in error_msg. |
500 |
DAS.220016 |
Failed to execute the space analysis task. |
Failed to execute the space analysis task. |
Check whether the database account has been recorded for the instance. |
500 |
DAS.220017 |
The switch is not enabled. |
Failed to enable log collection. |
Toggle on the switch. |
500 |
DAS.220065 |
Failed to turn on/off the DAS transaction switch. |
Failed to enable or disable the historical transaction switch. |
Rectify the fault based on the information returned in error_msg. |
500 |
DAS.220066 |
Failed to query the DAS historical transaction switch. |
Failed to query the status of the historical transaction switch. |
Rectify the fault based on the information returned in error_msg. |
500 |
DAS.220067 |
Failed to query the DAS historical transaction list. |
Failed to query the historical transaction list. |
Rectify the fault based on the information returned in error_msg. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot