...

Make sure we are getting as complete a copy of the data to be warehoused on shore as we can.

This document does not recapitulate all items on the checklist. If an item is in need of elaboration, please add to it.

0. Negotiate a time window

...

Run from PuTTY, Windows Terminal, Powershell, Hyperterminal.
You can run this step from SQL Developer too, but you'll need the command-line at the ODA for the data pump export command. If the oraenv script does not show LIMSJR1 as the default, contact the DBA (Sunil).

ssh oracle@k1.ship.iodp.tamu.edu

. oraenv
ORACLE_SID = [oracleLIMSJR1] ? LIMSJR<Enter>

sql your-nameyou_dba

sql>
alter tablespace labware read only;
exit

[oracle]$

...

cd /backup/export
ls -l
time expdp your-nameyou_dba directory=dmpdir full=y logfile=limsjr_full-###-export.log dumpfile=limsjr_full-###.dmpdp

Make the database read-write again

sql your-nameyou_dba
Password:

sql>
alter tablespace labware read write;
exit

[oracle]$

Test the export file

Carefully read Read the limsjr_full-###-export.log in k1:/backup/export.

• Are there any errors? No is good. If presenterrors, find cause, maybe re-rrunrun.
• Review the number of samples for LIMS.SAMPLE, LIMS.TEST, LIMS.RESULT, OPS.RIS_DATA.

Log into the SHIPTEST instance. Run these commands to confirm ability to restore content from the file generated.

ssh oracle@k1oracle@k2.ship.iodp.tamu.edu

. oraenv
ORACLE_SID = [oracleSHIPTEST] ? SHIPTEST<Enter>
[oracle]$

time impdp your-nameyou_shiptest_dba directory=dmpdir logfile=exp###-test-export.log dumpfile=limsjr_full-###.dmpdp tables=lims.sample, lims.test remap_schema=lims:transfer content=data_onlyremap_table=lims.sample:xxx_sample,lims.test:xxx_test exclude=trigger table_exists_action=truncatereplace

time impdp your-nameyou_shiptest_dba directory=dmpdir logfile=exp###-test-export.log dumpfile=limsjr_full-###.dmpdp schemas=geodp### remap_schema=geodp###:geodp###_review 

Use SQL Developer to review the content of the SHIPTEST TRANSFER.NEWXXX_SAMPLE table, XXX_TEST tables. Repeat for the restored GEODP###_REVIEW schema. Do not cleanup. Leave it for the oncoming crew to review.

...

Post the export log file on Slack jrso-developer. Note the size of the export file.

We will not zip it, nor send it over the wire. If needed to achieve earlier emplacement of content on shore, the person tagged with conducting the EOX Shore data processing will conduct those activities.

Email it to

• MCS - jr_mcs@ship.iodp.tamu.edu
• IT_OPS - it_ops@iodp.tamu.edu
• Data Librarian - database@iodp.tamu.edu
• programmers - programmers@iodp.tamu.edu
• DBAs - sunil@rajaconsultancy.com, murli@rajaconsultancy.com

Note In the email, note the size of the file and its location--if we're putting it in the right place, there's no need for the MCS to move it.

Speak with the MCS. They will pick up the data from here.

The MCS pick up the full export from  oemjr:/backup/export.

Inquire Enquire with the MCS. Ensure the (above) database content and the (below) ASMAN content are being taken to media for transport to HQ.

Take a copy of the export file

...