GetQueryOptimizeExecErrorStats - Database Autonomy Service

Queries SQL templates that failed to be executed.

Operation description

If you use Alibaba Cloud SDK or Database Autonomy Service (DAS) SDK to call this operation, we recommend that you use the latest version of the SDK.
If you use an SDK to call API operations of DAS, you must set the region ID to cn-shanghai.
This operation supports the following database engines:
- ApsaraDB RDS for MySQL
- PolarDB for MySQL
- ApsaraDB RDS for PostgreSQL

Debugging

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

Debug

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.

Operation	Access level	Resource type	Condition key	Associated operation
hdm:GetQueryOptimizeExecErrorStats	get	All Resources ``	none	none

Request parameters

Parameter	Type	Required	Description	Example
Engine	string	Yes	The database engine. Valid values: MySQL PolarDBMySQL PostgreSQL	MySQL
InstanceIds	string	No	The instance IDs. Separate multiple IDs with commas (,).	rm-2ze8g2am97624****
Keywords	string	No	The keywords of the SQL template. Separate multiple keywords with spaces.	select update
LogicalOperator	string	No	The logical relationship between multiple keywords. Valid values: or and	or
DbNames	string	No	The name of the database to be queried.	testdb01
Time	string	Yes	The time range to query. Specify the time in the UNIX timestamp format. Unit: milliseconds.	1642953600000
PageSize	string	Yes	The number of entries per page. Default value: 10.	10
PageNo	string	Yes	The page number. Pages start from page 1. Default value: 1.	1
OrderBy	string	No	The field by which to sort the returned entries. Only error_count is supported, which specifies that the entries are sorted based on the number of failed executions.	error_count
Asc	string	No	Specifies whether to sort the returned entries in ascending order. Default value: true. Valid values: true: sorts the returned entries in ascending order. false: does not sort the returned entries in ascending order.	true
Region	string	No	The region in which the instance resides. Valid values: cn-china: Chinese mainland cn-hongkong: China (Hong Kong) ap-southeast-1: Singapore This parameter takes effect only if InstanceIds is left empty. If you leave InstanceIds empty, the system obtains data from the region set by Region. By default, Region is set to cn-china. If you specify InstanceIds, Region does not take effect and the system obtains data from the region in which the first specified instance resides.** Note Set this parameter to cn-china** for the instances that are created in the regions in the Chinese mainland.	cn-china

Response parameters

Parameter	Type	Description	Example
	object
Code	string	The HTTP status code returned.	200
Message	string	The returned message.	Successful
Data	object	The detailed information, including the error codes and the number of entries that are returned.
Total	long	The total number of entries returned.	19
PageNo	integer	The page number.	1
PageSize	integer	The number of entries per page.	10
Extra	string	The reserved parameter.	None
List	array<object>	The information about the SQL templates that failed to execute.
QueryOptimizeExecErrorStats	object
InstanceId	string	The instance ID.	rm-2ze8g2am97624****
InstanceName	string	The alias of the database instance.	test01
Dbname	string	The name of the database.	testdb01
SqlId	string	The SQL template ID.	2e8147b5ca2dfc640dfd5e43d96a****
SqlText	string	The content of the SQL template.	select * from test1
ErrorCode	string	The error code returned if the request failed.	1146
ErrorCount	long	The number of errors.	10
RequestId	string	The request ID.	B6D17591-B48B-4D31-9CD6-9B9796B2****
Success	string	Indicates whether the request was successful. Valid values: true: The request was successful. false: The request failed.	true

Examples

Sample success responses

JSONformat

{
  "Code": "200",
  "Message": "Successful",
  "Data": {
    "Total": 19,
    "PageNo": 1,
    "PageSize": 10,
    "Extra": "None",
    "List": [
      {
        "InstanceId": "rm-2ze8g2am97624****",
        "InstanceName": "test01",
        "Dbname": "testdb01",
        "SqlId": "2e8147b5ca2dfc640dfd5e43d96a****",
        "SqlText": "select * from test1",
        "ErrorCode": "1146",
        "ErrorCount": 10
      }
    ]
  },
  "RequestId": "B6D17591-B48B-4D31-9CD6-9B9796B2****",
  "Success": "true"
}

Error codes

HTTP status code	Error code	Error message
400	InvalidParams	The request parameters are invalid.
403	NoPermission	You are not authorized to do this action.

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

Change history

Change time	Summary of changes	Operation
2023-03-29	The Error code has changed. The request parameters of the API has changed	View Change Details