Versions Compared

Old Version 18

changes.mady.by.user Unknown User (fackler)

Saved on

compared with

New Version Current

changes.mady.by.user Unknown User (fackler)

Saved on

Key

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

...

Restore routinely selected database content from the full backup to the shore production transfer schema. - DBA

Info

Nota bene. The expectation is that the data staged will contain the new expedition, QAQC, and 999 (operational test expedition).

In some cases, data is included from a prior expedition.

  • If new content was added, those additions should be preserved. Run this process as-is with the extra expedition. Shipboard changes to legacy content will overwrite the older content.
  • If no new content was added, that reference material should be expunged (already present in the aggregated shore warehouse). A modification of TRANSFER.BOX_LIMS_EXPEDITION_DELETE() is in development for this particular use-case.

Presently a common edge case with poor automation. Tread lightly. Check your work.

Once staged extract, transfer, and load scripts may be run.

...

The data is first imported into a test database instance in the transfer schema. After the data has been remediated to support moratorium concerns, a snapshot of this data may be exported for re-use. The export will be re-imported into the production database.

Code Block
sql my_dba@instance
dp export_dba@instance
dp export -directory dmpdir -dumpfile ###-transfer.dmpdp -schemas transfer -filesize 15gb

After completing the above export from the selected test instance, complete these commands at the production instance (LIMSHQ).

Code Block
sql my_dba@limshq
call transfer.util_cleanout_transfer_new_tables();
dp import -directory dmpdir -dumpfile ###-transfer.dmpdp -logfileschemas 400-transfer-export.log -schemas transfer -filesize 15gb -nameexpr table="like 'NEW__%'" -includemetadata false -includerows true


chk_tablespace_free.ksh

Review the space available in LABWARE, LABWAREIDX.

...

6. Test

Spot-check and test availability and completeness.availability and completeness.

  • Confirm that moratorium access is functioning by running LORE reports. - TAS, DEV
    • Can the EXP### moratorium account login to https://web.iodp.tamu.edu/LORE?
    • Can the EXP### moratorium account see LIMS data for the expedition--images, etc. Spotcheck.
    • Can the EXP### actually download some of the file content?
  • Confirm that moratorium access

...

  • and account permissions are functioning for GEODESC data products. - TAS, DEV
    • Can the EXP### moratorium account login to https://web.iodp.tamu.edu/DataAccess?
    • Can the EXP### moratorium account see the GEODESC Final Product files via DataAccess?
    • Can EXP### actually download some of those files?

7. Notify interested parties

...

  • EPM
  • DBA - RCI
  • Data Librarian
  • Web Master
  • Programmers
  • IT OPS

...




Shore EOX process applied by the DBA prior to expedition 398.
Re-worked below into process above--polishing and efficiency improvements welcome.
The scripts below are

...

equivalent to steps 2. thru 5.

EOX load and merge - rci_work/exp

...