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.

How You Upgrade Using the Upgradedb UtilityCheckpoint and Turn Off JournalingFor each database, including the iidbdb, checkpoint each database and turn offjournaling. Then save the configuration file.To checkpoint and turn off journaling1. Checkpoint each database, using the ckpdb command with –j option toturn off journaling. (The upgradedb process turns off journaling, so it isbest to do that now.) If upgradedb fails, you can use this checkpoint torecover and try again.Issue the following command:ckpdb -d -j dbname2. Save the configuration file stored in the dump area after each checkpoint.The configuration file is small. Issue the following command:cp $II_DUMP/ingres/dmp/default/dbname/aaaaaaaa.cnf {somewhere secure}Shut Down <strong>Ingres</strong>Shut down <strong>Ingres</strong> with the ingstop command.Preserve Site ModificationsCommonly Customized FilesFiles distributed as part of <strong>Ingres</strong> that you have customized will be lost duringthe upgrade. Any custom files you have added to the $II_SYSTEM directorytree will remain.You must copy your customized files to a safe place. Do not copy them to /tmpor anywhere in $II_SYSTEM/ingres directory.If local collation sequence files have been customized, save the originalcollation definition files and the compiled files that reside in$II_SYSTEM/ingres/files/collation.The following files are typically customized:• Termcap files in $II_SYSTEM/ingres/files• Keyboard map files in $II_SYSTEM/ingres/files• Local collation sequence files48 <strong>Migration</strong> <strong>Guide</strong>

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

Saved successfully!

Ooh no, something went wrong!