CreateProcCorrectOrder - Data Management - Alibaba Cloud Documentation Center

Creates a programmable object ticket.

Operation description

You can call this API operation only for database instances that are managed in Security Collaboration mode.

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:
- For mandatory resource types, indicate with a prefix of * .
- 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
dms:CreateProcCorrectOrder	create	All Resources ``	none	none

Request parameters

Parameter	Type	Required	Description	Example
Comment	string	Yes	The remarks of the ticket.	test
RelatedUserList	array	No	The operators that are related to the ticket.
	long	No	The ID of the operator that is related to the ticket.	1342**
Param	object	Yes	The parameters of the ticket.
Classify	string	No	The reason for the programmable object change.	test
DbItemList	array<object>	Yes	The information about the database.
	object	No	The information about the database.
DbId	long	Yes	The database ID. Databases are divided into physical databases and logical databases. To query the ID of a physical database, call the ListDatabases or SearchDatabase operation. To query the ID of a logical database, call the ListLogicDatabases or SearchDatabase operation.	19721978
Logic	boolean	Yes	Specifies whether the database is a logical database. Valid values: true: The database is a logical database. false: The database is a physical database.	false
RollbackSQL	string	No	The SQL statements for rolling back the data change. Note This parameter is required if you set the RollbackSqlType parameter to TEXT.	empty
RollbackAttachmentName	string	No	The key of the attachment that contains the SQL statements used to roll back the data change. You can call the GetUserUploadFileJob operation to obtain the attachment key from the value of AttachmentKey. Note This parameter is required if you set RollbackSqlType to ATTACHMENT.	test_rollback.sql
RollbackSqlType	string	No	The format of the SQL statements used to roll back the data change. Valid values: TEXT ATTACHMENT	TEXT
ExecSQL	string	Yes	The SQL statements for data change.	DELIMITER /// CREATE PROCEDURE GetAllProducts() BEGIN SELECT * FROM base_user; END ///
ExecMode	string	No	The mode in which the data change ticket is executed after the ticket is approved. Valid values: COMMITOR: The ticket is executed by the user who submits the ticket. AUTO: The ticket is automatically executed after the ticket is approved. LAST_AUDITOR: The ticket is executed by the last approver of the ticket.	COMMITOR
AttachmentKey	string	No	The key of the attachment for the ticket. The attachment provides more instructions for this operation. You can call the GetUserUploadFileJob operation to query the key of the attachment.	order_attachment.txt
Tid	long	No	The ID of the tenant. Note To view the ID of the tenant, go to the Data Management (DMS) console and move the pointer over the profile picture in the upper-right corner. For more information, see the View information about the current tenant section of the "Manage DMS tenants" topic.	4***

Response parameters

Parameter	Type	Description	Example
	object	Schema of Response
RequestId	string	The request ID.	427688B8-ADFB-4C4E-9D45-EF5C1FD6E23D
Success	boolean	Indicates whether the request was successful. Valid values: true: The request was successful. false: The request failed.	true
ErrorMessage	string	The error message that is returned if the request failed.	UnknownError
ErrorCode	string	The error code that is returned if the request failed.	UnknownError
CreateOrderResult	array	The ticket IDs.
OrderIds	long	The ticket ID.	12*****

Examples

Sample success responses

JSONformat

{
  "RequestId": "427688B8-ADFB-4C4E-9D45-EF5C1FD6E23D",
  "Success": true,
  "ErrorMessage": "UnknownError",
  "ErrorCode": "UnknownError",
  "CreateOrderResult": [
    0
  ]
}

Error codes

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

Change history

Change time	Summary of changes	Operation
2023-12-06	The internal configuration of the API is changed, but the call is not affected	View Change Details