Help Center/ Cloud Data Migration/ User Guide/ Managing Jobs/ Scheduling Job Execution
Updated on 2022-09-22 GMT+08:00
View PDF

Scheduling Job Execution

CDM supports scheduled execution of table/file migration jobs by minute, hour, day, week, and month. This section describes how to configure scheduled job parameters.

  • When configuring scheduled jobs, do not set the same scheduled time for different jobs. Instead, set different times to avoid exceptions.

  • If you use DataArts Studio DataArts Factory to schedule the CDM migration job and configure this parameter, both configurations take effect. To ensure unified service logic and avoid scheduling conflicts, enable job scheduling in DataArts Factory and do not configure a scheduled task for the job in DataArts Migration.

Scheduling Job Execution by Minute

CDM allows jobs to be executed every several minutes. It is recommended that the cycle be at least 5 minutes.
  • Start Time: indicates the time when the scheduled configuration takes effect, or the first time when the job is automatically executed.
  • Cycle (minutes): indicates the interval when a job is executed starting from the start time.
  • End Time: This parameter is optional. If it is not set, the scheduled job keeps being automatically executed. If it is set, the scheduled job will be automatically stopped at the end time.
Figure 1 Scheduling job execution by minute

Figure 1 shows that the job will be automatically executed at 15:30:30 on November 29, 2018 for the first time at a cycle of 30 minutes, and will be automatically stopped at 15:29:00 on November 30, 2018.

Scheduling Job Execution by Hour

CDM allows jobs to be executed every several hours.
  • Cycle (hours): indicates the interval when a job is automatically executed.
  • Trigger Time (minute): indicates the exact time in each hour when a scheduled task is triggered. The value ranges from 0 to 59. You can set a maximum of 60 values and use commas (,) to separate these values. However, the values must be unique.

    If the trigger time is not within the validity period, the system selects a trigger time closest to the validity period for the scheduled job to be automatically executed at the first time. The following gives an example:

    • Start Time: 1:20:00
    • Cycle (hours): 3
    • Trigger Time (minute): 10
  • Validity Period: includes Start Time and End Time.
    • Start Time: indicates the time when the scheduled configuration takes effect.
    • End Time: This parameter is optional, which indicates the time when the scheduled job is automatically stopped. If this parameter is not set, the scheduled job keeps being automatically executed.
Figure 2 Scheduling job execution by hour

Figure 2 shows that the scheduled configuration will take effect at 15:30:00 on November 30, 2018. The job is automatically executed for the first time upon the scheduled configuration takes effect, at 15:50:00 for the second time, and at 17:10:00 for the third time. The job is triggered for three times every 2 hours and the configuration is always valid.

Scheduling Job Execution by Day

CDM allows jobs to be executed every several days.
  • Cycle (days): indicates the interval when a job is executed starting from the start time.
  • Validity Period: includes Start Time and End Time.
    • Start Time: indicates the time when the scheduled configuration takes effect, or the first time when the job is automatically executed.
    • End Time: This parameter is optional, which indicates the time when the scheduled job is automatically stopped. If this parameter is not set, the scheduled job keeps being automatically executed.
Figure 3 Scheduling job execution by day

Figure 3 shows that the scheduled job will be automatically executed at 00:20:00 on December 1, 2018, and is executed once every three days. The configuration is always valid.

Scheduling Job Execution by Week

CDM allows jobs to be executed every several weeks.
  • Cycle (weeks): indicates the interval when a scheduled job is executed starting from the start time.
  • Trigger Time (day): You can specify the day of each week when the job is automatically executed. One or more days can be selected at a time.
  • Validity Period: includes Start Time and End Time.
    • Start Time: indicates the time when the scheduled configuration takes effect.
    • End Time: This parameter is optional, which indicates the time when the scheduled job is automatically stopped. If this parameter is not set, the scheduled job keeps being automatically executed.
Figure 4 Scheduling job execution by week

Figure 4 shows that the job will be automatically executed at 00:20:00 every Tuesday, Saturday, and Sunday every two weeks starting from 00:20:00 on December 1, 2018, and the job will be automatically stopped at 00:00:00 on June 1, 2019.

Scheduling Job Execution by Month

CDM allows jobs to be executed every several months.
  • Cycle (months): indicates the interval when a scheduled job is executed starting from the start time.
  • Trigger Time (day): indicates the day of each month when the job is executed. The value ranges from 1 to 31. You can set multiple values and use commas (,) to separate these values. However, the values must be unique.
  • Validity Period: includes Start Time and End Time.
    • Start Time: indicates the time when the scheduled configuration takes effect. The automatic execution time is accurate to hour, minute, and second.
    • End Time: This parameter is optional, which indicates the time when the scheduled job is automatically stopped. If this parameter is not set, the scheduled job keeps being automatically executed.
Figure 5 Scheduling job execution by month

Figure 5 shows that the job will be automatically executed at 00:00:00 on every fifth and twenty-fifth day of each month starting from 00:00:00 on December 1, 2018. The configuration is always valid.

Parent topic: Managing Jobs