Share this page
The verification process helps to ensure that the project database user schema is correct and configured as expected.
The verification process performs two types of schema verifications:
-
Schema Correctness. Checks that the project database schema includes all of the required schema objects, as defined in the expected database user schema for the project. This verification ensures that all of the required entities exist and are defined as expected. It also ensures that there are no extra entities defined on top of the schema.
-
Alignment to the current version. Notifies you about differences in the project database user schema caused by internal changes made in Quality Center or OpenText Application Quality Management. In this way, the verification process aligns the schema with the latest internal changes to the schema made in preparation for the upgrade.
The verification process displays warnings in the verification report if it finds the following:
-
Extra entities defined. For example, Table, Column, Trigger, View, and Sequence.
-
Differences from the expected definitions. For example, Column Size and Index Attributes.
-
Missing objects.
Schema differences found by the verification process can cause upgrade failures or usage problems. As long as the verification process still finds these differences, an upgrade to the current OpenText Application Quality Management version will not start.
Note: Many of the schema changes can be fixed automatically by the repair process.
The following sections contain possible warnings, grouped by the different database objects, that the verification process can display in the verification report:
