Troubleshooting Upgradedb

This chapter describes how to troubleshoot problems you may encounter when using the upgradedb utility.

The best way to avoid problems with the upgradedb utility is to upgrade to the most recent service pack of Ingres, and to follow the upgrade steps carefully.

Note: If you are upgrading to Ingres II versions 2.0 or 2.5, make sure you install the latest patch available for your platform before performing the upgradedb step.

• The upgradedb utility starts to process, and then hangs with no error indication.

  This condition is probably caused by the Remote Command Server interfering with the upgradedb process, which is likely if you are upgrading to Ingres II 2.0 instead of Ingres 2006. Use the rmcmdstp command to stop the Remote Command Server.

  You can use Configuration-By-Forms or Visual Configurator to turn off the Remote Command Server until the upgrade is finished: select Remote Command Server and use EditCount to set the startup count to zero.

• The following message occurs: "Product name has been made uninstallable by an incompatible dictionary upgrade."

  This message is caused by extra or incorrect rows in the front-end catalog ii_client_dep_mod. The rows may have been created by very old versions of Ingres. You can ignore this message.

• The following message occurs shortly after the upgradedb utility starts processing a database: "E_SC0206 An internal error prevents further processing of this query."

  This message is seen when upgradedb –all is used, and the database data ROOT location is not the same as others processed in the same upgradedb run. The errlog.log shows the message "E_DM9004_BAD_FILE_OPEN" referencing a filename: aaaaaaaa.cnf, shortly before the E_SC0206 message.

  This message has occasionally been seen in various versions of upgradedb. Simply rerun upgradedb for the one failed database, and continue the upgrade.

• Difficulties arise after upgradedb announces "Reloading query tree objects."

  The database may be usable but lack one or more views, permits, or other objects. Refer to the generated SQL script and output files in the directory $II_SYSTEM/ingres/files/UPGRADEUSER/ (where UPGRADEUSER is the user who is running upgradedb, typically "ingres"). You may be able to resolve the problem by inspecting the output files. You can complete the upgrade by re-running the input script files through the Terminal Monitor. For assistance, contact Ingres Technical Support.

Other Upgradedb Problems

If something else goes wrong with the upgradedb utility, contact Ingres Technical Support for help.

For problems with a single database, customer support can assist you in restoring the database data files from your system backup and resetting the database information in iidbdb so that you can retry upgradedb. In the worst case, it may be necessary to restore the entire installation from your system backup, fix the database problem, and redo the upgrade.