When upgrading from OpenIngres 1.2 or 2.0, Ingres II 2.0 or 2.5, or Ingres 2.6, we recommend the upgradedb method. The upgrade is internally much simpler than the upgrade from 6.4. In addition, there are fewer application-level incompatibilities among newer versions.

An unload/reload upgrade is possible, but is slower and requires more disk space than an upgradedb upgrade.

OpenIngres 1.2: If you are starting with OpenIngres 1.2, any tables having long varchar, long binary, or long spatial data must be unloaded under 1.x and reloaded into the new Ingres version. The format of the blob extension tables has changed. The remainder of the database can be upgraded with upgradedb; however, it is probably simplest to use a full unload/reload upgrade with any databases containing “long” data types.

Ingres 2.6: The Enhanced Security feature was removed after Ingres 2.6 and cannot be upgraded. When upgrading from Ingres 2.6, if this feature is present in your 2.6 installation, it must be disabled and removed before upgrading.

Pre-9.2: When upgrading from a pre-9.2 installation to a 9.2 or later installation that uses the setting II_CHARSETxx=UTF8, normalization of character data in non-Unicode columns is required. Contact Actian Services to help with an upgrade plan.