cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
787
Views
0
Helpful
3
Replies

Transporter Throws Issue ...Job does not exist in the destination database

When our admin attempts to migrate/move the job to Prod tier from QA using transporter it throws an error.

Job \QA\Apps Office Auto A\Statewide Emergency Event Resource Tracking\STICC in action Call SEERT STICC Job does not exist in the destination database.

The action job "Call SEERT STICC Job" exist in QA. The job "STICC" that the job action calls also exists. There was no problem moving the job from Test to QA using the same transporter tool. However, to move the job to QA to Prod it throws there error.

I attached the screen shot of the error, job action, and the job on the file "transporterissue.doc". please advise.

tidal master 5.3.1.373


thank you,
warren

3 Replies 3

Derrick Au
Level 4
Level 4

Hi Warren,

In short the correct sequence for migration from QA to PROD is

1) STICC job, then

2) Job Action, Call SEERT STICC Job

and not the other way around.

BR,

Derrick Au

thanks derrick. right the STICC job was migrated first. then the job action was right after the STICC job. this was when the transporter throws an error.

Hi Warren,

That's odd. Can you please confirm if STICC and its children jobs migrated successfully? If succeeded, then the action should be able to migrate over. The transporter should also have some logs that might offer more clues as to what might have triggered that error message. Also, the Master and Transporter version that you are on is a bit outdated, you may be required to patch.

BR,

Derrick Au

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: