We are looking at upgrading our version of Ingres from 2.0 to 2.6 on Solaris (due to the drop of support). Does anybody know of any issues surrounding the upgrade from version 2.0 to 2.6.

Thanks

Gregory Wilding
UK North Midlands Solutions Centre
Abney Park
Manchester Road
Cheadle
Cheshire SK8 2PD
Tel +44 (0) 161 495 3488
Fax +44(0) 161 428 5009
<mailto:gregory.wilding (AT) eds (DOT) com <mailto:gregory.wilding (AT) eds (DOT) com> >

"Wilding, Gregory" <gregory.wilding (AT) eds (DOT) com> wrote

surrounding the upgrade from version 2.0 to 2.6.

Not really.

Hash joins might cause some grief for badly written applications that
omitted an ORDER BY clause where ordering is in fact important. Hash joins
are often/usually substituted for FSM joins, which used to mask the missing
ORDER BY. Hash joins can be disabled in CBF if you want--and the jury is
still deliberating whether they are always a net win anyway.

Maybe you would also count the risk of some bug regressions. But we haven't
been bothered by those since the latest service pack, which obviously you
should use.

Roy Hann (rhann at rationalcomemrce dot com)
Rational Commerce Ltd.
www.rationalcommerce.com
"Ingres development, tuning, and training experts"

Some new reserved words in Ingres 2.6. There is a script you can run to
check your schema. It can be found in the technotes at the ingres home page
in supportconnect. I've got some scripts for checking source code - let me
know if you're interested.

Rather than upgrading I created a new instance then just moved the data
across.

After moving to 2.6, some of our long running queries improved from 10
minutes down to 30 seconds. Other queries moved from 4 seconds up to 5
minutes. These were related to isam tables and hash and psm joins I think.
To fix some required only restructuring the table or adding an index. Others
required a change in SQL.

Several of our screens broke because there was no order by clause.

Make sure you have copies of customisations from your ingres/files
directory. eg ckptmpl.def

Several parameters needed changing with 2.6. CA support were very helpful in
this area. They looked at our config.dat and protect.dat and made a few
recommendations.

2.6 requires at least Solaris 2.5 I think

Paul

-----Original Message-----
From: Wilding, Gregory [mailto:gregory.wilding (AT) eds (DOT) com]
Sent: Thursday, 17 March 2005 7:05 PM
To: info-ingres (AT) cariboulake (DOT) com
Subject: [Info-ingres] Ingres Upgrade.


We are looking at upgrading our version of Ingres from 2.0 to 2.6 on Solaris
(due to the drop of support). Does anybody know of any issues surrounding
the upgrade from version 2.0 to 2.6.

Thanks

Gregory Wilding
UK North Midlands Solutions Centre
Abney Park
Manchester Road
Cheadle
Cheshire SK8 2PD
Tel +44 (0) 161 495 3488
Fax +44(0) 161 428 5009
<mailto:gregory.wilding (AT) eds (DOT) com <mailto:gregory.wilding (AT) eds (DOT) com> >


_______________________________________________
Info-ingres mailing list
Info-ingres (AT) cariboulake (DOT) com
http://mailman.cariboulake.com/mailm...py/info-ingres