About Prevalidation

After you start the upgrade process, you have the option to run the prevalidation step. We strongly recommend that you select this option. Prevalidation checks for data inconsistencies that might cause upgrade problems. If you run prevalidation, the upgrade utility creates one or more html reports in the <PPM_Home>/PPM_Upgrade/upgrade_960/logs/reports/html/integrity/validator directory.

We recommend that, at a minimum, you start the upgrade just to run the prevalidation step for upgrades performed in advance of your production system upgrade. Running the prevalidation step can give you a good estimate of how long it takes to run prevalidation scripts against your specific data set, and allow you to plan your upgrade appropriately.

If the time to execute prevalidation scripts against your environment consumes a significant amount of the time allocated for the production upgrade, then consider performing the prevalidation step and resolving any uncovered issues before you upgrade your production instance.

Prevalidation Reports

Prevalidation may generate several reports that list any problems detected, their cause, and any corrective action to take before you start the upgrade process. The warnings and errors in these reports indicate potential problems with data that may cause the upgrade to fail. We strongly recommend that you take corrective action for warnings and errors before you proceed to upgrade your PPM instance.

The following table lists the generated prevalidation report files.

Prevalidation Report
File Name

Invalid Data Reported


Reports any of the following, if detected:

  • Requests integrated with Mercury Application Mapping that must now be moved to Universal CMDB tables

  • Request types that contain the MAM Impact Analysis field group, which must now be replaced with the uCMDB field group

JVM PreValidation.html

Reports the following, if detected:

  • JVM (Java virtual machine) is not installed and configured on the Oracle database server.

  • PPM Workbench Java plug-in version has been customized.


Lists any calendars with names that conflict with system calendars.


Reports whether the state is missing on any business objectives.


Reports whether the start and finish periods for some projects are missing from the project field groups table.


Reports any of the following, if detected:

  • Values in the resource_pool_seq column for parent resource pool are not continuous in the rsc_resource_pools table

  • At least one row in the table rsc_rp_distribution_entries table has no start time

  • Incorrect parent org unit ID


Lists any missing access grants that are required for the PPM user.


Lists any tablespaces that are configured in PPM but are missing from your database. The tablespace names are configured in the kins_tablespaces table in the database schema. If problems are detected, you must manually update the kins_tablespaces table.


Reports on whether any actuals in Time Management do not match the corresponding actuals in Project Management any tasks or projects.

Prevalidation also detects invalid configuration and insufficient database access rights.