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.

Chapter 5: Troubleshooting UpgradedbThis section contains the following topics:How to Avoid Upgradedb Problems (see page 77)Typical Upgradedb Problems (see page 77)Other Upgradedb Problems (see page 79)How to Avoid Upgradedb ProblemsThe best way to avoid problems with the upgradedb utility is to upgrade to themost recent service pack of <strong>Ingres</strong>, and to follow the upgrade steps carefully.Typical Upgradedb ProblemsHere are some typical problems you may encounter when using the upgradedbutility.The upgradedb utility starts to process, and then hangs with no errorindication.This condition is probably caused by the Remote Command Serverinterfering with the upgradedb process, which is likely if you are upgradingto <strong>Ingres</strong> II 2.0 instead of <strong>Ingres</strong> 2006. Use the rmcmdstp command tostop the Remote Command Server.You can use Configuration-By-Forms or Visual Configurator to turn off theRemote Command Server until the upgrade is finished: select RemoteCommand Server and use EditCount to set the startup count to zero.The following message occurs: “Product name has been madeuninstallable by an incompatible dictionary upgrade.”This message is caused by extra or incorrect rows in the front-end catalogii_client_dep_mod. The rows may have been created by very old versionsof <strong>Ingres</strong>. You can ignore this message.Troubleshooting Upgradedb 77

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

Saved successfully!

Ooh no, something went wrong!