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.
Upgrading from versions prior to OnBase 16 required a call to Technical Support to run a script. This functionality is native to OnBase 16. For more information, see the topic Re-upgrading the Database in Part 4 - Considerations for Versions Previous to 16.