This topic describes the error codes and error messages that you may encounter when you configure online migration jobs or data addresses. This topic also provides the corresponding solutions.
Error code | Description | Solution |
InvalidArgument | The request contains one or more invalid parameters. | Enter valid parameter values to create a migration job. |
MissingArgument | A required request parameter is not specified. | Check and modify the parameter values you entered, and try again. |
InvalidImportJobStatus | The job status that you specified is invalid. | For information about the status of a migration job, see Subsequent operations. |
ImportAddressNumExceed | The number of data addresses has reached the upper limit. By default, up to 50 data addresses can be created in each region. | Delete the data addresses that are no longer in use. Then, try again to create a data address. |
ImportJobNumExceed | The number of migration jobs has reached the upper limit. By default, up to 50 migration jobs can be created in each region. | Delete the migration jobs that are finished. Then, try again to create a migration job. |
ImportJobDepthExceed | The number of job retries has reached the upper limit. A retry is to start a subtask. Therefore, the default maximum number of retries in a region equals 50 minus the number of existing migration jobs in the region. | The number of retries has reached the upper limit. We recommend that you troubleshoot the issue by referring to Common causes of a migration failure and solutions, and then try again to create a new migration job. If the issue persists, submit a ticket. |
NoSuchImportJob | The specified job does not exist. | Enter the name of an existing job. |
NoSuchImportJobRunTimeId | The job of the specified runtime ID does not exist. | Enter the runtime ID of an existing job. |
NoSuchImportJobParent | The specified retry job does not exist. | Enter the name of an existing retry job. |
NoSuchImportAddress | The specified data address does not exist. | Enter the name of an existing data address. |
ImportJobConflictOnUpdateStatus | A conflict occurred when the job status is being updated. | Make sure that the job status is consistent with the status transition diagram and try again. |
ImportJobAlreadyExist | The job name already exists. | Modify the job name and try again. |
ImportAddressAlreadyExist | The data address name already exists. | Modify the data address name and try again. |
ImportAddressIsOccupied | The data address is being used. | The data address is being referenced by a migration job. Delete the migration job and then delete the data address. |
ImportJobRepeatedOnSameAddress | The source data address and destination data address of the job are the same. | Make sure that the source data address and destination data address are different when you create a migration job. |
ImportJobHasDescendants | The migration job that you managed already has a retry record. | Delete the retry record and try again. |
ImportJobUpdateConcurrently | The job status is being updated and cannot be concurrently updated. | Wait until the status of the current job is updated and try again. |
InternalError | An internal error has occurred. | Submit a ticket and provide the detailed error message. |