Contact & password data in all CAWIS Non-Production regions should be maintained as is outlined below to ensure no real-world clients are contacted during MDM or EDM testing.
These conditions need to be revisited after every DBA migration of data from Production to the DEV/ACC/PreACC/Training regions, or following any inadvertent execution of the CCARCS/CAWIS synchronization routines (which pulls Prod data) into those regions.
see : PBI-125292 Client acceptance region issues
REFRESHING THE DEVELOPMENT AND ACCEPTANCE SCHEMAS
...
Prior to refreshing the development and acceptance schemas back up the table |
|---|
NOTE : The Development and acceptance schemas should be refreshed with Production data every 3 or 4 years to assist with client test scenarios. However, CAWIS has size issues which cause problems when refreshing the test regions. It contains a high volume of data and there is a great deal of daily production data activity. (AD issuance, AAIR and SDR submissions etc…)
The most recent refresh of the CAWIS test schemas (in 2022) took over 2 weeks each.
Refresh attempts tend to fail on timeouts (too much production data changes during the copy) or conflicts with nightly backups otherwise. CAWIS contains a great volume of data and has a great deal of production data activity. (AAIR and SDR submissions etc…) .
see : PBI-158212 , SM-GS TICKET C254719
PBI-158213, SM-GS TICKET C254278
from DBA notes :
This database is huge so its complicated to just do an export of the schema. It always runs out of redo logs or other resources before finishing. Duplicating it is the best option
Initial backup used for cloning had some corrupt blocks
I had copied the Oracle encryption wallet to the 18c wallet folder, but it should have gone to 11g wallet in order to match with the sqlnet.ora wallet destination setting.
Final attempt with encryption wallet files in proper destination and a fresh Full backup.
However, its recommended that the DBA be requested to CLONE Production into the desired target region, rather than duplicate. Though both approaches have failed before.
DB-LINKS
Ensure all DBLinks are pointed to the correctly corresponding schema after the refresh
DEV to DEV,
ACC to ACC etc…
BATCH JOBS
ENSURE that any automated triggers for Batch jobs (CCARCS-CAWIS sync, Project Notifications) are inactive in all regions except Production. If the synchronization routine is run in Non-Production region, it can do a great deal of damage to the test data.
DB-LINKS
Ensure all DBLinks are pointed to the correctly corresponding region after a test region refresh DEV to DEV,
ACC to ACC etc…
REGION-SPECIFIC DATA BACKUPS
Backup the following data into a TXT files file and attach to the PBI before beginning the refresh (or clone)
...
SELECT
'UPDATE TR47_CAWIS_GENERAL_PROPS SET PROPERTY_VALUE = ''' ||
PROPERTY_VALUE || ''' WHERE PROPERTY_NAME = ''' ||
PROPERTY_NAME || ''' ; ' AS UPD1
FROM TR47_CAWIS_GENERAL_PROPS ;
...
AFTER A TEST REGION DATA REFRESH, PERFORM THE FOLLOWING TASKS
PASSWORDS
1)Passwords on all Userids are to be set to “XXXXXX”
...
ALL of the newest AD documents, issued since the LAST data refresh for the target region, need to be copied FROM Production, into the folder for the corresponding target region. This is important for testing the AD subsystem , Project Tracking System (PTS) , Information programs and routing.
Production folder :
https://wwwapps.tc.gc.ca/Saf-Sec-Sur/2/AWD-CN/documents/
CAW Server share \\ncrfs345\ncrws345GROUPS\AARD\AARD Public\CAWIS-REPORTS\AD_ARCHIVE\WORKING
INTERNAL PROD - \\ncrws539\tcappsroot\Saf-Sec-Sur\2\AwD-CN\documents
EXTERNAL PROD - \\ncrws536\wwwappsroot\Saf-Sec-Sur\2\AwD-CN\documents
Acceptance folder :
INTERNAL ACC - \\tcapps2test\tcappsroot\saf-sec-sur\2\AWD-CN\documents
EXTERNAL ACC - \\wwwapps2test\wwwappsroot\Saf-Sec-Sur\2\AWD-CN\documents
Development folder:
INTERNAL DEV - \\ncrws499\catcappsx\Saf-Sec-Sur\2\AWD-CN\documents
EXTERNAL DEV - \\ncrws499\cawwwappsx\saf-sec-sur\2\AWD-CN\documents
...