The upgrade activities that you need to carry out during cut-over are as follows.
On the cut-over date, the following activities required to be done at the production environment level.
In the Gold Copy, truncate the transaction data tables and re-import the same from the latest production data dump. You can use the script files ‘Truncate-pData.sql’ and ‘Export-Source-PData.par’ (See “Annexure” on page 1.) for this.
Ideally the transaction data that has gone into the production data from the time of starting mock run to till time would be the data level change in the source. You need to handled this. However, during the mock run and verification activities the transaction data (p-Data) might have undergone changes. So you must truncate the p-Data tables using the scripts in the Gold Copy.
You need to repeat the database upgrade activity performed during the mock upgrade.
See “Upgrading Database” on page 3.
You need not do any static data comparison at this point. The implementation team takes care not to do any static data changes in the production environment.
Selectively apply the post upgrade check points in the upgraded production area.
See “Verifying Data after Database Upgrade” on page 7.
In order to make the database consistent and up-to-date, you can reapply the scripts discussed in chapter ‘Mock Upgrade Activity’.
See “Verifying Data after Database Upgrade” on page 7.
See “Post Import Activities” on page 6.
The Gold Copy should be used for setup in production environment for all applicable components and various files.