Error Codes

Status Code	Error Code	Error Message	Solution
400	DBS.280001	Parameter error.	Refresh the page, modify some parameters, and try again.
400	DBS.300002	Server failure.	Refresh the page and try again later.
400	DBS.300005	Failed to process the request.	-
400	DBS.300100	Failed to create the schema.	Check whether the DDM instance is available, whether the instance is in the Running state, whether the RDS DB instance is being scaled, and whether the schema name is duplicated. If the schema name is duplicated, modify the name and send the request again.
400	DBS.300101	Failed to delete the schema.	Check whether the schema has been deleted and whether the associated RDS DB instance exists or becomes abnormal.
400	DBS.300102	The number of RDS DB instances associated with the schema is invalid.	Check whether the number of RDS DB instances associated with the schema is valid and try again.
400	DBS.300103	The RDS DB instance does not exist or it is not in the same VPC as the schema.	Check whether the RDS DB instance exists and whether the DB instance is in the same VPC as the required DDM instance, and then try again.
400	DBS.300104	The sharding rule of the schema is invalid.	Ensure that the sharding rule is valid and try again.
400	DBS.300106	The number of shards per RDS DB instance is invalid.	Check whether the number of shards per RDS DB instance in the request is correct. If not, modify the number and try again.
400	DBS.300107	The accounts are duplicated.	Check whether the accounts configured in parameters are duplicated and try again.
400	DBS.300108	The RDS DB instances are duplicated.	Check whether there are duplicate RDS DB instances in the request. If yes, modify them and try again.
400	DBS.300109	The schema name is invalid.	Check whether the schema name is valid. If no, modify it and try again.
400	DBS.300110	The status of the RDS DB instance does not allow associating with the schema.	Resolve the RDS DB instance status exception and try again.
400	DBS.300112	This schema name already exists.	Check whether a schema with the same name exists. If yes, modify the name and try again.
400	DBS.300113	Failed to create a physical database.	Check whether the RDS DB instance administrator and password are correct. If no, modify them and try again.
400	DBS.300114	The administrator or password is incorrect.	Check whether the RDS administrator and password are correct. If no, modify them and try again.
400	DBS.300115	Failed to delete the shard.	To delete the schema, check whether there are RDS DB instances associated with it. If the associated RDS DB instances have been deleted, click Synchronize DB Instance Data on the Basic Information page and delete the schema again.
400	DBS.300116	Failed to query available RDS DB instances.	Check whether the RDS service is running properly and try again.
400	DBS.300117	Failed to obtain the associated RDS DB instances.	Check whether the RDS service is running properly and try again.
400	DBS.300118	Failed to scale out the schema.	Check input parameters in the request.
400	DBS.300120	Failed to obtain task information.	Ensure that the DDM instance is running properly and try again.
400	DBS.300121	Failed to clear source data.	Ensure that the scale-out task exists and is in the valid state and that the administrator password of the destination RDS DB instance is correct, and try again.
400	DBS.300122	Failed to roll back the scale-out task.	Ensure that the scale-out task exists and is in the valid state and that the administrator password of the destination RDS DB instance is correct, and try again.
400	DBS.300123	Failed to retry the scale-out task.	Ensure that the scaling out task exists and its status is normal, and try again.
400	DBS.300125	Failed to synchronize RDS information.	Ensure that the RDS service is running properly and try again.
400	DBS.300127	The number of shards in the RDS DB instances associated with the schema is invalid.	Ensure that the total number of shards in the associated RDS DB instances is valid and try again.
400	DBS.300128	Failed to query schema information.	Ensure that the DDM instance is running properly and try again.
400	DBS.300129	Failed to query schema information.	Ensure that the schema exists and try again.
400	DBS.300130	Invalid schema status.	Ensure that the schema is in the Running state and try again.
400	DBS.300131	Failed to update the schema SQL blacklist.	Ensure that the DDM instance is running properly and try again.
400	DBS.300132	Failed to query the schema SQL blacklist.	Ensure that the DDM instance is running properly and try again.
400	DBS.300133	The RDS DB instance is being used to scale out a schema.	Ensure that the RDS DB instance status is not Scaling out or Scaling failed and try again.
400	DBS.300134	The schema status does not allow rolling back or canceling the scale-out task.	Refresh the page and try again later.
400	DBS.300135	Failed to update the relative read weight of the RDS DB instance.	Ensure that the DDM instance is running properly and try again.
400	DBS.300300	Failed to create a DDM account	Ensure that the DDM instance, schema, and account exist and try again.
400	DBS.300301	Failed to update the account.	Ensure that the account and associated schema exist and that the password meets the requirements, and try again.
400	DBS.300302	Failed to delete the account.	Ensure that the DDM instance is running properly and try again.
400	DBS.300305	Invalid DDM account name.	Ensure that the account name is valid and try again.
400	DBS.300306	The account password is invalid.	Ensure that the account name and password in the request body are correct and try again.
400	DBS.300307	The account description is invalid.	Ensure that the maximum length of account description does not exceed 256 characters and try again.
400	DBS.300309	The account basic permissions are invalid.	Ensure that basic permissions configured for the account are correct and try again.
400	DBS.300310	The account extended permissions are invalid.	Ensure that extended permissions configured for the account are correct and try again.
400	DBS.300311	The account already exists.	Ensure that the account name is unique and try again.
400	DBS.300312	Failed to query the account.	Ensure that the DDM instance is running properly and try again.
400	DBS.300313	Failed to configure the SQL blacklist.	Ensure that the schema exists and is in the Running state, and try again.
400	DBS.300314	Failed to modify the read/write policy.	Ensure that the DDM instance is running properly and try again.
400	DBS.300315	Invalid read/write relative weight.	Ensure that the weight is greater than 0 and less than 100.
400	DBS.300316	Failed to query the read/write policy.	Ensure that the DDM instance is running properly and try again.
400	DBS.300322	Failed to save instance metadata.	Provide environment information, instance ID, involved operations, and symptom description and contact technical support.
400	DBS.300323	The associated RDS DB instance is unavailable or this operation cannot be performed when the RDS DB instance is in the current state.	Ensure that the associated RDS DB instance exists and is in normal state, and try again.
400	DBS.300327	The account does not exist.	Ensure that the account exists and try again.
400	DBS.300328	Failed to reset the password.	Ensure that the account exists and try again.
400	DBS.300329	Failed to obtain the step name.	Try again or roll back the scale-out task.
400	DBS.300330	Failed to convert the string from JSON to the required format.	Provide environment information, involved operations, instance ID, and symptom description and contact technical support.
400	DBS.300331	Data migration error.	Provide environment information, involved operations, instance ID, and symptom description and contact technical support.
400	DBS.300332	The scale-out task timed out.	Try again or roll back the scale-out task.
400	DBS.300333	Failed to check the time zone.	Log in to the RDS console. In the instance list, locate the source RDS DB instance and click its name. In the navigation pane, choose Parameters, search for time_zone in the upper right text box to check its value. Then, perform these operations on the target RDS DB instance, and check whether its time_zone value is consistent with the source DB instance. If not, modify it to ensure that the two values are consistent and retry.
400	DBS.300334	sql_mode check failed.	Log in to the RDS console. In the instance list, locate the source RDS DB instance and click its name. In the navigation pane, choose Parameters, search for sql_mode in the upper right text box to check its value. Then, perform these operations on the target RDS DB instance, and check whether its sql_mode value is consistent with the source DB instance. If not, modify it to ensure that the two values are consistent and retry.
400	DBS.300335	Failed to obtain the RDS link.	Check whether the RDS service is running properly.
400	DBS.300336	Physical database not found.	Log in to the associated RDS DB instance and execute SHOW DATABASES. Check whether there is a physical database whose name starts with the schema name, and whether the number of physical databases must be the same as the number of shards in the schema.
400	DBS.300337	Failed to check the primary key.	Check whether there are tables without primary keys. If yes, add primary keys for those tables and retry.
400	DBS.300338	Failed to disable DDL or DML.	Provide environment information, instance ID, involved operations, and symptom description and contact technical support.
400	DBS.300339	Failed to insert a scale-out subtask.	Contact technical support.
400	DBS.300340	Failed to change statuses of scale-out subtasks to Initialization.	Contact technical support.
400	DBS.300341	Failed to issue a scale-out subtask.	Contact technical support.
400	DBS.300342	Failed to obtain scale-out subtasks.	Contact technical support.
400	DBS.300343	The volume of remaining subtask data is invalid.	Provide environment information, involved operations, and symptom description and contact technical support.
400	DBS.300344	Status check for scale-out task failed.	Contact technical support.
400	DBS.300345	Failed to obtain information about the scale-out task.	Try again.
400	DBS.300346	Failed to obtain information about the DDM process.	Try again.
400	DBS.300347	Failed to disable the link.	Try again.
400	DBS.300348	Failed to obtain subtasks during data verification.	Contact technical support.
400	DBS.300349	Failed to update the schema status during route switching.	Contact technical support.
400	DBS.300350	The required data is not found.	Provide environment information, involved operations, and symptom description and contact technical support.
400	DBS.300351	Failed to change statuses of scale-out subtasks to Error.	Contact technical support.
400	DBS.300352	Failed to change statuses of scale-out subtasks to Stop.	Provide environment information, involved operations, and symptom description and contact technical support.
400	DBS.300353	Data verification failed.	Provide environment information, involved operations, and symptom description and contact technical support.
400	DBS.300354	Failed to change statuses of scale-out subtasks to Complete.	Provide environment information, involved operations, and symptom description and contact technical support.
400	DBS.300355	Schema creation failed.	Provide environment information, involved operations, and symptom description and contact technical support.
400	DBS.300356	Failed to connect to the RDS DB instance.	Check whether the RDS service is running properly.
400	DBS.300357	The RDS DB instance administrator or password is incorrect.	If the RDS DB instance administrator is incorrect, log in to the RDS console, locate the required RDS DB instance and click its name, and view the administrator on the instance details page.
400	DBS.300358	There is a schema where source data is not cleared.	Log in to the DDM console, switch to the schema management page, locate the target schema, and click Clear in the Operation column.
400	DBS.300360	The associated instance does not support this operation.	Provide environment information, involved operations, and symptom description and contact technical support.
400	DBS.300362	The scaling method is invalid.	Select either one of rebalance and reshard.
400	DBS.300363	Pre-check failed.	Provide environment information, involved operations, and symptom description and contact technical support.
400	DBS.300364	Failed to check disk space of the DB instance.	Perform the following operations to scale up disk space of the DB instance: Log in to the management console. Hover on the left menu to display Service List and choose Database > Relational Database Service. On the Instance Management page, locate the required DB instance and click its name. On the Basic Information page, locate the Storage Space part. Click Scale and try again after the scaling is complete.
400	DBS.300365	Failed to update metadata.	Retry the scale-out task.
400	DBS.300366	Failed to rename physical tables during migration.	Retry the scale-out task.
400	DBS.300367	Failed to clear source data.	Try again.
400	DBS.300368	Parameter lower_case_table_names of the DB instance is invalid.	Perform the following operations to scale up disk space of the DB instance: Log in to the management console. Hover on the left menu to display Service List and choose Database > Relational Database Service. On the Instance Management page, locate the required DB instance and click its name. Choose Parameters in the left navigation pane, search for lower_case_table_names and verify that its value is 1 and retry.
400	DBS.300369	Failed to configure the access control switch. Contact customer service.	View DBS-ddm-instancemanager logs and DBS-resource-manager logs and modify as follows: If error code APIG.xxxx is returned, indicating that you have no permission to access the API, contact ELB O&M engineers to grant the user the required permission. View the URI of the API in the resource management INFO log. If an error code containing ELB.xxxx is displayed, contact ELB O&M engineers to locate the fault.
400	DBS.300370	Load balancing is not enabled for the current DDM instance. To enable it, contact technical support.	If needed, go to DBS Operation System to enable access control for the required DDM instance.
400	DBS.300371	Creating a test DDM instance is not supported. To enable this function, contact technical support.	Recommend users to create a DDM instance using the engine ID of a stable version. To create a test DDM instance, go to the DBS Operation System platform to add the user to the whitelist. View the DDM instance management logs to obtain the whitelist name.
400	DBS.300372	Invalid destination DDM instance.	Create a DDM instance as the destination instance.
400	DBS.300375	Invalid {param}.	Change the value of {param} and try again.
400	DBS.300376	The time zone is invalid.	Enter a correct time zone.
400	DBS.300377	Invalid time range.	Ensure that the format of the time range for route switching is HH:mm:ss. Ensure that the route switching start time and end time are the same day and the interval is longer than 1 hour. Retry after completing the above operations.
400	DBS.300379	The operation is not allowed for this type of tasks.	Enter the ID of the required schema scale-out task.
400	DBS.300400	The task is not found.	Enter a valid task ID.
400	DBS.300401	Failed to modify the automatic route switching time range.	Provide environment information, involved operations, symptom description, and tenant node logs and contact technical support.
400	DBS.300402	Failed to switch the route manually.	Provide environment information, involved operations, symptom description, and tenant node logs and contact technical support.
400	DBS.300405	The schema name length is invalid.	Ensure that the schema name contains 2 to 24 characters.
400	DBS.300406	The schema name cannot contain keyword keyword.	Ensure that the schema name does not contain information_schema, mysql, performance_schema, and sys.
400	DBS.300407	The schema name cannot contain uppercase letters.	Enter a schema name that only consists of lowercase letters.
400	DBS.300408	Failed to check the RDS connectivity.	Upgrade Agent to 2.6.1 or later. Provide environment information, involved operations, symptom description and contact O&M engineers to check whether the Agent is faulty.