10.07.2015 Views

Ingres 9.2 Migration Guide - Actian

Ingres 9.2 Migration Guide - Actian

Ingres 9.2 Migration Guide - Actian

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Alternate Upgradeb ProcedureFix FE Reload ScriptBecause the new database was not created with front-end catalogs, it is notnecessary to drop them.To fix the front-end reload script, for each database:1. Open the file cp_ingres.in.2. Delete the following lines:\include/ing64/ingres/files/iiud.scr\include/ing64/ingres/files/iiud64.scrNote: The directory path may differ.3. Save the file.Alternate Upgradeb ProcedureThe upgradedb utility in <strong>Ingres</strong> 2006 is enhanced to allow 6.4 databases to beupgraded using the standard procedure in the chapter “Upgrading UsingUpgradedb.” Due to the many enhancements made since <strong>Ingres</strong> 6.4, theupgradedb 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 thissection. This modified procedure is designed so that the upgradedb utility hasto perform as little work as possible, so that it will correctly handle theupgrade tasks.In the procedure, each database is prepared by dropping all objects that canbe recreated, that is, by dropping everything but the base tables. Each basetable 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 generateSQL that recreates database objects and storage structures. If proceduresalready exist to recreate database objects and storage structures, you can usethese instead. Make sure, however, that the procedures recreate all therelevant 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 userwho owns objects in any database (using login or UNIX “su”). If this is notfeasible, you can run as the installation owner (default user ID is ingres), anduse the -u{user} flag to pretend to be that user whenever you must run an<strong>Ingres</strong> command.106 <strong>Migration</strong> <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!