This is a discussion on Running upgradefe through netu from 2.6 -> 6.4 ? within the Ingres forums, part of the Database Server Software category; --> Hello, Does anyone one know what will happen if you run upgradefe on a vnode database where the vnode ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hello, Does anyone one know what will happen if you run upgradefe on a vnode database where the vnode is a connection from a 2.6 server to a 6.4 server/db? I don't really want to try it and see what will happen because if the effects are not good I'm not sure how to reverse it :-(. Will this have any impact on users accessing the db locally that are still on 6.4? We're getting different behavior from netu depending on how it's accessed. If we use isql, sql or qbf utilities there is no problem connecting from 2.6->6.4. But any abf apps, esqlc apps, reports from command line, or access through DBI::Ingres complains and fails to connect :-(. The error DBI is passing back from the connect attempt by the report command is: E_UI0029 Cannot start program; must upgrade catalogs This program cannot run against this database because some of the INGRES catalogs need to be upgraded. To upgrade the catalogs, run the command: upgradefe vnode::mydb INGRES E_RW13E8 Error connecting with database vnode::mydb. Processing stops. Thanks Dennis d underscore roesler at agilent dot com |
| Thread Tools | |
| Display Modes | |
|
|