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 Perform an Upgrade Using Unload/Reload(Optional) Print Optimizer StatisticsNote: This step applies only to a clean-install upgrade.Print optimizer statistics for each database. If your upgrade plan allows enoughdowntime to run a full optimizedb against your databases, you can omit thisstep. If your plan does not allow enough downtime, perform this step as ashortcut.Note: Using this shortcut may result in some of the new <strong>Ingres</strong> metrics notbeing available; query performance may suffer until a full optimizedb can becompleted.If you are upgrading from Open<strong>Ingres</strong> 1.x, you should regenerate newstatistics instead of saving the old ones, if possible.To print the existing optimizer statistics, run statdump with the -o flag to a filefor each database, as follows:statdump -o dbname.stats dbnameRecord Database InformationFor each database, you will need to know information such as whether thedatabase was journaled, where the database resides, and in what order thedata locations were configured.To record database information1. Run infodb against each database. Issue the following command:infodb dbname >infodb.outSave the output for later.2. Record whether the database is public or private.To find out, use the catalogdb command. Select Databases, and then enterthe database name. The screen that appears has an Access field thatindicates whether the database is public or private.Upgrading Using Unload/Reload 61

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

Saved successfully!

Ooh no, something went wrong!