Data Mover jobs may fail to complete successfully if they are blocked because there are locks on source or target database objects. In addition, SQL execution may fail if a transaction is aborted due to a deadlock (Error 2631). You can configure the daemon to detect these situations and attempt to start the job or deadlocked transaction after time intervals you specify.
- In the Daemons column, click the name of the daemon you want to configure.
- In the Daemon Setup column, click Job Retry.
- [Optional] To enable blocked job detection, click the Enable blocked jobs check box under Blocked Jobs.
- Next to Attempt to start a blocked job every, designate the time interval for Data Mover to wait before checking if locks are still present.
- Enter the Maximum number of blocked jobs that can be checked for periodic restart attempts.If a job is detected as blocked when this number is reached, the job is added to the job queue.
- [Optional] To enable deadlock error detection, click the Enable deadlocked transactions check box under Deadlocked Transactions.
- Specify the time to wait before retrying a SQL execution that failed with a 2631 deadlock error in the Time between retry attempts fields.
- Enter the Maximum number of retry attempts that can be checked for periodic restart attempts.If a job is detected as blocked when this number is reached, the job is added to the job queue.
- Click Apply.