4 Cutover Upgrade

This topic provides the systematic instructions on cutover upgrade activities.

Cutover Upgrade Activity

The upgrade activities that you need to carry out during cutover are as follows:

• Activities in production environment
• Database upgrade in production environment
• Installation of other components

These activities are explained in detail as follows:

Activities in Production Environment

On the cut-over date, the following activities required to be done at the production environment level:

• Run Pre-EOD and bring the system to pre-EOD completed stage of migration date.
• Ensure that there are no unauthorized transactions in any module.
• Switch off the SWIFT and other interfaces.
• Bring down the application server with due notification.
• Bring down the Gateway server.

Database Upgrade in Production Environment

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 (Refer topic Annexure).

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 handle 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.

Refer to the topics Upgrade Database and Post Import Activities.

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.

Installation of other Components

The Gold Copy should be used for setup in production environment for all applicable components and various files.