You can set configuration properties to detect locks on source or target objects that would prevent the job from executing successfully. You can configure Data Mover to try to start a blocked job after the interval you specify.
- Execute the list_configuration command to generate configuration.xml.
- Open the configuration.xml file.
-
For the blocked.job.retry.enabled key, specify the desired value:
- true: Enables detection of locks on the source and target objects included in a job.
- false: Default value. Data Mover does not check to see whether there are locks on source or target objects. If there are locks, the job will hang.
-
For the blocked.job.retry.interval key, specify the time interval for Data Mover to wait before rechecking whether objects are still locked:
- In the value tag, entered the desired number of minutes or hours.
- In the unit tag, enter the time unit. Valid entries are: MINUTES, HOURS.
-
For the blocked.job.retry.maxInterval key, specify the maximum amount of time to wait when checking object locks before exiting indicating an error message and marking the job as failed.
- In the value tag, entered the desired number of minutes or hours.
- In the unit tag, enter the time unit. Valid entries are: MINUTES, HOURS.
- For the blocked.job.maxAllowedLimit key, specify the maximum number of jobs that can be marked as blocked and retried.
- Save configuration.xml and execute the save_configuration command to apply the desired blocked job configuration settings.