CreateFreeLockCorrectOrder - Data Management - Alibaba Cloud Documentation Center

Creates a lock-free change ticket.

Operation description

For more information about the lock-free change feature, see Overview .

This operation can be used only for instances that are managed in Stable Change or Security Collaboration mode. For more information, see Change data without the need to lock tables and Change schemas without locking tables.

Debugging

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

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
dms:CreateFreeLockCorrectOrder	Read	All Resources *	none	none

Request parameters

Parameter	Type	Required	Description	Example
Comment	string	Yes	The purpose or objective of the data change. This parameter is used to help reduce unnecessary communication.	test
RelatedUserList	array	No	The stakeholders of the data change. All stakeholders can view the ticket details and assist in the approval process. Irrelevant users other than DMS administrators and database administrators (DBAs) are not allowed to view the ticket details.
	long	No		51****
Param	object	Yes	The parameters of the ticket.
Classify	string	No	The reason for the data change.	test
ExecSQL	string	Yes	The SQL statements that you want to execute to change data.	delete from base_user where 1 = 1;
SqlType	string	Yes	The format of the SQL statements used to change data. Valid values: TEXT: text ATTACHMENT: attachment. This value is not supported.	TEXT
AttachmentName	string	No	The key of the attachment that contains the SQL statements used to change data. This parameter is not supported.	test.sql
RollbackSQL	string	No	The SQL statements used to roll back the data change.	empty
RollbackAttachmentName	string	No	The key of the attachment that contains the SQL statements used to roll back the data change.	test_rollback.sql
RollbackSqlType	string	No	The format of the SQL statements used to roll back the data change. Valid values: TEXT: text ATTACHMENT: attachment. This value is not supported.	TEXT
DbItemList	object []	Yes	The databases in which you want to change data.
DbId	long	Yes	The ID of the database. The database can be a physical database or a logical database. To obtain the ID of a physical database, call the ListDatabases or SearchDatabase operation. To obtain the ID of a logical database, call the ListLogicDatabases or SearchDatabase operation.	1860****
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
ExecMode	string	No	The execution mode of the ticket after the ticket is approved. Valid values: COMMITOR: The data change is performed by the user who submits the ticket. AUTO: The data change is automatically performed after the ticket is approved. LAST_AUDITOR: The data change is performed by the last approver of the ticket.	COMMITOR
AttachmentKey	string	No	The key of the attachment that provides more instructions for the ticket. You can call the GetUserUploadFileJob operation to obtain the attachment key from the value of the AttachmentKey parameter.	order_attachment.txt
Tid	long	No	The ID of the tenant. You can call the GetUserActiveTenant or ListUserTenants operation to obtain the tenant ID.	3***

Response parameters

Parameter	Type	Description	Example
	object	Schema of Response
RequestId	string	The ID of the request.	0C1CB646-1DE4-4AD0-B4A4-7D47DD52E931
Success	boolean	Indicates whether the request is successful. Valid values: true: The request is successful. false: The request fails.	true
ErrorMessage	string	The error message returned if the request fails.	UnknownError
ErrorCode	string	The error code returned if the request fails.	UnknownError
CreateOrderResult	array	The ID of the ticket.
	long		134****

Examples

Sample success responses

JSONformat

{
  "RequestId": "0C1CB646-1DE4-4AD0-B4A4-7D47DD52E931",
  "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

No change history