IBM DataPower Operations Dashboard v1.0.10.0
A newer version of this product documentation is available.
You are viewing an older version. View latest at IBM DPOD Documentation.
Sync Tasks Status Codes
- Assaf Cohen (Deactivated)
Owned by Assaf Cohen (Deactivated)
| Status Code | Description |
|---|---|
| WAITING_FOR_PRE_VALIDATION | Task entered the execution queue, but has not yet been validated or checked, and eventually may not get executed |
| SKIPPED_APIC_DOMAIN | Task will not execute - cannot sync API Connect domain |
| SKIPPED_SOURCE_DEVICE_DOES_NOT_EXIST | Task will not execute - the source device specified in the activity does not exist |
| SKIPPED_SOURCE_DEVICE_NOT_AVAILABLE | Task will not execute - the source device was not available |
| SKIPPED_TARGET_DEVICE_DOES_NOT_EXIST | Task will not execute - the target device specified in the activity does not exist |
| SKIPPED_TARGET_DEVICE_NOT_AVAILABLE | Task will not execute - the target device was not available |
| SKIPPED_NO_DEVICES_MATCHING_PATTERN | Task will not execute - no devices matching the pattern specified in the activity were found |
| SKIPPED_NO_DOMAINS_FOUND_IN_SOURCE_DEVICE | Task will not execute - no domains matching the pattern specified in the activity were found |
| SKIPPED_DOMAIN_DOESNT_EXIST_IN_TARGET_DEVICE | Task will not execute - the specified domain exists in the source device but not in the target device DPOD does not create domains on the target devices, it is your responsibility to create them |
| SKIPPED_DOMAIN_WAS_NOT_CHANGED | Task will not execute - for scheduled plans, no changes were found in the source domain since the last time it was synced to the target domain |
| VALIDATION_STARTED VALIDATIONS_OK | Interim status -Â DPOD is validating the task |
| ERROR_DEVICE_FIRMWARE_NOT_SUPPORTED | Task will not execute - sync is supported only when the source and target devices' firmware level is higher or equal to 7.1.0.0 |
| ERROR_DEVICE_TYPE_INCOMPATIBLE | Task will not execute - sync is possible only from lower to higher device type XG-45 < XI-52 < XB-62 < IDG You can turn this check off in the sync activity definition |
| ERROR_FIRMWARE_LEVELS_INCOMPATIBLE | Task will not execute - sync is possible only from lower major firmware level to an equal or higher firmware level (e.g. 7.2.0.X to 7.2.0.X and higher) |
| ERROR_TARGET_MISSING_FEATURES | Task will not execute - the target device is missing features/licenses found in the source device (e.g. B2B, SQL-ODBC, Tibco-ESM) You can turn this check off in the sync activity definition |
| ERROR_UNSUPPORTED_DEVICE_TYPE | Task will not execute - only the following device types are supported: IDG, XB-62, XI-52, XG-45 |
| ERROR_DEPLOYMENT_POLICY_WAS_NOT_FOUND_IN_SOURCE_DOMAIN | Task will not execute - the deployment policy specified in the sync activity definition was not found in the source domain |
| ERROR_DEPLOYMENT_POLICY_WAS_NOT_FOUND_IN_TARGET_DOMAIN | Task will not execute - the deployment policy specified in the sync activity definition was not found in the target domain |
| ERROR_DEPLOYMENT_POLICY_VARIABLES_WAS_NOT_FOUND_IN_TARGET_DOMAIN | Task will not execute - the deployment policy variables object specified in the sync activity definition was not found in the target domain |
| ERROR_NEEDS_USER_APPROVAL_TO_CREATE_TEST_OBJECTS | Task will not execute - for firmware levels above 7.5.2.4, DPOD will try to check if the passphrase is identical in source and target devices, in order to perform this check, DPOD will need to create a temporary password map object in the source domain, you will need to approve this object creation in the sync activity definition |
| ERROR_SOURCE_AND_TARGET_PASSPHRASE_ARE_DIFFERENT | Task will not execute - the source and target passphrases are different |
| PLAN_FAILED_PRE_SCRIPT | Task will not execute - the pre-plan script returned with a return code greater than 0 |
| SKIPPED_BECAUSE_ERROR_POLICY EXECUTION_CANCELED_BECAUSE_ERROR_POLICY | Task will not execute - Another task failed and specified Error Policy = Fail (See Maintenance Concepts to learn more about Error Policies) |
| READY_FOR_EXECUTION | Interim status - the task passed all validation, it is queued and will be executed in the next minute, or is waiting for other tasks to finish executing first. |
| WAITING_FOR_EXPORT_TASK | Interim status - the import task to the target domain is waiting for the export task from the source domain to finish executing |
| ALL_DEPENDENT_IMPORT_TASKS_SKIPPED | The export task was skipped - no import tasks are waiting for the export (for example, because the target devices were not available) |
| EXECUTION_CANCELED_BECAUSE_MAINTENANCE_WINDOW | Task was not executed - the current time is not within the maintenance window (see Maintenance Concepts for more information about the maintenance window), the maintenance window is checked for all execution types: schedules, ad-hoc via the UI and via the REST API |
| SENT_TO_MDB EXECUTION_STARTED EXECUTION_PRE_CHECKS_STARTED | Interim status - the task is executing |
| EXECUTION_PRE_CHECKS_DOMAIN_IS_ALREADY_QUIESCED | Task failed - quiesce domain requested but the domain was already quiesced |
| EXECUTION_PRE_CHECKS_DEVICE_NOT_AVAILABLE | Task failed - the DataPower device was not available |
| EXECUTION_WAITING_FOR_PRE_SCRIPT | Waiting for the user pre-script to execute |
| EXECUTION_PRE_SCRIPT_ERROR | Task failed - the user pre task script return code was larger than 0, the post task script will still be executed (if specified) |
| EXECUTION_EXPORT_DOMAIN_STARTED | Interim status - exporting data from the source domain |
| EXECUTION_EXPORT_DOMAIN_SOMA_ERROR | Task failed - the export domain process returned an error |
| EXECUTION_EXPORT_DOMAIN_RETURNED_EMPTY_FILE | Task failed - the export domain process returned an empty export file |
| EXECUTION_QUIESCE_STARTED | Quiesce domain/device started |
| EXECUTION_QUIESCE_WAITING_FOR_QUIESCE | Waiting for the device or domain to quiesce |
| EXECUTION_QUIESCE_TIMEOUT_OCCURRED | A timeout occurred while waiting for the device or domain to quiesce, the timeout can be configured -  see Configurable Parameters and Settings (DPOD will add 3 minutes to the specified timeout) |
| EXECUTION_IMPORT_DOMAIN_DRY_RUN_STARTED | Interim status - importing into the target domain started, this is a dry-run import and WILL NOT change any data in the target domain. |
| EXECUTION_IMPORT_DOMAIN_DRY_RUN_UNSUCCESSFUL | Task failed - the import dry run returned an error |
| EXECUTION_IMPORT_DELETE_TARGET_OBJECTS_STARTED | Interim status - DPOD started to delete objects from the target domain |
| EXECUTION_IMPORT_DELETE_TARGET_OBJECTS_SOMA_ERROR | Task failed - the delete objects process returned an error |
| EXECUTION_IMPORT_DELETE_TARGET_OBJECTS_UNSUCCESSFUL | Task failed - could not delete one or more objects from the target domain |
| EXECUTION_IMPORT_DOMAIN_STARTED | Interim status - importing configuration to the target domain started |
| EXECUTION_IMPORT_DOMAIN_SOMA_ERROR EXECUTION_IMPORT_DOMAIN_EXCEPTION | Task failed - the import process returned an error NOTE: the target domain's objects were deleted, DPOD does not restore the domain to its previous state This error may indicate that the target device is under heavy load and cannot handle the import process, if no transactions are running on the device, this may happen when multiple sync tasks are running in parallel. |
EXECUTION_IMPORT_DOMAIN_SAVE_CONFIG_UNSUCCESSFUL EXECUTION_IMPORT_DOMAIN_SAVE_CONFIG_EXCEPTION | Task failed - the domain may or may not have been synced, DPOD could not issue Save Configuration on the target device.Check the target domain status manually and save the configuration manually. |
| EXECUTION_UNQUIESCE_STARTED EXECUTION_UNQUIESCE_ON_ERROR_STARTED | Unquiesce domain/device started |
| EXECUTION_UNQUIESCE_WAITING_FOR_UNQUIESCE EXECUTION_UNQUIESCE_ON_ERROR_WAITING_FOR_UNQUIESCE | Waiting for domain/device to unquiesce |
| EXECUTION_UNQUIESCE_TIMEOUT_OCCURRED EXECUTION_UNQUIESCE_ON_ERROR_TIMEOUT_OCCURRED | A timeout occurred while waiting for the device or domain to unquiesce, the timeout can be configured -  see Configurable Parameters and Settings (DPOD will add 3 minutes to the specified timeout) |
| EXECUTION_WAITING_FOR_POST_SCRIPT | Waiting for the user post script to execute |
| EXECUTION_POST_SCRIPT_ERROR | Task failed - the user post script return code was great than 0 |
| SKIPPED_EXPORT_TASK_FAILED | (For Import tasks) Task skipped - the export source domain task failed, cannot perform the import task |
| EXECUTION_CANCELED_BECAUSE_A_DAY_PASSED | Task was not executed - it was automatically cancelled because more than 24 hours passed since it started to wait for execution |
| EXECUTION_FAILED_WITH_INTERNAL_EXCEPTION | Internal error occurred, see error message for details |
| EXECUTION_FAILED_LONG_RUNNING | The task was running for more than 60 minutes (see Configurable Parameters and Settings on how to change this duration) and was marked as finished, the task may still be executing, manual intervention may be required |
| SUCCESS | The export or import finished successfully |