Ingres 9.2 Migration Guide - Actian

How You Perform an Upgrade Using Unload/ReloadRestore Site ModificationsRestore any site-specific files that you copied in the step Preserve SiteModifications.If the checkpoint template file cktmpl.def has been modified, the modificationsmay need to be carried forward into Ingres. The cktmpl.def from Ingres 6.4cannot be used with Ingres, as the file format has changed. This means thatyou must recreate the changes using the Ingres 6.4 cktmpl.def as a guide. Seethe Ingres 6.4 Database Administrator's Guide.If the archiver exit script acpexit was changed in Ingres 6.4, you must makethe changes to the Ingres template (acpexit.def), and then move that file to$II_SYSTEM/ingres/files/acpexit.Review Ingres ConfigurationIf you are doing a clean install, you need to change the default Ingresconfiguration to match your site requirements.If you are doing an in-place upgrade, the upgrade process preserves youroriginal Ingres installation parameters. You should review the configurationbecause some parameters may change from version to version. Forinformation on parameters that changed, check the Readme for your newversion of Ingres.Review your parameter settings by running Configuration-By-Forms orConfiguration Manager. Especially pay attention to major items such as startupcounts and DBMS cache settings. If you are doing a clean install, you can useyour original Ingres installation configuration as a guide.Note: If you disabled the Remote Command Server in the step Disable RemoteCommand Server, use EditCount to restore its startup count to the originalvalue.Set Up Ingres NetCreate the vnode definitions for the remote installations by using netutil. Ifusing shadow passwords on UNIX, you must run mkvalidpw. For details, seethe Connectivity Guide.If there are NFS client-only installations that have not been set up, runingmknfs to set them up.Upgrading Using Unload/Reload 69