Hello,

Reserved words are less critical with Ingres 2.6 (context evaluation of
keywords). For cookbook please see the file mg.pdf (Migration Guide) in the
standart documentation.

The path is to unload reports, frames and application (ABF) and to reload
them (instead transporting them with unloaddb).

For OpenROAD, duplicate your database to compile it with OR 4.1 and keep
somewhere a version in 3.5 Once an application is compiled in a newer
version a return in the older one is no more possible. If your application
need to be modified, modify it in the 3.5 environment, and report
modification in the 4.1 environment.

Issues you can find is more newer Ingres is more "near to the doc" it is.
Some syntax pb can appear then, but not so many. I've done many migration
from an Ingres version to an other (6.4 or 2.0 to 2.6 or 2006) sometimes
from an OS to an other (Unix to Linux) and I never find someting without a
solution or workaround.

Hope this help.
Jean-Pierre

2006/12/23, Colin Hay <wobble7@hotmail.com>:

Hi Colin,

I just went through the same exercise upgrading from II2.0 to II2.6sp3 on
Solaris 7.

I was relatively straight forward following the migration guide, but I did
find that following the unload/reload method
Where it says to create the database in the new installation  using the -f
nofeclient then loading the data and running upgradefe <db> INGRES failed
with a 'already at version 3' message, and the system catalog table that
previously contained a column 'system_maintained', was left unchanged, when
it should have been changed to 'sys_maintained'.

To get round it, created the databases as normal, then edited the copy.in
and manually changed the system_maintained to sys_maintained and the reload
was seamless.

Of course I was in the awkward position of the live server being the only
solaris box available, so was not able to test the upgrade method, and on
Ingres Corps recommendation I basically verifydbed all tables in all
databases, unloaded them, verified the unload by reloading to a temp
database to ensure that the unloaded data was valid, then as each database
unload was proved good, I destroydb'ed that database until all I had was the
iidbdb and imadb, then installed the new version over the top, and the
installation realised that it was an upgrade and proceeded accordingly.

NOTE, Ingres Corp recommended that I upgraded directly to II2.6 Service Pack
3, which they provided for download, and that is exactly what I did.

Admittidly the server was effectively down for a week, but since everyone
else had gone on christmas hollidays, it did not affect anybody, and the
preparation took 4 days to verifydb/unload/reload/verify and 1 day to
actually install/upgrade the installation and reload the live databases

Cheers

Richard

/**********************************\

\**********************************/

-----Original Message-----
From: info-ingres-admin@cariboulake.com
[mailto:info-ingres-admin@cariboulake.com] On Behalf Of Colin Hay
Sent: Sunday, 24 December 2006 2:20 a.m.
To: info-ingres@cariboulake.com
Subject: [Info-ingres] Ingres upgrade

Got an Ingres upgrade to do coming up soon - from 2.0 to 2.6 on Solaris
along with an Upgrade of OpenROAD from 3.5 (!) to 4.1 sp3

Is there still a cookbook for this or is it just the usual unloaddb and
checking for reserved words ?

Colin

_______________________________________________
Info-ingres mailing list
Info-ingres@cariboulake.com
http://mailman.cariboulake.com/mailman/listinfo.py/info-ingres