2.2 Mock Upgrade Activity

This topic provides systematic instructions on Mock Upgrade activity.

Mock Upgrade Activity

The mock upgrade activity provides a safe platform for the actual production environment upgrade. You need to prepare a test area where the mock activity can be carried out.

During mock activity, you need to perform User Acceptance Testing (UAT) for the new functionalities that are added in the higher versions. While performing the actual migration, you need to take the maintenances and parameterizations done in UAT to the production environment.

The target database after the mock upgrade serves as a Gold Copy for you to set up the upgraded production environment.

You can truncate the p-Data tables from the Gold Copy and re-import from the production area. In the time between starting mock run activity and starting the actual production upgrade activity, if any of the static data is changed, then you need to handle such data manually.

Mock upgrade involves the following steps:

1. Upgrade Oracle database to the new version.
2. Identify temp soft changes to and take appropriate action to setup target version with temp soft changes (temp soft changes refer to the customization changes and bug fixed on the source version).
3. Set up target version of Oracle FLEXCUBE Investor Servicing.
4. Perform module specific changes if any.
5. Set up interfaces and adapters.
6. After upgrade, test the target version along with all interfaces and adapters.
7. Get sign off on the production environment upgrade.

• Apply Temp Soft Changes
  This topic gives the instructions to apply Temp Soft changes.
• Set up Target Schema
  This topic gives the instructions to set up Target Schema.