...
| Code Block |
|---|
ssh oracle@k1.ship.iodp.tamu.edu # Connect to an ODA with a terminal session.
cd /backup/export # Export file and log will be placed here.
. oraenv # Confirm which database instance is the default
ORACLE_SID = [LIMSJR1] ? # LIMSJR1 is the expected default. Press <Enter> for no change.
# If anything else shows, contact the DBA.
# The default for K2 is expected to be SHIPTEST.
sql me # Supply your DBA account in place of "me". |
NOTE: For command-line tools--like sql, sqlplus, rman: if your password has spaces or symbol characters, you must quote the password, e.g.
...
# ! Quote your password if it contains spaces or symbol characters. # Example. Password:"@ s3cr3t fr45e" |
Run data cleaning and preening scripts
Connect to Oracle as TRANSFER (schema owner) or your DBA account. Doing this work in SQL Developer is often convenient.
...
- 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.
- You must look up and specify ###. The script as written deletes all
auditkeys_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.
...