...
- VARIANCE: If you need to keep some data from the previous expedition for the next expedition, skip this step. Even if you forget, you can still copy what you need from TRANSFER.NEW_tables without having to resort to the data pump import tool.
- VARIANCE: If you need to keep some data from the previous expedition for reference on the next expedition, then custom SQL is required to preserve what you need. And you must communicate with the MCS to ensure what you need is preserved on the ASMAN file system--their routine is to expunge the previous expedition.
VARIANCE: If multiple expeditions need to be cleaned, repeat the command for each expedition.
Run the command again if you see errors like thisCode Block Error report - ORA-20000: ORU-10027: buffer overflow, limit of 1000000 bytes ORA-06512: at "SYS.DBMS_OUTPUT", line 32 ...
An alternative is to Alternatively "set serveroutput off" for this command and simply . Then use SQL like that below to monitor progress of
transfer.box_lims_expedition_delete()from another terminal window or SQL Developer worksheet. ExampleCode Block select x_expedition, count(*) from lims.sample group by x_expedition order by x_expedition;
- Look up and specify ### (
lims.x_lime_audit_main.audit_key). The script as written deletes allaudit_key<= ### fromlims.x_lime_audit_main. The deletion cascades to linkedlims.x_lime_audit_detail. - Defragmentation of the space used by SAMPLE, TEST, RESULT is recommended, but not required if you are pressed for time. Defragmentation on 398 took an hour to run with current ODAs and configs. Older ODAs and configs experienced 9-14 hours.
...