Ingres 9.2 Migration Guide - Actian

How You Upgrade from Ingres 6.4 Using Upgradedb (Alternate)S_DU0305_CLEAR_PRTUPS Recommended action is to clear protection informationfrom iirelation, and S_DU1619_NO_VIEW iirelation indicates that there is aview defined for table (owner), but none exists.S_DU030C_CLEAR_VBASE Recommended action is to clear view base specificationfrom iirelation.Also ignore the “patch warning” message that warns of the loss of usertables in “runinteractive” mode. This mode will not be used.3. If some databases produce a “verifydb failed” message and then abort, runthe Terminal Monitor with the update system catalogs flag, as follows:sql +U dbnameSELECT * FROM iistatistics;\goNo rows should be returned. If there are rows, this is the probable cause ofthe verifydb problem.4. If there are rows, delete them, as follows:DELETE FROM iistatistics;COMMIT;\go\quit5. Rerun the verifydb command as shown at the end of the oi_prep.sh.6. If error messages are returned from verifydb, correct the problems beforecontinuing. Contact Ingres Technical Support for help, if necessary.Checkpoint and Turn Off JournalingFor each database, including the iidbdb, checkpoint each database and turn offjournaling. Then save the configuration file.The upgradedb process turns off journaling, so it is best to turn if off now. Ifupgradedb fails, you can use this checkpoint to recover and try again.To checkpoint and turn off journaling1. Checkpoint each database, using the ckpdb command with -j option to turnoff journaling. Issue the following command:ckpdb -d -j dbnameNote: For the iidbdb, use the ckpdb -s option. The iidbdb database doesnot have an "unload" directory.2. 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}112 Migration Guide