Stability of UDB v7 versus v6
HouseOfNo
version 6? I've been sticking to version 5 for a long time, because when I
got in v6 I couldn't even get it to install properly. All the new Java stuff
crashed all over the place, and when I did get it installed none of the
tools worked properly like they did in v5.
Is version 7 any better?
Are binaries compiled under version 5 upwards compatible?
Scott
ana...@my-deja.com
"HouseOfNo" <sc...@skwc.com> wrote:
> Anyone have any comments on whether UDB version 7 is more stable than
> version 6? I've been sticking to version 5 for a long time, because
when I
> got in v6 I couldn't even get it to install properly. All the new Java
stuff
> crashed all over the place, and when I did get it installed none of
the
> tools worked properly like they did in v5.
>
> Is version 7 any better?
I would suggest v6.1 with fixpak5 is quite stable. Though i'm in the
process of migrating all my 6.1 servers to 7.1, i haven't received any
feedback from the application group.
>
> Are binaries compiled under version 5 upwards compatible?
Yes, they are. IBM says it's forward compatible to next 2 versions,
which means you can migrate straight away to 7.1. Moreover, i've also
tested the scenario and it's working fine.
>
> Scott
>
>
Sent via Deja.com http://www.deja.com/
Before you buy.
shind...@my-deja.com
couple of findings/observations regarding DB2 code stability:
1. There is no question that, generally speaking, right out of the box
V6 is better than V5, and that V7 is better than V6. That being said,
however, I would not install V6 without at least FP6, nor V7 without at
least FP2 (due in early Dec.) to be assured of good stability.
The good news here also is that in my own experience it took ten
fixpacks on top of V5 to reach an acceptable level of system stability
(I think I see a good trend here).
2. If you need to upgrade right away and because V7 is still relatively
new, I would recommend that you upgrade to V6 first. It has now 'aged'
enough and reached an acceptable level of stability to be put into a
production environment. You can then upgrade to V7 later on after it
has also 'aged'.
3. Fixpack 6 for V6 is now available and based on my own testing I would
recommend it. Fixpack 5 fixed many things (included in FP6) but it
unfortunately broke some things too. Most notably the parsing of the
double quotes used in keywords like SCHEMALIST in the db2cli.ini file.
This is supposed to be corrected in FP6.
Hope this provides you with some guidance to make your own decision.
Perry Shindle
KPMG Consulting
Harrisburg, PA
p.s. The opinions expressed here are purely my own. Others may have
different experiences/opinions.
In article <b6AO5.97666$P4.26...@news1.rdc1.tn.home.com>,
"HouseOfNo" <sc...@skwc.com> wrote:
> Anyone have any comments on whether UDB version 7 is more stable than
> version 6? I've been sticking to version 5 for a long time, because
when I
> got in v6 I couldn't even get it to install properly. All the new Java
stuff
> crashed all over the place, and when I did get it installed none of
the
> tools worked properly like they did in v5.
>
> Is version 7 any better?
>
> Are binaries compiled under version 5 upwards compatible?
>
F.Hauptlorenz
I had run V6.1 and V7.1 (now on Fix 1) on Linux Server and V7 is much
more stable than V6.1 ever was... (especially on low fixpaks).
Cheers,
Frank
Jean-Marc BLAISE
>Anyone have any comments on whether UDB version 7 is more stable than
>version 6? I've been sticking to version 5 for a long time, because when I
>got in v6 I couldn't even get it to install properly. All the new Java
stuff
>crashed all over the place, and when I did get it installed none of the
>tools worked properly like they did in v5.
>
>Is version 7 any better?
>
>Are binaries compiled under version 5 upwards compatible?
>
>Scott
>
I also find DB2 V7.1 with FP1 more stable than v6.1 was at the beginning.
I would suggest to wait for v7.1, FP2 - delivery date Dec 7 - and take a
look on all functionnalities you could use or that have been improves; for
example dropping JAVA stored proc does not make you stop the instance, full
backup archives the current active log file ...
Hope this helps,
Jean-Marc