When you attempt to import a job, the import fails with an unexpected error. The Application log in the Event Viewer shows the following error message from adTempus:
This happens under the following scenario:
This fails because the import process matches variables based on their unique, internal identifiers, rather than their names. Because the variables were created independently on separate servers, they have different identifiers even though they have the same name. Therefore adTempus attempts to create a new variable rather than updating the existing variable. This results in a duplicate key error when adTempus attempts to save the variable to the database, because there are now two variables with the same name.
To work around this issue, delete all variables from the job on Server B before performing the import. The variables will be re-created from the import file. Because they will not have the same identifiers as the variables on Server A, the next time you perform an export/import for this job the problem will not occur.
This issue has been resolved. Resolved in version 4.7.