Share this page

# Columns

This topic covers the warnings that database columns can contain.

In this topic:

## Extra Column

The verification process checks that each table includes the required columns, as defined for the expected database user schema and version. The schema should not include extra columns. Extra columns in a table might cause upgrade failure or functionality problems.

Problem: If the verification process detects an extra column (that does not exist in the database user schema definitions) in one of the tables, it generates an Extra Column warning.

Note: This problem requires manual repair. The repair process cannot fix it.

Solution: Do one of the following:

- Change the Schema. If you have an internal implementation that requires extra table columns, move the extra columns to a different table in a different schema. If you do not use a particular column, delete it. Before taking either action, back up your schema and consult your database administrator. For a more detailed explanation, see Change the database user schema.

- Use the Exception File.

Note: Not recommended: Instruct the upgrade to ignore this problem.

## Column Size Mismatch

The verification process checks that all the table columns are defined as expected. This validation ensures that the column size matches the expected size as defined for each table column. This verification excludes user-defined fields, whose size can be customized through project customization.

Problem A: Size is bigger than expected. If the column size is bigger than expected, decrease the column size to the required size manually. Because this operation can cause data loss, it is not performed automatically by repair process.

Note: This problem requires manual repair. The repair process cannot fix it.

Solution A: Consult your database administrator to resolve this issue. For risks involved in changing the database user schema, see Change the database user schema.

Problem B: Size is smaller than expected. If the column size is smaller than expected, the repair process fixes the problem automatically by increasing the column size to the expected size.

Solution B: Run the repair process to increase the current size to the required size.

## Column Precision Mismatch

In an Oracle Database, "precision" is the term used to define the size of fields with the INTEGER type.

Problem: The verification process generates a warning if the precision defined for a certain column is smaller than expected.

Solution: Run the repair process to increase the current precision to the required precision.

Column Type Mismatch

Changing a column type causes the upgrade to fail, and can cause major functionality problems.

Problem: The verification process generates a Column Type warning if the column type has changed.

Note: This problem requires manual repair. The repair process cannot fix it.

Solution: Consult your database administrator to resolve this issue. For risks involved in changing the database user schema, see Change the database user schema.

## Column Nullability Mismatch

One of the attributes that is defined for a column is whether it can accept null values. A null is the absence of a value in a column of a row. Nulls indicate missing, unknown, or inapplicable data. If you have defined a NOT NULL or PRIMARY KEY integrity constraint for a particular column, you cannot insert rows into the column without adding a value.

Problem: The verification process compares the required definitions for each column in the expected database user schema to the project database user schema. If it encounters differences in the column NULL attribute definition, it generates a Column Nullable warning.

Solution: Run the repair process. The repair process runs a query to modify the column attributes to the expected attributes.

If the column includes NULL values, the repair process cannot update the column attribute to NOT NULL (if this is the required attribute) for the column. Ask your database administrator how to remove the NULL values from the column. After removing the NULL values, run the repair process again. For details, see Change the database user schema.

## Identity Column

The IDENTITY property is one of the attributes defined for columns in Microsoft SQL server.

Problem: As part of the verification for the columns attributes, the verification process might find a column IDENTITY property that is not configured as expected.

Note: This problem requires manual repair. The repair process cannot fix it.

Solution: Change the IDENTITY property of the column to the expected configuration (according to the output from the verification process report) manually. Consult your database administrator to resolve this issue. For details, see Change the database user schema.

## Missing Column

If a column is missing from a table, run the repair process or contact OpenText Support.

Problem: If the verification process finds that a column is missing from one of the tables, it generates a Missing Column warning.

Solution: Do one of the following:

- Run the repair process to fix the problem.

- See Change the database user schema.

https://admhelp.microfocus.com Application Quality Management 8942
Tips to improve your search results... OpenText™ Application Quality Management Help Center OpenText™ Application Quality Management Help Center OpenText™ Application Quality Management Help 26.1 All View Local Help Center View Online Help Center Version: