Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The intent of these processes is to establish required database configurations for a new expedition. Only a small portion of this content is needed for any one expedition. Additional scenarios and combinations of data handling are described and considered.

Process  ----> DO THIS ON

...

THE DEV BOX via a shared account like SHIP\DAQ

  • Because it may take a long time and you don't want to tie up your laptop.
  • Because your opposite may need to check in on progress if it runs longer than your shift.

...

Log into operating system oracle user first; then conduct database user logins.

  • Open a PuTTY SQL Developer session. 
  • Connect to oracle@k1.ship.iodp.tamu.edu.
  • From the prompt k1run the commands shown.
  • Supply the appropriate credentials.

...

sql>
spool box_processing-349.log
 
set timing on
set serveroutput on
 
call transfer.copy_cleanout_new_tables(); -- (1)
call transfer.box_asman_catalog_delete('EXP346'); -- (2) Last expedition
call transfer.box_lime_audit_delete(###);    -- (4)
call transfer.box_lims_expedition_delete('346');  -- (3) Last expedition
call transfer.box_lims_cleanup();
call transfer.box_lims_defrag(); -- (5)
spool off
exit

...

Logging the effort quantifies the experience for future improvements. Please place the log file in an expedition folder under r:\ad\support\###...\box\

  • The box_lims_expedition_delete() step is the longest. Monitoring is required.
  • If material from another expedition was analyzed on this expedition, it may be necessary to delete that content too, e.g. call box_lims_expedition_delete('344(312)');

...