Run a mapping task after you configure all of the required settings.
You can run a mapping task in the following ways:
• Manually. To run a mapping task manually, on the Explore page, navigate to the task. In the row that contains the task, click Actions and select Run.
You can also run a mapping task manually, with or without advanced options, from the Task Details page. To access the Task Details page, click Actions and select View.
•On a schedule. To run a mapping task on a schedule, edit the task in the mapping task wizard to associate the task with a schedule.
When a mapping task that processes change data from a CDC source is stopped, you can click Restart on the job details page to restart the task from the beginning or to resume from where it left off.
Reprocessing incrementally-loaded source files
Reprocess source files to create a snapshot of the data from a specified time interval, to debug and discover the source of bad data in your target, or to restore deleted data. In the advanced options, you can configure the properties to reprocess incrementally-loaded source files.
A job that reprocesses incrementally-loaded files reads the files that were modified during the time that you specify. You can choose to reprocess files that were modified in a given time interval or all files modified after a given start time. Reprocessing applies only to Source transformations that you configure to incrementally-load files. The following image shows the reprocessing settings in Advanced Options:
You can reprocess source files when at least one source is configured to incrementally load files and the files have been loaded at least once. The advanced options are not available if the mapping does not have sources configured to incrementally load files, the mapping task has never run, or the mapping task is configured to perform a full load of all files.
Reprocessing doesn't change the time that the mapping task uses in future jobs to identify modified files for incrementally-loaded sources. For example, you have a mapping task that incrementally loads files and is scheduled to run every Monday at 8 a.m. After you run a job with advanced options on a Thursday, the next scheduled job still checks for files modified after Monday at 8 a.m. If you want to change the time that the mapping task uses to identify modified files, override the incremental file load type in the mapping task configuration.
Note: Processing is unpredictable when the start or end time of a reprocessing job is within the repeated hour on the day that Daylight Saving Time ends.
Reprocessing incrementally-loaded source files example
You have a source directory that receives a new data file every six hours. In Data Integration, you have a mapping that incrementally loads these files to a target and a mapping task that is scheduled to run the mapping at 3:00 a.m. every day.
The following image shows the contents of the source and target directories over two days:
Mid-day on February 4, you realize that incorrect data was loaded the previous day, February 3, so your target contains incorrect data for the files created on February 2. After fixing the files in the source directory, you run a job with advanced options to reprocess the incorrect files.
In the advanced options, you choose to read incrementally-loaded source files that were modified between 02/02/2022 00:00:01 and 02/03/2022 00:00:00. You click Run to run the mapping task with the advanced options. The reprocessing job processes the files modified within the selected time interval and writes them to the target.
When the next scheduled job runs at 3 a.m. on February 5, it incrementally loads the files created on February 4, as usual.
