Overview

The verification process, described in Verify domains and projects, detects inconsistencies and indicates which problems the repair process can fix automatically, and which you should repair manually. Suggested solutions for repairing each issue are provided in this appendix.

If an error is displayed during the verification or upgrade process, you can see error descriptions at this KB article.

If a warning is displayed during the verification process, you can use the Quick Warning Reference to locate the corresponding solution for that warning.

Some solutions require that you change the database user schema:

• Database User Schema. Database in SQL Server and a user schema in Oracle. This term is used for both cases because OpenText Application Quality Management can be deployed over SQL Server and Oracle. Both cases are logical sets of database objects (for example, tables, indexes, and so on) owned by the same logical owner.

• Expected Database User Schema. OpenText Application Quality Management Database User Schema configurations, as defined in the configuration file for a new Database User Schema. As a preparation for the current version, each project database user schema should be aligned with the latest configurations, as defined in this schema.

If you need to modify the database user schema, see the additional instructions under Change the database user schema.