The following document guides you through the database upgrade process using a collection of procedures and functions collectively referred to as a package. There are two packages, IN_DB_UTIL and IN_DB_UPGRADE.
You can use the IN_DB_UPGRADE package as an alternative to the traditional database incremental scripts.
The IN_DB_UPGRADE package provides a means for you to upgrade the Perceptive Content database schema in a manner that facilitates the execution of the most time-consuming schema changes in uptime to reduce the duration of downtime events during database upgrades.
This package supports upgrading the inuser database schema to version 7.9.0.0 (22.2) or 7.7.0.0 (22.1 and EP4) or 7.5.0.0 (EP3 and EP2) from 7.7.0.0 or 7.5.0.0 or 7.4.0.3 or 7.2.3.0 or 7.2.0.0 or 7.1.5.2 or 7.1.4.0 or 7.1.3.3. It supports both the Unicode and ANSI versions of the schema.
This upgrade package is ideal for customers with very large databases who might benefit from executing the longest running operations in uptime, resulting in a much shorter downtime event during the upgrade.
This upgrade is also ideal for customers that are many versions behind as it simplifies the upgrade process by facilitating the upgrade with just a few commands instead of manually executing multiple incremental DDL scripts to upgrade the database schema to the latest version.
Using this package to upgrade the database schema involves the duplication of the IN_DOC table as well as several large indexes. The size of the indexes depends on your schema version. This requires the allocation of additional storage for the duration of the upgrade, which can be reclaimed afterwards if necessary.