Ingres 9.2 Migration Guide - Actian

Schema CheckingKnown Installation IssuesNote: For more information about these issues, check the technical documentsavailable at the Ingres Technical Support web site.Creating the Ingres System Administrator account from within VMSINSTALdoes not assign the correct process quotas to the account. (For the correctquotas, see the Installation Guide.) The workaround is to create the accountbefore the VMSINSTAL process is started with the correct privileges andprocess quotas.II_WORK is not picked up, if pre-defined in the local symbol table, when anExpress installation is performed. The user must enter the correct informationwhen prompted.If Ingres is installed from a non-Ingres System Administrator account, imadb iscreated as the process owner for VMSINSTAL rather than the installation ownerconfigured earlier. When Ingres is started, the RMCMD process will hangbecause it is running as a user that is unable to connect to the RMCMDcatalogs in imadb. The workaround is to install Ingres as the intended IngresSystem Administrator.Schema CheckingIngres reserves a number of new keywords, mostly for support of SQLadditions. If names such as substring, first, or cache are used as columnnames, you must change the database schema. For a list of Ingres reservedwords, see the appendix “Keywords” and the SQL Reference Guide.If you are concerned that some column names in your database may conflictwith reserved words, you can take a copy of the schema from the currentinstallation and load it into an Ingres database. You should extend thesechecks to the applications to verify that tables and views created at runtimeare not affected by the new keywords. Conflicts found in the schema andapplications must be removed before moving to Ingres.Considerations for Alpha OpenVMS 83