Domain name for API request: cynosdb.intl.tencentcloudapi.com.
This API is used to restore access to isolated instances.
A maximum of 20 requests can be initiated per second for this API.
The following request parameter list only provides API request parameters and some common parameters. For the complete common parameter list, see Common Request Parameters.
| Parameter Name | Required | Type | Description |
|---|---|---|---|
| Action | Yes | String | Common Params. The value used for this API: ActivateInstance. |
| Version | Yes | String | Common Params. The value used for this API: 2019-01-07. |
| Region | Yes | String | Common Params. For more information, please see the list of regions supported by the product. This API only supports: ap-bangkok, ap-beijing, ap-chengdu, ap-chongqing, ap-guangzhou, ap-hongkong, ap-jakarta, ap-nanjing, ap-seoul, ap-shanghai, ap-shenzhen-fsi, ap-singapore, ap-tokyo, eu-frankfurt, na-ashburn, na-siliconvalley, sa-saopaulo. |
| ClusterId | Yes | String | Cluster ID |
| InstanceIdList.N | Yes | Array of String | Instance ID list. A single instance ID is in the format of cynosdbmysql-ins-n7ocdslw, identical to the instance ID displayed on the TDSQL-C MySQL database console. You can obtain it through the query instance list API. Its value is the InstanceId field in the output parameter. |
| Parameter Name | Type | Description |
|---|---|---|
| FlowId | Integer | Task flow id |
| RequestId | String | The unique request ID, generated by the server, will be returned for every request (if the request fails to reach the server for other reasons, the request will not obtain a RequestId). RequestId is required for locating a problem. |
Restore instance access
https://cynosdb.intl.tencentcloudapi.com/?Action=ActivateInstance
&ClusterId=cynosdbmysql-bzxxrmtq
&InstanceIdList.0=cynosdbmysql-ins-7upukfpw
&<Common request parameters>{
"Response": {
"RequestId": "fd5759b5-89e9-483c-b79c-d99b27c33192",
"FlowId": 147842
}
}TencentCloud API 3.0 integrates SDKs that support various programming languages to make it easier for you to call APIs.
The following only lists the error codes related to the API business logic. For other error codes, see Common Error Codes.
| Error Code | Description |
|---|---|
| FailedOperation.DatabaseAccessError | Database access failed. Try again later. If the issue persists, contact customer service. |
| FailedOperation.FlowCreateError | Failed to create the process. Please retry later. If the issue continues, contact customer service. |
| FailedOperation.OperationFailedError | Operation failed. Try again later. If the issue persists, contact customer service. |
| InternalError.DbOperationFailed | Query database failed. |
| InvalidParameterValue.InstanceNotFound | The instance does not exist. |
| InvalidParameterValue.PrePayPayModeError | Operation not allowed for prepaid payment type. |
| OperationDenied.ClusterOpNotAllowedError | Operation forbidden. The current cluster does not allow this operation. |
| ResourceNotFound.ClusterNotFoundError | The cluster does not exist. |
| ResourceNotFound.ResourceError | The resource corresponding to the parameter does not exist. |
| ResourceUnavailable.InstanceLockFail | Failed to lock the instance. It is temporarily inoperable. |
| ResourceUnavailable.InstanceStatusAbnormal | Instance status is abnormal and temporarily not operable. |
| UnauthorizedOperation.PermissionDenied | CAM authentication failed. |
Apakah halaman ini membantu?
Anda juga dapat Menghubungi Penjualan atau Mengirimkan Tiket untuk meminta bantuan.
masukan