Executing a Snapshot Import Job

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

During the Execute Snapshot 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.

Before running this script, upload the snapshot export ZIP to the inbox in Data Integration using the EPM Automate uploadFile command. You can also use the File Browser in Data Integration to upload a file to the Data Integration inbox.

To schedule the script to run now, see Scheduling a Job to Run Now.

To schedule the script to run later, see Scheduling a Job to Run Later.

When scheduling the Execute Snapshot Import script, from the Snapshot File Name, specify the path and file name of the ZIP to be executed. For example, you might type: inbox/DMSnapshot_082021.zip.

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

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.