Tables

This topic describes the warnings that database tables can contain.

In this topic:

Extra Table

The OpenText Application Quality Management schema should contain only the tables that are defined in the schema configuration file. Adding extra tables on top of the schema is not supported and might cause future problems with OpenText Application Quality Management.

Problem: If the verification process finds extra tables that were added manually to the schema, it generates an Extra Table warning.

Solution: Do one of the following:

• Change the Schema. If you use the table, copy it to a different schema. If you do not use the table, delete it. Before taking either action, back up the schema and consult your database administrator. For details, see Change the database user schema.

• Use the Exception File.

  If the project database is case sensitive, the table name must be the same in both the database and the exception file.

Missing Table

The verification process checks that all of the tables defined for the project schema actually exist (according to the tables of each Quality Center/OpenText Application Quality Management version).

Problem: If a table is missing, the verification process generates a Missing Table warning.

Solution: Do one of the following:

• See Change the database user schema.

• Run the repair process to create the missing table. Although you can use the repair process to add these objects, we recommend that you contact OpenText Support to make sure that the missing objects are not just symptoms of a bigger problem.