...
- Create accounts for new participants - participants_add.sql
- Delete the accounts for those who are leaving or have left the ship.
- Adapt the script in Subversion to our current needs - participants_remove.sql.
7. Review Oracle accounts for expiring users
Review Oracle for accounts that are locked or pending expiration.
| Code Block |
|---|
select username, lock_date, expiry_date, password_change_date from dba_users where expiry_date <= sysdate + interval '3' month; |
Send notifications to those whose accounts expire soon. Assist those whose accounts are locked.
8. Clean the database
Remove previous expedition content. Maybe remove 999 (play core content). Ask Technical Staff and ALOs first.
...
Prior expedition content is to be removed to enforce moratorium. Use this detailed reference to go through the process.
...
9. Check that database triggers are enabled
This step is dependent on the completion of (7). Via SQLDeveloper, log into the LIMS account. Ensure that no triggers, functions, procedures, views are flagged by a red 'X' (indicates invalid or disabled content).
...
If invalid triggers exist, track down why. Look for the Oracle-specific errors via SQL Developer. Give another DBA a holler.
...
10. Programs to Run
Start the Virtual Photo Generator
...
If not already present, help set it up on the dedicated IRIS-Collector physical host. This should be the ONLY location that runs it.
...
11. Core Catcher Types
Chat with the Core Technicians--are there any changes to the list of Core Catcher Types LIST_ENTRY where LIST='CC_TYPE'?
The goal is to keep the list short. Most often used items should be pushed to the top by use of the ORDER_NUMBER field.
Keep core entry simple. Drill-floor safety and core recovery take precedent over this small thing.
...
12. Check with the DESC tech to see if DESC value list entries need to be made available to the SEM uploader.
This step involves updating the DESCINFO2.X_SIEM_HERARCHY table. If this is needed:
- In SQL Developer, look at the table, sorted by HIER_KEY. At the bottom, you might find one or more expedition-specific entries (they'll have an expedition number in their names). Delete these.
- This documentation describes the process of adding new values for your expedition: SEM uploader X_SEM_HIERARCHY table.
- If the above documentation is confusing, here are some notes:
- The data in this table represents a hierarchy, and the PARENT value for each record links back to the HIER_KEY of that item's parent.
- For example, "igneous rock names", "sediment names" and "metamorphic rock names" (HIER_KEY = 80, 90, 100) all link back to "LITHOLOGY" (HIER_KEY = 10). On expedition 396, we added three entries, with each one linking back to one of the three lithology items just mentioned, so their PARENT values were 80, 90, 100.
- If you've done this properly, you should be able to run the SEM uploader and (after selecting an image, which can be anything), see the name(s) you added when you pick the parents (e.g. Category = LITHOLOGY → General subcategory = igneous rock names → Exp. specific subcategory = [your entry or entries]).
...
13. Replace GEODCAT with
...
the latest definitions from shore
TBD - RTLIMS.GEODCAT, or Blum source spreadsheet?
This needs to become routine (as does catalog merging and updates of taxonomies.
You tested on shore.
...
Test again. Do templates load? Can new samples be added to DataCapture working sets?
Proactively ensure readiness for use of GEODESC data transported.
14. Honor moratorium.
Assist other technical staff with expedition preparation.
...
15. Expedition readiness
Assist other technical staff with expedition readiness concerns.
...