Call GetDataExportOrderDetail to obtain the details of a data export ticket.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer. You can use OpenAPI Explorer to search for API operations, call API operations, and dynamically generate SDK sample code.

Request parameters

Parameter Type Required Example Description
Action String Yes GetDataExportOrderDetail

The operation that you want to perform. Valid values: GetDataExportOrderDetail .

OrderId Long Yes 123456

The ID of the ticket.

Tid Long Yes -1

The ID of the tenant.

Note The tenant ID is taken from the avatar in the upper-right corner of the system. For more information, see Tenant ID and Tenant .

Response parameters

Parameter Type Example Description
DataExportOrderDetail Struct

The detailed information of the data export ticket.

KeyInfo Struct

The status information of the data export ticket.

JobStatus String EXPORT_SUCCESS

The status of the data export ticket. Valid values:

  • PRE_CHECKING: The ticket was being prechecked.
  • PRE_CHECK_SUCCESS: The ticket was successfully prechecked.
  • PRE_CHECK_FAIL: The ticket failed to be prechecked.
  • WAITING_APPLY_AUDIT: The ticket was to be submitted for approval.
  • APPLY_AUDIT_SUCESS: The ticket was successfully submitted for approval.
  • ENABLE_EXPORT: The ticket was approved. Data can be exported.
  • WAITING_EXPORT: Data was to be scheduled for export.
  • DOING_EXPORT: Data was being exported.
  • EXPORT_FAIL: Data failed to be exported.
  • EXPORT_SUCCESS: Data was successfully exported.
PreCheckId Long 123

The ID of the precheck task.

OrderDetail Struct

The detailed information of the ticket.

ActualAffectRows Long 1

The number of affected rows verified by the system.

Classify String text

The category of the reason for the export.

Database String xxx@xxx:3306

Export the database.

DbId Integer 123

The ID of the exported database.

EnvType String test

The environment information of the database to be exported.

ExeSQL String select 1

The export SQL statement.

IgnoreAffectRows Boolean false

Specifies whether to ignore the number of affected rows.

IgnoreAffectRowsReason String empty

Ignore the verification reason.

Logic Boolean false

Specifies whether the database is a logical database.

ErrorCode String UnknownError

The error code.

ErrorMessage String UnknownError

The error message of the failure.

RequestId String 427688B8-ADFB-4C4E-9D45-EF5C1FD6E23D

The ID of the request.

Success Boolean true

Indicates whether the request is successful.

Examples

Sample requests


     http(s)://[Endpoint]/? Action=GetDataExportOrderDetail &OrderId=123456 &Tid=-1 &<common request parameters> 
   

Sample success responses

XML format


     <DataExportOrderDetail> <KeyInfo> <PreCheckId> 15544 </PreCheckId> <JobStatus> export_success </JobStatus> </KeyInfo> <OrderDetail> <Logic> false </Logic> <ActualAffectRows> 1 </ActualAffectRows> <ExeSQL> select 1; </ExeSQL> <Database> yuyang_test @ xxx:3306 [yuyang_test_xxx] Hangzhou non-cellular </Database> <IgnoreAffectRows> false </IgnoreAffectRows> <DbId> 116367 </DbId> <Classify> the test </Classify> <EnvType> product </EnvType> </OrderDetail> </DataExportOrderDetail> <RequestId> 78C93646-D9B1-4E6E-B5FD-C69F94A7905A </RequestId> <Success> true </Success> 
   

JSON Format


     {"DataExportOrderDetail": { "KeyInfo": { "PreCheckId": 15544, "JobStatus": "EXPORT_SUCCESS" }, "OrderDetail": { "Logic": false, "ActualAffectRows": 1, "ExeSQL": "select 1;", "Database": "yuyang_test @ xxx:3306 [yuyang_test_xxx] Hangzhou non-unitization", "IgnoreAffectRows": false, "DbId": 116367, "Classify": "test", "EnvType": "product" } }, "RequestId": "78C93646-D9B1-4 E6 E-B5FD-C69F94A7905A", "Success": true} 
   

Error codes

Go to the Error Center For more information, see error codes.