The upgradedb utility in Ingres 9.0 is enhanced to allow 6.4 databases to be upgraded using the standard procedure in the chapter “Upgrading Using Upgradedb.” Due to the many enhancements made since Ingres 6.4, the upgradedb utility performs an intricate task when upgrading a 6.4 database.

If you encounter upgradedb problems in your testing, or if you prefer a safer (but more complex) procedure, use the alternate upgradedb procedure in this section. This modified procedure is designed so that the upgradedb utility has to perform as little work as possible, so that it will correctly handle the upgrade tasks.

In the procedure, each database is prepared by dropping all objects that can be recreated, that is, by dropping everything but the base tables. Each base table must be checked to make sure it is valid and has no internal damage. After the upgrade, the various database objects are recreated.

The procedure directs you to cut and paste the output of unloaddb to generate SQL that recreates database objects and storage structures. If procedures already exist to recreate database objects and storage structures, you can use these instead. Make sure, however, that the procedures recreate all the relevant objects. If users or applications dynamically create database objects, it may be safer to cut and paste from unloaddb.

The alternate upgradedb procedure assumes that you can become any user who owns objects in any database (using login or UNIX “su”). If this is not feasible, you can run as the installation owner (default user ID is ingres), and use the -u{user} flag to pretend to be that user whenever you must run an Ingres command.