...
set timing on
set serveroutput on
call transfer.util_cleanout_transfer_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 )
# Clean out these tables too. Particularly OPS.RIS_DATA.
# The timestamps below will surely not be correct. Review when the database dump was conducted. Review the data based on a time range.
delete from ops.ris_data where observed_time <= to_timestamp('2023-08-11 13:00:00.0', 'yyyy-mm-dd hh24:mi:ssxff'); delete from ops.ris_configuration where last_modified <= to_timestamp('2023-08-11 13:00:00.0', 'yyyy-mm-dd hh24:mi:ssxff'); delete from ops.ris_event where event_timestamp <= to_timestamp('2023-08-11 13:00:00.0', 'yyyy-mm-dd hh24:mi:ssxff');
|
The box_lims_expedition_delete()
step is the longest. Monitoring is helpful. Currently takes about 30 minutes--mostly to delete millions of results. Historically saw ranges of 2-8 hours (older hardware, fewer CPUs, slower disks).
...