Upgrading the Initiate database

After creating the initial runtime environment, you must upgrade the existing database. Before beginning, it is helpful to understand the upgrade process.

After reviewing this topic, use the database upgrade worksheet to define the values needed for the upgrade. You then use the madconfig utility to perform the upgrade.

Incremental upgrade steps. The incremental upgrade, or skip-level upgrade, processes the upgrade incrementally by version. The madconfig upgrade_instance_datasource and madconfig upgrade_datasource targets are used to perform this process. During the upgrade, a confirmation prompt is used to process through each applicable stage of the upgrade steps:

• From 9.0 to 9.2
• From 9.2 to 9.5
• From 9.5 to 9.7
• From 9.7 to 10.0
• From 10.0 to 10.1
• From 10.1 to 11.0
• From 11.0 to 11.3

Related to the upgrade steps, it is suggested that you confirm system version information and verify the database upgrade.

• Before running the madconfig utility, confirm that your system version information is set correctly to represent the version that the operational server runtime environment is running. Version information is found in the mpi_syskey table. The keyval column for the row when keyname equals “ALIGNDEX_VERSION” must accurately reflect the major.minor version of the product.
• After each upgrade step (for example, from 9.0 to 9.2, from 9.2 to 9.5, and so on), verify that the database is upgraded to the applicable version. Conduct this verification before allowing the madconfig utility to continue with the next upgrade step.

Checks in upgrade process. The upgrade script runs checks for these items:

• Custom libraries. If custom libraries are found, the script exits the process. You can bypass this check by deleting the custom library from the mpi_libhead table. One caution is that if the custom functionality has not been integrated into the mainline operational server in a subsequent release, the upgrade appears to run smoothly. However, the operational server might not function as expected, or it might fail to run. If the implementation requires the use of a custom library and that functionality is not part of the mainline product, perform the database upgrade manually.
• EID script. The script detects obsolete enterprise IDs. If the upgrade script finds obsolete EIDs, you are prompted to choose whether to discontinue the upgrade.

Upgrade limitations. Before you begin a skip-level upgrade by using madconfig upgrade_instance_datasource and madconfig upgrade_datasource, become familiar with these limitations:

• Accuracy of the upgraded data is not verified.
• Weights are not regenerated automatically.
• Data is not re-derived automatically.
• Backup and recoveries are not performed automatically.

Before starting the upgrade, complete the database upgrade worksheet.