Ingres 9.2 Migration Guide - Actian

Unload/Reload Procedure for Upgrading from 6.4Archiver Exit ShellscriptTransaction Log SizeIngres has a sample Archiver exit script, acpexit.def. If the Ingres 6.4 acpexitscript was customized, you must carry over these changes to the Ingresinstallation.For information about the acpexit script, see the System Administrator Guide.Generally, Ingres uses less transaction log file space than Ingres 6.4. A fewoperations may use more (for example, MODIFY TO MERGE). To allow for itsimproved logging algorithms, Ingres reserves transaction log space that it maynot actually write.The force-abort limit cannot be set as close to log-full as was possible in Ingres6.4.If your Ingres 6.4 transaction log was barely large enough, it may be advisableto increase the size before or during the upgrade.Unload/Reload Procedure for Upgrading from 6.4The unload/reload upgrade avoids the upgradedb program (except for iidbdb),in favor of unloading the Ingres 6.4 databases to flat files, recreating thedatabases under Ingres, and then reloading the databases. This approach hasthe advantage of starting with clean databases, but requires more time anddisk space than does the upgradedb method.Note: Databases using the system-maintained logical key feature are bestupgraded using upgradedb. Tables that contain SYSTEM_MAINTAINEDtable_key or object_key columns cannot be safely unloaded and reloadedwithout additional work. The reload step generates all new logical key values.If other tables reference the logical key columns, the new values must bemanually propagated to those tables.94 Migration Guide