Executing a Snapshot Import Job

Truncates all the setup and data artifacts and then import them.

During the snapshot data import process, the system first truncates all the setup and data artifacts and then imports them. Additionally, database sequences are reset based on the imported data so that no conflicts occur after the data is restored.

To execute a snapshot import:

1. Upload the snapshot export ZIP to the inbox in Data Integration.

   To upload the snapshot export ZIP to the inbox in Data Integration, use the EPM Automate uploadFile command.

   You can also use the File Browser in Data Integration to upload a file to the Data Integration inbox.

2. Click Application, then Jobs, and then Schedule Jobs.
3. From the Schedule Jobs page, then What type of job is this?, select Integration Maintenance Script.
4. To schedule an integration maintenance script to run now, see Scheduling Hourly Jobs.

   To schedule an integration maintenance script to run later, see Scheduling a Data Rule or Integration Definition to Run Later in the Job Scheduler.

5. From the Integration Maintenance Script page, click to the right of the Execute Snapshot Export task to schedule.
6. On the Execute Snapshot Import page, from Snapshot File Name, specify the path and file name of the ZIP to be executed.

   For example, you might type: inbox/DMSnapshot_082021.zip.

7. Click OK.

   Only one Execute Snapshot Import job can be executed at a time.

   The message: Custom script executed initiated with Process ID: 0.

   You can access the job log from the Process Details page.

   Note:

   The Process ID for the snapshot import is always " 0" only when the file is exported in ALL, INCREMENTAL or ALL_INCREMENTAL modes because each of these three exports contain data artifacts and process details are part of data tables.

   The Process ID is not "0" when only setup data is exported. This is because setup data doesn’t contain data tables (Process details). In this case, the next available sequence in the Process ID is used.