2. Upgrade and Conversion Approach

2.1 Introduction

This chapter gives an outline of the upgrade and conversion approaches. This also provides a summary of all the activities involved in the entire upgrade process.

2.2 Approach - Data Import to Target Schema

In this approach, you will prepare the staging area only with the target version schema. This is the recommended approach.

The steps involved in this method are as follows:

1. Prepare the staging area with the target version schema.
2. Insert the E-data (factory shipped static data) alone in the target schema using the consolidated insert scripts. You can do this using the Oracle FLEXCUBE Universal Banking Installer. The basic setup step should not be done through the installer.
3. Disable the Not null and check constraints in the target schema. Disable all the triggers except the module specific triggers required to be enabled for the upgrade activity. For the list of triggers to be enabled, See “Module Upgrade” on page 1.
4. Perform data import from the export dump of the production data.
5. Apply the conversion scripts for the columns with the not null and check constraints in the target schema to populate them with proper business data.
6. Enable the constraints in the target schema.

The target schema will now act as the gold copy for the customer to resume the verification/production activities.

2.2.1 Advantages

The advantages of this approach are as follows:

• Only one staging area prepared for the target version schema
• The production p-data (transaction data) is imported without loss of data as constraints are disabled during the import

2.2.2 Disadvantages

The disadvantages of this approach are as follows:

• While enabling the constraints which are disabled earlier during the process, there might be a few columns that violate the constraints. You need to manually handle this.

2.3 Upgrade Process Summary

A summary of the version upgrade process is provided below.

1. Complete the mock upgrade activity. The mock upgrade provides a safe platform for the actual production environment upgrade. Mock upgrade involves the following steps:
   (See “Upgrading Database” on page 3.)

• Identify the source database schema. The source system should be at the stage of TI just marked on migration date.
• Setup the target database as per the installation manuals. Exit the installer immediately after loading the static data.
• Retrofit the customization changes, if any, into the target database. Apply the DB object changes, source file changes and static data changes.
• Take a full dump of the source schema.
• In the target schema, disable all the triggers and selective constraints.
• In the target schema, selectively enable the triggers as per the module wise approach.
• Import the table data alone into the target database from the full dump of source schema.
• In target schema, apply the dynamic conversion scripts. This makes the target database compatible with the front end application deployed. (See “Conversion Script Generation Tool” on page 1.)
• In the target schema, enable all the triggers and constraints.
• In target schema, proceed with LD to CL migration and then LM to ELCM migration. Complete the module wise migration and verification checks (See “Module Upgrade” on page 1.)
• In the target schema, complete the verification activities (See “Verifying Data after Database Upgrade” on page 7.)

2. Complete the cut-over upgrade activity. During this, you will upgrade the production environment database. (See “Cut-over Upgrade Activities” on page 1.)

• During cut-over upgrade, if conversion script needs to be applied on any specific units, generate the required conversion script and apply it on the target schema. (See “Conversion Script Generation Tool” on page 1.)

3. Reconcile the data in the source and target databases using the data reconciliation tool. Run a parallel EOD and reconcile the data again. (See “Data Reconciliation” on page 1.)