Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 32 Current »

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

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.

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.

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.

REGION-SPECIFIC DATA BACKUPS

Backup the following data into a TXT file and attach to the PBI before beginning the refresh (or clone)

TR47_CAWIS_GENERAL_PROPS needs to be backed up from the target region, then restored afterward

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”

UPDATE A01_USER A01 SET PASSWORD = 'jV1Vz@<=lz'
WHERE A01.USER_ID NOT IN
(SELECT FROM_TXT FROM Z980_TERM_CONVERSION WHERE TERM_TYPE_CD = ‘SYSID’) ;

/* Generic system Userids are skipped */

2) Owner AAIR Access code/passwords are to be set to “XXXX1111”

UPDATE Y50_PARTY SET ACCESS_CODE = '37328B5E590E26C946B75A91E26B33B2'
WHERE CLIENT_ID > 0 ;

/* only the owners have client_ids on the Y50 table */

CONTACT DATA

4) All FAX numbers are to have their area codes replaced with 000-

SELECT * FROM A92_ADDRESS_PROPERTY
WHERE  SUBSTR(ADDRESS_PROPERTY_TXT,1,3) <> '000' AND ADDRESS_PROPERTY_TYPE_CD = 2 ;
UPDATE A92_ADDRESS_PROPERTY
SET    ADDRESS_PROPERTY_TXT = '000-' || SUBSTR(ADDRESS_PROPERTY_TXT,5,8)
WHERE  SUBSTR(ADDRESS_PROPERTY_TXT,1,3) <> '000' AND ADDRESS_PROPERTY_TYPE_CD = 2 ;

5) All Email addresses are to be suffixed with "X"


SELECT * FROM A92_ADDRESS_PROPERTY
WHERE  ADDRESS_PROPERTY_TXT LIKE '%@%' AND ADDRESS_PROPERTY_TXT NOT LIKE '%X' ;
UPDATE A92_ADDRESS_PROPERTY
SET    ADDRESS_PROPERTY_TXT = UPPER(ADDRESS_PROPERTY_TXT) || 'X'
WHERE  ADDRESS_PROPERTY_TXT LIKE '%@%' AND ADDRESS_PROPERTY_TXT NOT LIKE '%X' ;

/* ensure CAWIS admin’s email remains unmarked */

UPDATE A92_ADDRESS_PROPERTY
SET ADDRESS_PROPERTY_TXT = 'LAUREN.MCMAHON@TC.GC.CA'
WHERE ADDRESS_PROPERTY_TXT = 'LAUREN.MCMAHON@TC.GC.CAX' ;

6) ENSURE THAT CONTINUING AIRWORTHINESS ACCOUNTS REMAIN ACTIVE AND HAVE ADMIN ROLE CODES

The Userid’s for all members of Continuing Airworthiness are found on the Z980 table where Term_type_cd = ‘CAW’

UPDATE A01_USER SET ACTIVE_IND = 'Y'
WHERE ACTIVE_IND = 'N'
AND USER_ID IN (SELECT FROM_TXT FROM Z980_TERM_CONVERSION WHERE TERM_TYPE_CD = 'CAW');
UPDATE A103_USER_ROLES SET CAWIS_ROLE_CD = 'AU'
WHERE CAWIS_ROLE_CD = 'NS'
AND USER_ID IN (SELECT FROM_TXT FROM Z980_TERM_CONVERSION WHERE TERM_TYPE_CD = 'CAW');

7) Check PINS

Review all logins to ensure that the connection strings for that region are still valid.

8. UPDATE THE AIRWORTHINESS DIRECTIVE DOCUMENT FOLDER FOR THE TARGET REGION

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\GROUPS\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

Note : Its normal to find a small amount of records, with legitimate TC-email, or TC-employee personal emails, or TC cell phone numbers in the FAX fields at any given time. This is how data conditions are setup for MDM/EDM testing.

KM - 2022-08-10



  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.