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.

Unload/Reload Procedure for Upgrading from 6.4Unload/Reload Upgrade TypesYou must choose one of the following variations of the unload/reloadprocedure:• In-place upgrade, which replaces the 6.4 installation with the new <strong>Ingres</strong>installation. The master database (iidbdb) is upgraded with upgradedb,even though other databases are unloaded and reloaded. Because theiidbdb remains, all your locations, users, groups, and roles still exist in thenew installation.• Clean install upgrade, which leaves the 6.4 installation alone. <strong>Ingres</strong> isinstalled into a completely new installation. (The new installation may evenbe on a different machine.) When performing a clean install upgrade, youmust take extra steps to recreate locations and move users, groups, androles from the 6.4 installation to the new one.Front-end Catalogs and the Upgradefe ProgramThe hardest part of the unload/reload upgrade is dealing with the front-endcatalogs. These catalogs are unloaded in <strong>Ingres</strong> 6.4 format, and cannot beloaded into an <strong>Ingres</strong> database. To circumvent this problem, the <strong>Ingres</strong>database is created without front-end catalogs. The catalogs are then loaded inthe <strong>Ingres</strong> 6.4 format and upgraded using the upgradefe program.Upgrading from <strong>Ingres</strong> 6.4 95

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

Saved successfully!

Ooh no, something went wrong!