Ingres 9.2 Migration Guide - Actian

Typical Upgradedb ProblemsThe following message occurs shortly after the upgradedb utility startsprocessing a database: “E_SC0206 An internal error prevents furtherprocessing of this query.”This message is seen when upgradedb –all is used, and the databasedata ROOT location is not the same as others processed in the sameupgradedb 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 theupgrade.Warning messages appear after upgradedb announces “Reloadingquery- tree objects.”Although the messages are warning messages and the database is shownas having been upgraded, some views, permits, or other objects have beenrecreated incorrectly and are missing from the database, so treat thesewarnings as if they are fatal errors.Refer to the following files found in the directory$II_SYSTEM/ingres/files/upgradedb/UPGRADEUSER, where UPGRADEUSERis the user who ran upgradedb, for example “ingres”:• upgradedb.log• upgradedb.dbg• dbname.innSQL terminal monitor script, where dbname is the name of thedatabase being upgraded and nn is the sequence number of theupgrade for that database starting from 1.• dbname.onnOutput from dbname.inn, where dbname is the name of thedatabase being upgraded and nn is the sequence number of theupgrade for that database starting from 1.You can identify the problem by inspecting the messages found inupgradedb.log. Data is appended to this file, so more than one entry mayexist for dbname.A possible cause of failure is that a table used in a database procedure hasbeen dropped and when that procedure is being recreated as part ofupgradedb, the program fails due to table not found.You may be able to resolve the problem by inspecting the output file(dbname.onn) and then editing the dbname.inn file. Make copies of thefiles before making changes. After you have made the changes to thedbname.inn file, rerun it using the Terminal Monitor.For assistance, contact Ingres Technical Support.78 Migration Guide