All Products
Search
Document Center

AnalyticDB:EnableElasticPlan

Last Updated:Aug 30, 2024

Enables a scaling plan for an AnalyticDB for MySQL cluster.

Operation description

For information about the endpoints of AnalyticDB for MySQL, see Endpoints .

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer.

Authorization information

The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:

  • Operation: the value that you can use in the Action element to specify the operation on a resource.
  • Access level: the access level of each operation. The levels are read, write, and list.
  • Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
    • The required resource types are displayed in bold characters.
    • If the permissions cannot be granted at the resource level, All Resources is used in the Resource type column of the operation.
  • Condition Key: the condition key that is defined by the cloud service.
  • Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
OperationAccess levelResource typeCondition keyAssociated operation
adb:EnableElasticPlanupdate
  • All Resources
    *
    none
none

Request parameters

ParameterTypeRequiredDescriptionExample
ElasticPlanNamestringYes

The name of the scaling plan.

Note You can call the DescribeElasticPlans operation to query the names of scaling plans.
test
DBClusterIdstringYes

The cluster ID.

Note You can call the DescribeDBClusters operation to query the IDs of all AnalyticDB for MySQL Data Lakehouse Edition (V3.0) clusters within a region.
amv-wz9509beptiz****

Response parameters

ParameterTypeDescriptionExample
object

The response parameters.

RequestIdstring

The request ID.

A5C433C2-001F-58E3-99F5-3274C14DF8BD

Examples

Sample success responses

JSONformat

{
  "RequestId": "A5C433C2-001F-58E3-99F5-3274C14DF8BD"
}

Error codes

HTTP status codeError codeError messageDescription
400ACS.ElasticPlan.AutoWorkerPlanExistsFailed to enable the elastic plan. The instance already has an active elastic plan.Failed to enable the storage scaling plan because the cluster has another storage scaling plan enabled.
400ACS.ElasticPlan.WorkerPlanExistsFailed to enable the elastic plan. At least one active elastic plan already exists.Failed to enable the storage scaling plan because another storage scaling plan has been enabled.
400ACS.ElasticPlan.InvalidStartTimeIntervalThe start time of this elastic plan is too closed to another one.The effective time of the scaling plan is close to that of another scaling plan.
400ACS.ElasticPlan.InvalidEndTimeThe end time should be later than current time.The end time of scheduled scaling must be later than the current time.
400ACS.ElasticPlan.InvalidTodayPlanFailed to enable this elastic plan. Today's schedule time is missed and you should prepare at least %s minutes for us to prepare resource.-
400ACS.ElasticPlan.InvalidTargetSizeInvalid target size.-
400ACS.ElasticPlan.InvalidStartTimeInvalid start time.-
404InvalidDBCluster.NotFoundThe DBClusterId provided does not exist in our records.The specified DBClusterId parameter does not exist. Make sure that the DBClusterId value is valid.

For a list of error codes, visit the Service error codes.

Change history

Change timeSummary of changesOperation
2023-12-12The Error code has changedView Change Details
2023-06-30The Error code has changedView Change Details
2023-04-13The Error code has changedView Change Details