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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

How You Upgrade from <strong>Ingres</strong> 6.4 Using Upgradedb (Alternate)Remove Non-table ObjectsThe purpose of removing non-table objects is to reduce the database to basetables.Some database objects such as procedures and views can be very complicated,and some past versions of upgradedb did not always process themsuccessfully. Additionally, processing of some objects (grants in particular) isslow and expensive. Dropping the grants and later recreating them avoids anypossible failure due to lack of transaction log space.Note: Do not process <strong>Ingres</strong> Star distributed databases.To remove non-table objects1. Drop all non-table objects from the database including:• Optimizer statistics• Views• Rules• Database procedures• Database events• Secondary indexes• Grants and QUEL permits• QUEL integrities2. Modify all tables to heap.UNIX:To perform this step automatically1. Use the shell script oi_prep.sh. The script is available from <strong>Ingres</strong>Technical Support.Using the C shell, issue this command:oi_prep.sh dbname |& tee oi_prep.logIf there are any dependent views, “drop” errors messages may be reportedon those views (oi_prep.sh does not drop views in reverse dependencyorder); ignore the “drop” errors2. Run verifydb checks against the database.The verifydb -odbms command may output the following messages, whichyou can ignore:S_DU1611_NO_PROTECTS iirelation indicates that there are protections fortable (owner), but none are defined.Upgrading from <strong>Ingres</strong> 6.4 111

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

Saved successfully!

Ooh no, something went wrong!