Share this page

# General validation

This topic describes the general validation checks the verification process performs.

In this topic:

## Supported database version

The verification process checks that the project schema is stored in a supported database server. If the verification process detects that the database server version is not supported, it displays a warning.

Note: For the most up-to-date supported environments, see Support Matrix

## Valid Database User Schema Name

The upgrade mechanism does not support databases that include special characters in the database name. If the verification process finds special characters, you must remove them. For SQL databases, periods are also not supported in the database user schema name.

To remove special characters from database names:

1. Deactivate the project.

2. Ask your database administrator to rename the database user schema to a name that does not include special characters, or periods for SQL databases.

3. Remove the project from Site Administration.

4. Update the Dbid.xml file to point to the new database user schema name.

5. Restore the project by using the updated Dbid.xml file.

6. Run the verification process again to make sure the problem is resolved.

## Mixed Table Ownership

OpenText Application Quality Management can connect to Microsoft SQL server by using SQL authentication or Windows authentication.

For each of these methods, a different user owns the tables of a project:

- SQL Authentication. Table owner is the user `td`.

- Windows Authentication. Table owner is the user `dbo` (a user mapped to the operating system user that runs the OpenText Application Quality Management server).

If you create a project with one type of authentication (for example, SQL), and then restore it with the other type of authentication (for example, Windows), these tables cannot be accessed. In this case, new tables are created with owners that are different from those of the old tables. You will not be able to work with the project. It is likely that the upgrade will fail.

To prevent this problem, the duplicate ownership validator checks that the owner of all of the tables in the project database user schema matches the connection method that OpenText Application Quality Management is using to connect to the server.

To fix table ownership manually, do one of the following:

- SQL Authentication: Run the following query to make `td` the table owner:

    EXEC sp_changeobjectowner '<table name>', 'td'

- Windows Authentication: Run the following query to make `dbo` the table owner:

    EXEC sp_changeobjectowner 'td.<table name>', 'dbo'

## Database permissions

To enable an upgrade to the current OpenText Application Quality Management version, the project schema requires a set of minimum required permissions. The verification process makes sure that both the project user and the administrator user have all the privileges needed to perform the upgrade.

## Text Search Configuration

If your database does support text search, OpenText Application Quality Management installs the required components when creating a new project database. OpenText Application Quality Management also activates the text search for the new database. The verification process checks whether your project has the text search feature enabled, and that it is configured correctly.

The verification process validates the following:

- Validity of the Text Search Configuration

- Only Valid Fields Configured Under "Text Search"

- Text Search Validation for Oracle Database Server

- Text Search Validation for Microsoft SQL Database Server

Validity of the Text Search Configuration

The verification process checks that text search components are installed and are valid on the database server. If a database server is text search-enabled in the DB Servers tab in Site Administration, text search must also be enabled on the Oracle or SQL database server. If the verification process detects that text search is not enabled or configured incorrectly on the Oracle or SQL database server, the upgrade process does not run until you manually repair the problem.

We recommend that you ask your database administrator to reconfigure text search on the Oracle or SQL database server. Alternatively, as a workaround, you can disable text search for the database server from Site Administration.

To disable the text search for the database server:

1. Run the following query on your Site Administration schema:

       update <SA Schema>.dbservers set db_text_search_enabled = null where dbserver_name = '<DB logical name>'

2. Restart the OpenText Application Quality Management server.

3. Run the repair process for your projects.

4. When the repair process completes, run the following query:

       update <SA Schema>.dbservers set db_text_search_enabled = 'Y' where dbserver_name = '<DB logical name>'

5. Restart the OpenText Application Quality Management server.

Only Valid Fields Configured Under "Text Search"

The verification process checks that only valid fields are defined as searchable. You can enable the text search only for specific entities, and only on fields of the type string or memo. The following entities are supported: BUG, COMPONENT, COMPONENT_STEP, DESSTEPS, REQ, TEST, BPTEST_TO_COMPONENT, and CYCLE. Any other configuration could cause functionality problems during upgrade or customization. This problem is fixed automatically by the repair process.

Text Search Validation for Oracle Database Server

For an Oracle Database server, the verification process checks the following:

- Validity of Text Search Indexes. The verification process checks that database text search indexes are valid. Invalid text search indexes can cause functionality problems and even upgrade failure in OpenText Application Quality Management. If the verification process detects an invalid index, try to recreate the index by dropping it from the schema and creating it again. In Site Administration, click the Site Projects tab. Select the relevant project and click the Enable/Rebuild Text Search button. If this procedure returns an error, consult your database administrator or contact OpenText Support.

- Validity of Project Database User Permissions. The verification process checks that the project database user has the required permissions to work with text search. When text search is installed on the database, the role CTXAPP is created automatically. OpenText Application Quality Management requires that this role be granted to all projects database users that support text search. (OpenText Application Quality Management grants the CTXAPP role automatically when creating the project or enabling the text search for a project.) If this role is not granted to the project database user (configured to support text search), the verification process returns a warning. In these cases, ask your database administrator to grant the required role to the project database user.

Text Search Validation for Microsoft SQL Database Server

The verification process checks that the project database user schema enables the text search feature. To work with text search on SQL project, you need to enable the text search on the database.

To enable text search on the database:

1. Select the database from the SQL server Enterprise Manager.

2. Right-click the database name.

3. Select Properties/Files.

4. Select Use Full-Text Indexing.

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: