Versions Compared

Key

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

Applies to development and acceptance. Do not use this procedure to insert test CAME accounts, for developers, on production.

When should an eMER account(s) be backed up?

  • CAMIS developer (Avro Arrows and Medevac) as well business support accounts being used on acceptance should be backed up before the refresh.

  • If you have an account on development and wish to recreate it on acceptance (or vice versa). You will have to modify some values in the scripts that are exported, due to sequences that exist on some tables, as explained in this document.

  • other occasions, as needed.

...

Export the records to “sql” script files for the following tables:

These tables contain the main data for a fully functional eMER account. The tables are presented in the order that the insert scripts need to be in, in the final script that is constructed to restore the record.

  • CAMIS.YA096_PERSON

  • CAMIS.YA001_MEDICAL_EXAMINER

  • CAMIS.YA006_PERSON_TELEPHONE

  • CAMIS.UA031_MEDICAL_EXAMINER_OFFICE

  • CAMIS.UA041_MEDICAL_OFFICE_TEL

  • CAMIS.UA045_STAMP

  • CAMIS.AA008_APPLICATION_USER


Also backup the reference table TC019_ADDRESS as you may wish to restore addresses if a refresh is being done from production to acceptance or development. Production may not have all the same addresses.Note: the following table contain reference data for UA031_MEDICAL_EXAMINER_OFFICE:
TC019_ADDRESS

Exporting data to “sql” script files:

...