The outgoing programmer is responsible for all of the end-of-expedition (EOX) activities.
...
NOTE: While performing the EOX for expedition 384, it was discovered that the path represented by "data_pump_dir" did not exist. You can discover what the data_pump_dir is supposed to be using this query (logged in as your DBA account):
select * from dba_directories;
The results have a lot of stuff that's not useful, but the DATA_PUMP_DIR should be there. Currently it is /backup/LIMSJR/dpdump. Note that "backup" is singular (it used to be plural) and there is apparently some desire to change this, so keep that in mind. If you find that the folder does not exist, the command in this step will fail and you may need to get an MCS or a DBA on shore to help create it.
...
create directory data_pump_dir as '/backup/LIMSJR/dpdumpexport';
grant read, write on directory data_pump_dir to transfer, system;
...
|
...
Need to test DMPDP.
Need to post log results.
11. Notify everyone. Database snapshot process is complete.
...
|
The MCS will copy the files over to oem.ship.iodp.tamu.edu:/media/backup/export--one of several staging areas for the EOX tape run.
Inquire with the MCS. Ensure the (above) database content and the (below) ASMAN content are being taken to media for transport to HQ.
12. Send the transfer content home.
NOTE:
Please transfer only the limjr_transfer file online. The full file can come on tape.
Rakesh
This is now routine. The Database Group expects this to occur. This method makes the data available a week earlier than can be achieved transporting tapes.
...
- Hand the files over to the MCS, requesting that they be transferred to \\NORTH\FTP\FromShip\EOX\ << Preferred.
...