Ingres 9.2 Migration Guide - Actian

Considerations for Ingres 6.4Application Preparation SummaryMany of the changes required for Ingres are backward compatible with Ingres6.4. Make application changes in the Ingres 6.4 installation, and bring themforward to the Ingres installation for testing. In this way, you do not have tofreeze application development while preparing for Ingres.At this stage, resist the temptation to make Ingres-specific applicationchanges. While an outer join or a session temp table may enhanceperformance, there is plenty of time to add performance enhancements afterthe upgrade.System PreparationTake the following steps to prepare your system:• Change customized start and stop shell scripts to reflect new commands• Change shell scripts that use ingprenv1 environment variable• Carry forward any changes to archiver exit script• Change transaction log parameter settingsIngres Startup and Shutdowningprenv Replaces ingprenv1Ingres uses new commands for startup and shutdown: ingstart and ingstopinstead of iistartup and iishutdown. If you have customized shell scripts thatstart and stop Ingres, you must change them. Verify the changes in thedevelopment Ingres installation and have the revised scripts ready for theproduction environment at time of upgrade.If you are running multiple DBMS servers with Ingres 6.4, you should be ableto simplify your startup and shutdown procedures. Ingres supports multipleDBMS servers directly from the Ingres configuration.In Ingres, the ingprenv command replaces the Ingres 6.4 ingprenv1 command,which displayed one Ingres environmental variable. Shell scripts that useingprenv1 must be changed.It is possible to recreate ingprenv1 as follows:echo 'exec $II_SYSTEM/ingres/bin/ingprenv $*' >/usr/local/bin/ingprenv1chmod +x /usr/local/bin/ingprenv1Upgrading from Ingres 6.4 93