# Error Code

If an error occurs in an API, no result is returned. You can locate the error cause based on the error codes of each API. When the invocation fails, an HTTP status code is returned. The returned message body contains the specific error code and information.

#### Error Response Body Format

- Parameter description

  Table 1 Parameter description
  Name | Type | Description
  --- | --- | ---
  error_code | String | Specifies the error returned when a task submission exception occurs.
  error_msg | String | Specifies the description of the error returned when a task submission exception occurs.

- Response example

      {
          "error_code": "DBS.200001",
          "error_msg": "Parameter error"
      }

#### Error Code Description

Table 2 Error code description
HTTP Status Code | Error Code | Error Information | Handling Measure
--- | --- | --- | ---
400 | DBS.200001 | Parameter error. | Check whether the transferred parameters or URLs are correct.
404 | DBS.200002 | The DB instance does not exist. | Check whether the DB instance and its ID are correct and whether the DB instance exists.
400 | DBS.200010 | Authentication failed | Check whether the tenant and instance match.
403 | DBS.200011 | Operation cannot be executed in current state of the DB instance. | Check whether the instance status or the ongoing operation on the instance conflicts with the request.
404 | DBS.200013 | The node does not exist | Check whether the node ID or group ID is correct.
403 | DBS.200018 | This DB instance is not available. | Check whether the instance status or the ongoing operation on the instance conflicts with the request.
403 | DBS.200019 | Operation cannot be executed in current state of the DB instance. | Check whether the instance status or the ongoing operation on the instance conflicts with the request.
400 | DBS.200024 | The region is unavailable. | Check whether the region name is correct and whether the region is available.
400 | DBS.200022 | The DB instance name already exists. | Check whether the DB instance name exists.
400 | DBS.200025 | Invalid AZ. | Check whether the AZ name is correct and whether the AZ is available.
403 | DBS.200028 | The maximum storage space has been reached. | Check whether the storage space exceeds the upper limit.
404 | DBS.200042 | Invalid DB engine. | Check whether the DB engine is supported by DDS.
400 | DBS.200029 | Invalid username and password. | Check whether the username and password match and whether the password meets the password strength requirements.
400 | DBS.200047 | Operation cannot be executed in current state of the DB instance or node. | Check whether the instance status or the ongoing operation on the instance conflicts with the request.
400 | DBS.200048 | Invalid VPC. | Check whether the VPC ID and name are correct and meet the requirements.
400 | DBS.200049 | Invalid subnet. | Check whether the subnet ID and name are correct and meet the requirements.
400 | DBS.200050 | Invalid security group. | Check whether the security group ID and name are correct and meet the requirements.
400 | DBS.200052 | Invalid password. | Check whether the username and password match and whether the password meets the password strength requirements.
400 | DBS.200053 | The DB instance specifications do not exist. | Check whether the specifications are correct and supported in the current AZ.
400 | DBS.200054 | Invalid DB instance specifications. | Check whether the specifications are correct and supported in the current AZ.
400 | DBS.200057 | Invalid parameter group. | Check whether the parameter group is correct, whether the parameter group exists, and whether the parameter group matches the instance type.
400 | DBS.200075 | Invalid node role. | Check whether the role of the node meets the requirements and whether the instance is normal.
403 | DBS.200076 | Operation cannot be executed in current state of the DB instance. | Check whether the instance status or the ongoing operation on the instance conflicts with the request.
400 | DBS.200095 | Parameter error. | Check whether the parameters in the request and URLs are correct.
400 | DBS.200302 | The storage space must be a multiple of 10. | Check whether the storage space is a multiple of 10.
400 | DBS.200303 | The maximum number of times that the storage space can be scaled up has been reached. | The maximum number of times that the storage space can be scaled up has been reached. To continue to scale up the storage space, contact technical support.
400 | DBS.200304 | The storage space can be scaled up a maximum of four times. | Check whether the instance has been scaled up for multiple times.
400 | DBS.200306 | Invalid storage space. | Check whether the storage space is correct and meets the requirements.
400 | DBS.200311 | Scaling up the storage space is not allowed in current state of the node. | Check whether the node type, instance type, and node ID are correct.
400 | DBS.200434 | Failed to restart the DB instance. | Check whether the DB instance status is normal and whether other operations are being performed on the DB instance.
400 | DBS.200470 | Invalid AZ. | Check whether the AZ is correct.
400 | DBS.200501 | The subnet does not exist. | Check whether the subnet ID and name exist and match the VPC.
400 | DBS.200502 | The security group does not exist. | Check whether the security group ID and name exist and match the VPC.
400 | DBS.200503 | The VPC does not exist. | Check whether the tenant has the VPC.
400 | DBS.200506 | The encryption key does not exist. | Check whether the disk encryption key ID exists.
400 | DBS.200507 | The encryption key is not available. | Check whether the disk encryption key is available.
403 | DBS.201000 | Operation cannot be executed in current state of the DB instance. | Check whether the instance status or the ongoing operation on the instance conflicts with the request.
400 | DBS.201006 | Parameter error. | Check whether the transferred parameters or URLs are correct.
403 | DBS.201014 | Operation cannot be executed in current state of the DB instance. | Check whether the instance status or the ongoing operation on the instance conflicts with the request.
403 | DBS.201015 | This operation cannot be performed because another operation is being performed. | Check whether the instance status or the ongoing operation on the instance conflicts with the request.
400 | DBS.201020 | Invalid DB engine. | Check whether the DB engine is supported by DDS.
403 | DBS.201028 | The DB instance does not exist. | Check whether the DB instance belongs to the tenant and whether the DB instance exists.
400 | DBS.201201 | The backup already exists. | Check whether the backup name or ID already exists.
400 | DBS.201202 | Operation cannot be executed in current state of the DB instance. | Check whether the instance status or the ongoing operation on the instance conflicts with the request.
400 | DBS.201204 | The backup file does not exist. | Check whether the backup file exists and matches the instance.
400 | DBS.201214 | The backup file does not exist. | Check whether the backup exists and matches the instance.
400 | DBS.201319 | Deleting backup file is not allowed because a restoration task is currently in progress. Please wait. | Check whether the backup is being used to restore instances.
400 | DBS.201501 | The DB instance does not exist. | Check whether the tenant has the DB instance, whether the DB instance name or ID is correct, and whether the DB instance exists.
400 | DBS.201502 | The DB instance does not exist. | Check whether the tenant has the DB instance, whether the DB instance name or ID is correct, and whether the DB instance exists.
404 | DBS.212001 | The security group does not exist or has been deleted. | Check whether the parameter group exists.
400 | DBS.212003 | This operation is not permitted. | Check whether the instance status or the ongoing operation on the instance conflicts with the request.
400 | DBS.212006 | The node associated with this parameter group is not available. | Check whether the node that is associated with the parameter group is normal.
400 | DBS.212008 | The database type is not supported. | Check whether the database type is supported
400 | DBS.212013 | This parameter group does not exist. | Check whether the parameter exists.
400 | DBS.212017 | Invalid parameter. | Check whether the transferred parameters or URLs are correct and meet the requirements.
400 | DBS.212019 | Invalid parameter. | Check whether the transferred parameters or URLs are correct and meet the requirements.
400 | DBS.212028 | Invalid parameter group description. | Check whether the parameter group description is valid.
400 | DBS.212030 | The parameter group name already exists. | Check whether the parameter group name is correct and whether the tenant has created the parameter group.
400 | DBS.212031 | Invalid parameter group name. | Check whether the parameter group name meets the requirements:
400 | DBS.212032 | The operation cannot be performed because this parameter group is applied to one or more DB instance nodes. | Check whether the parameter group has been applied to the instance.
400 | DBS.280001 | Parameter error. | Check whether the transferred parameters or URLs are correct and meet the requirements.
500 | DBS.280005 | Server error. Try again later. | Contact technical support engineers.
400 | DBS.280015 | Permission denied. | Check whether the token expires and whether the instance matches the tenant.
400 | DBS.280016 | Resource not found. | Check whether the transferred parameters are correct and whether the instance exists.
403 | DBS.280019 | Account suspended. | Check the account balance.
403 | DBS.280032 | Permission denied. | Check whether the rights of the user group to which the current user belongs allow the corresponding operation.
403 | DBS.280042 | Invalid request. | Check whether the request is allowed by the current instance status and the operations being performed on the instance and whether the request is valid.
401 | DBS.280056 | Invalid token. | Check whether the instance belongs to the tenant and whether the token has been obtained again.
403 | DBS.280063 | Permission denied. Contact the account administrator for authorization NOTE: xxx indicates the fine-grained configuration item corresponding to an operation performed on the DDS DB instance. | Check whether the user group to which the current user belongs has the corresponding operation permission.
500 | DBS.280064 | Fine-grained authentication failed. | Contact the customer service.
400 | DBS.200072 | Invalid storage space. | Check whether the storage space exceeds the upper limit.
400 | DBS.280110 | The DB instance does not exist. | Check whether the tenant has the DB instance, whether the DB instance name or ID is correct, and whether the DB instance exists.
400 | DBS.280122 | Invalid DB engine. | Check whether the storage engine matches the instance engine.
400 | DBS.280123 | Invalid node number. | Check whether the number of nodes to be added to the instance meets the requirements.
400 | DBS.280124 | Invalid backup. | Check whether the backup ID is correct and meets the requirements.
400 | DBS.280127 | Invalid backup description. | Check whether the backup description is correct and meets the requirements.
400 | DBS.280200 | The password contains invalid characters. | Check whether the password is correct and meets the requirements.
400 | DBS.280214 | Invalid retention period. | Check whether the backup retention period is correct.
400 | DBS.280215 | Invalid backup period. | Check whether the backup start time, end time, and backup cycle are correct and meet the requirements.
400 | DBS.280216 | Invalid backup start time. | Check whether the backup start time meets the requirements and whether the relationship between the backup start time and end time is correct.
400 | DBS.280234 | Invalid DB instance name. | Check whether the instance name is correct and whether the instance exists.
400 | DBS.280235 | Invalid DB engine. | Check whether the DB engine information is correct.
400 | DBS.280236 | Invalid database version. | Check whether the database version is supported.
400 | DBS.280239 | Invalid specifications. | Check whether the specification code is correct, whether the specification exists in the current AZ, and whether the specification is supported.
400 | DBS.280241 | Invalid storage type. | Check whether the storage type is correct and meets the requirements.
400 | DBS.280242 | The storage space is out of range. | Check whether the disk size is correct.
400 | DBS.280244 | Invalid AZ. | Check whether the parameters of the AZ are correct, whether the AZ exists, and whether the AZ matches the specifications.
400 | DBS.280247 | Invalid VPC. | Check whether the VPC ID is correct and whether the VPC exists.
400 | DBS.280248 | Invalid subnet. | Check whether the subnet ID is correct and whether the subnet exists.
400 | DBS.280249 | Invalid security group. | Check whether the security group ID is correct and whether the security group exists.
400 | DBS.280266 | Invalid storage space. | Check whether the storage space is correct and meets the requirements.
400 | DBS.280267 | Specifications not match. | Check whether the specification information is correct and whether the specification matches the instance.
400 | DBS.280277 | Invalid backup name. | Check whether the backup name is correct and meets the requirements.
400 | DBS.280280 | Invalid DB instance number. | Check whether the number of DB instances is correct and meets the requirements.
400 | DBS.280284 | Invalid IP address. | Check whether the IP address is correct and meets the requirements.
400 | DBS.280292 | Invalid username. | Check whether the username is correct and meets the requirements.
400 | DBS.280311 | Invalid storage space. | Check whether the storage space is correct and meets the requirements.
400 | DBS.280314 | Invalid storage type. | Check whether the storage type is correct and whether the instance supports the disk type.
400 | DBS.280327 | Invalid node type. | Check whether the node type is correct, whether the node type matches the instance, and whether the node type matches the group ID and node ID.
400 | DBS.280342 | Invalid DB instance mode. | Check whether the instance mode is correct and whether the instance mode matches the instance ID.
400 | DBS.280365 | Invalid payment mode. | Check whether the payment mode is correct and meets the requirements.
400 | DBS.280404 | Invalid DB instance ID. | Check whether the instance ID is correct and meets the requirements.
403 | DBS.280406 | The DB instance cannot be deleted. | Check whether the DB engine and billing mode support direct deletion of instances.
400 | DBS.280408 | Unauthorized tenant ID | Check whether the tenant ID is correct and meets the requirements.
400 | DBS.280414 | Invalid group type. | Check whether the group type is correct, whether the group type matches the instance, and whether the node type matches the group ID.
400 | DBS.280434 | Invalid resource specifications code. | Check whether the resource specifications code exists and meets the requirements.
400 | DBS.280446 | The database information does not exist. | Check whether the datastore field exists.
400 | DBS.280438 | Invalid encryption key ID. | Check whether the disk encryption key ID in the request is created and available, and whether the current DB engine supports disk encryption.
400 | DBS.280439 | Invalid query limit. | Check whether the value of the limit parameter is valid.
400 | DBS.280440 | Invalid offset. | Check whether the value of the offset parameter is valid.
400 | DBS.280441 | Invalid key. | Check whether the tag key is valid.
429 | DBS.280443 | The maximum number of connections has been reached. | APIs are frequently called by the same tenant. Reduce the frequency of API calls.
400 | DBS.280445 | The DB instance class is not available. | The current DB instance class is unavailable. Select another one.
400 | DBS.290000 | Parameter error. | Check whether the transferred parameters or URLs are correct and meet the requirements.

Parent topic: Appendix