Moving an input file after Project runs

[Grant]

I have recently upgraded from MDP6 to & and the product is amzing. I am wondering what the easiest way to move and rename an import file is after a multi-export project runs on it. there are no post=project input file handling dialogues in this version as there was in 6.

Also can a process/project be triggered to run on the existance of the file in a directory (ie. HR copies a payroll file into a directory and the process executes automatically).

Thanks

[Todd Niemi]

I assume you're using Version 7. You can configure an input file distribution to move and rename the input file. (To do so, when configuring an export, click the Input Distribution button on the XPRJ Editor's Input tab, click the Add button on the Edit Actions dialog, then select the Move option on the Add Action dialog. (Use the Help buttons in the dialogs to help you configure it.)

If you wish to check for the existence of an input file before running a process, on the Advanced tab of the Process Properties dialog, enable process retries and then specify retry interval and number of retries settings. Then, when configuring the project file for the process, on the XPRJ Editor’s Input tab under the File Existence Criteria heading select “All specified files must exist”. Lastly, configure the appropriate process schedule. For example, you might configure a process schedule that operates every 5 minutes beginning at 9 AM on the day the input file is going to be copied into the directory by HR.

Hope this helps.

[Gareth Horton]

Hi

Todd is correct on using the input distribution to move and rename your file.

It may be better to create a schedule that operates once per day, then configure the retries to retry until the next iteration of the schedule, or you will end up with a number of failed processes, as the retries expire every 5 minutes.

In the next point release of Data Pump, there will be a "Retry Indefinitely" setting, so you can get much closer to a trigger type approach.

There is no exact equivalent of the file trigger settings as in MDP6, as this methodology brings many problems with it, especially when getting files over slow connections such as WANs and FTP. What can happen is that the trigger fires, but the file is not fully written.


Gareth