Preparing to upgrade the database

The Application Security database migration process creates larger transactions than those created during regular use. For databases that have been successfully run in production environments, database migration does not typically require changes to your database configuration or resources. For large databases, OpenText recommends that you review and, if necessary, increase the database resources and settings required to accommodate the migration process.

If you are upgrading from version 23.1.0 or earlier to version 23.2.0 or later, you need to be aware that during migration the ID column type in the scan_issue table is changed from INT to BIGINT for MySQL and SQL Server databases to avoid reaching the maximum 32b integer limit.

If you have already applied the recommended workaround for SQL Server to reset the identity value on the scan_issue table to a negative number with DBCC CHECKIDENT (scan_issue, reseed, -2147483648), then you must perform an additional manual migration step. Reset the identity value back to a positive number after the migration. To perform the reset, run the query: DBCC CHECKIDENT (scan_issue, RESEED). The user running the query must be either an owner of the schema that contains the table or must have the sysadmin, db_owner, or db_ddladmin fixed database role.

If you are upgrading a MySQL database, see Setting the Innodb Buffer Pool Size when upgrading a MySQL database.