Applies to development and acceptance. Do not use this procedure to insert test CAME accounts, for developers, on production.
When should an eMER account 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.
Identifying the accounts to backup:
This script returns the developer accounts, for Team Avro Arrows and Team Medevac, as well as the business that are currently active on the target environment.
| Code Block |
|---|
select * from YA096_PERSON
where upper(LAST_NAME_NM) in ('ASGILL', 'AMIN', 'COLLINS', 'DERTINGER', 'KHAN', 'MAGHUR', 'NGUYEN', 'WANG', 'SHIRZAD', 'LE', 'BEDARD', 'DAVID-OMBIGA', 'KENNEDY', 'PEREIRA', 'ROY', 'SAMANT', 'ZOBARICH', 'BAPTISTE', 'DAWI' )
and upper(FIRST_NAME_NM) in ('ALAIN', 'HIREN', 'CHRIS', 'NOREEN', 'SAM', 'SUFYAN', 'PHUONG', 'HAOYUAN', 'SIAMAK', 'MICHELLE', 'ALEXANDRE', 'BOJE', 'RYAN', 'FABIO', 'VERONIQUE', 'MOHIT', 'RICHARD', 'DANIEL', 'SAMIA')
and DATE_DELETED_DTE is NULL
--and upper(EMAIL_TXT) like ('%TC.GC.CA')
order by LAST_NAME_NM asc; |
Export the records to “sql” script files for the following tables:
These tables contain the 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.
...
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.
Exporting data to “sql” script files:
Take note of the PERSON_ID of the account in YA096_PERSON from the script run earlier in this document.
Retrieve the account to be backed up;
For example:
...
The expected result is a sql file containing an insert statement similar to the one below, with the actual data content corresponding to the record being exported:
Code Block Insert into CAMIS_DATA_ADMIN.YA096_PERSON (PERSON_ID, LAST_NAME_NM, FIRST_NAME_NM, EMAIL_TXT, LANGUAGE_CORRESPONDENCE_CD, LANGUAGE_SERVICE_CD, EXTERNAL_PERSON_IND, DATE_CREATED_DTE, DATE_LAST_UPDATE_DTE, USER_LAST_UPDATE_ID) Values (762818, 'DERTINGER', 'Noreen', 'noreen.dertinger@tc.gc.ca', 'B', 'B', 1, TO_DATE('2023/06/05 7:58:11 AM', 'YYYY/MM/DD HH:MI:SS AM'), TO_DATE('2023/07/06 2:48:16 PM', 'YYYY/MM/DD HH:MI:SS AM'), 733962);Repeat these steps to generate SQL files for the remaining seven tables
Combine the exported SQL scripts into a single file in the exact order the table names were listed in this document to avoid constraint errors.
Updating the script for compliance with the sequences
Before running the script with the combined insert statements, the following values have to be checked for compliance with the sequences. If that is not done constraint errors will occur.
...