Each time a job is started, a verification step is performed to capture any changes in the source and target environments between the time the job was first created and the time it is run. This can negatively impact performance for jobs that run frequently.
For jobs with source and target environments that do not change after creation, use the freeze_job_steps parameter to prevent the job steps from being recreated each time the job is run.
If the freeze_job_steps parameter is true and the job target object status changes from non-exists to exists or from empty to non-empty, Data Mover recreates the job steps for only table and view objects. No rebuild is performed when using DSA.
If any changes occur in the source or target environments for the job, run the update_job_steps command to refresh the job steps.
- Open the parameters.xml file containing the job definition information for the job.
- Add the freeze_job_steps parameter in the appropriate place.
- Set the value of freeze_job_steps to true.If unspecified, the default value is false. If freeze_job_steps is true and the source or target environments change after job creation, an error may result when the job is run. In this case, run the update_job_steps command to refresh the job steps.