Excellent question! I'd love to hear more about your setup! We have not set up a highly structured environment yet. We do have a test machine, but it is for testing out upgrades to Data Pump, and not changes to individual processes.
The back end of Data Pump is SQL. If you view the tables, PumpProcesses is probably the key to your question. You could copy one row from the table on DEV to the table on PROD. Then, you would need to copy the folder with the XPRJ files ect. I think this table contains everything local to the process. However, if you have anything system specific, such as distributions, and global scripts it may pose a problem.
Please let me know what you think and if you work somethign out.
If I may pose a question to you: What is different between DEV and PROD? Are all of your exports to development databases / or the local disk drive? Our challenge is that all exports are to the main file server, and we don't have a test version of that file server. Difficult to run a production job on test.
I think you can use Monarch Utilities to accomplish this? The only thing that doesn't get carried over would be any manual scripting you have done (at least that's been my experience). We have had to move our projects/models multiple times, and have had the UNC pathing and directory pathing change on us, all of which is manageable by using the utility. You can copy projects/models en masse, and manage all the paths as well.
Hello Zach, Joey, everyone,
The Utility will copy the projects etc, but in many cases I don't want to touch them. It's the DataPump process which I'd like to move.
I agree that we could label the process as "DEV" on the production server, but what I'm working towards is limiting access to the production server and so stopping colleagues from putting anything into production which is not signed off formally, which is where having two machines is helpful.
I understand that this will now be included in the next version of DataPump.