3.4 Verify Data after Database Upgrade

This topic provides a detailed instructions to verify data after database upgrade.

Verify Data after Database Upgrade

Once the database is upgraded, you need to do the following verifications:
  • System wide data verification of reports and other check points
  • Interface testing to check the connectivity
  • Converted deals testing
  • New deals testing
  • New product maintenance testing
  • Signoff

These verifications are explained in detail under the following headings.

System wide Data Verification

This verification includes the following steps.

Generic Checks
Generic check includes the following:
  • Check the main parameter table cstb_param and paramstbl for the parameter values.
  • Menu organization is as per the static factory shipped data and handled from the import.
  • The bank may need to modify their user roles. You need to take care of the change of user roles for the new modules. A script will introduce all such roles into ALLROLES.
EOD and Performance Testing
This verification includes the following:
  • Configure the following as part of FCJ configuration:
    • Install Oracle Web cache which is present in the Sizing document.
    • Change the Internet Explorer setting as per DBA server sizing document (Recommended IE settings).
    • Ensure that onsite changes are not done to introduce no-cache in the code.
    • Configure realistic user roles against the usual ALLROLES.
  • Launch basic screens of high volume module sand process them onsite.
  • Record and review the EOD and EOM timelines before and after upgrade to check if there are any major variances.
  • Check if all the programmes maintained in the EOD window is run without being skipped.
  • Check if all aspects of the EOD, i.e. module functionality and reports generation are covered.
  • Test on a masked dump of the site if it is done offshore.

Interface Testing to Check Connectivity

As part of this verification, you need to perform the following activities:
  • Test incoming and outgoing interfaces
  • Check for all the channels that receive information from Oracle FCIS

Converted Deals Testing

You need to test the converted deals as follows:
  • As part of the upgrade, the system will have new tables as well as new columns in the existing tables. Populate the additional fields and tables by testing the converted/migrated data.
  • Perform basic life cycle testing for the converted contracts.
  • Check the product maintenances and static maintenances for modifications.

New Deals Testing

You need to test the new deals as follows:
  • Create new transactions on existing funds and observe the validation of default values.
  • Test the basic life cycle of new deals.

New Product Maintenance Testing

Once the upgrade is completed, create a new product/fund in each module.

Sign Off

Get the customer sign off to go ahead with the upgrade of production environment.

Gold Copy

Gold Copy - DB Schema Setup

Once the above activities are completed, you can use the DESTSCHEMA as the Gold Copy to set up the database during production environment upgrade.

Gold Copy - Front-End Setup and Interface

Use the latest available executables to set up the various components for production upgrade. All interface related changes available in various files need to be deployed.

Parent topic: Upgrade Database