Ingres 9.2 Migration Guide - Actian

How You Upgrade from Ingres 6.4 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.Configure IngresRun Configuration-By-Forms (CBF) and initially configure the Ingresinstallation. Use the rundbms.opt and showrcp information from Ingres 6.4 asa guideline. For information about CBF and the various tuning parameters, seethe System Administrator Guide.Information on the correlation between 6.4 and Ingres parameter names, isdescribed in Corresponding Parameter Names (see page 114).Derived parameters are recalculated when values they depend on are changed.If derived parameters are set, they can be “protected” against change.Ingres versions from 2.0 through 2.6 may calculate very large default lock andresource limits parameters. Check the lock_limit and resource_limit settings,and consider reducing these limits to the Ingres 6.4 settings.On OS-thread platforms, do not turn on async_io; and do not declare theII_NUM_SLAVES Ingres variable.Ingres supports larger qef_sort_mem values than Ingres 6.4. Ingres may notneed as much qsf_memory as did Ingres 6.4. OS-thread platforms should notreduce quantum_size, as it does not improve performance on those platforms.Upgrading from Ingres 6.4 103