Re-upgrading the database is necessary if legacy clients have connected to a database of a newer version during the IPUP. Prior to any database upgrade, perform a full restorable backup of the OnBase database.
When the database schema is updated, new tables and columns are created. Older client software ignores the new tables, but when new tables are encountered, those tables are populated with null values. Re-upgrading the database removes the null values and populates the tables with default values. This requires a short period of scheduled downtime while the database schema is reset and the upgrade is re-run.
Hyland recommends that this is performed during key stages throughout the IPUP, but it is only necessary as a last step.
In previous versions, your first line of support needed database access in order to run the re-upgrade script. In OnBase 16, Hyland enabled administration of this within the Configuration module. To perform this action, the administrator must be assigned the System Configuration configuration right and the Database Management product right.
The -ROMANZO switch must also be applied.
Before using features enabled by the -ROMANZO switch, ensure that you understand the feature and implications of any changes to your system. Contact your service provider with any questions regarding these features. Features enabled by the -ROMANZO switch should not be made available to the casual user. Remove the -ROMANZO switch after completing necessary actions.
For instructions on how to re-upgrade the database, see the topic titled Database Functions in the System Administration module reference guide.