× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Something doesn't sound right. Why did they reload all their data for a
V5R3 to V5R4 upgrade? What else did they do, as this doesn't sound like a
straight upgrade. Why and who told them they should reload their system?
Change the machine? Did they restore to a new machine, that already had QSYS
installed and you didn't take all your objects from the old machine in QSYS?

Did you do a STROBJCVN on all the SQLPGMs after the upgrade or are you
relying on first touch?

Pete

Pete Massiello
iTech Solutions
www.itechsol.com

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mark S. Waterbury
Sent: Friday, August 22, 2008 11:51 AM
To: MIDRANGE-L@xxxxxxxxxxxx
Subject: unexplained performance problems with SQL after upgrading to V5R4

Hi, all:

One of our large customers upgraded their production system from V5R3 to
V5R4 last week-end.

They re-initialized all of their DASD and re-loaded all of their data
from back-up tapes, during or after the upgrade to V5R4. They say access
paths were saved (and restored), so they are not seeing index rebuilds
going on.

The problem is, for their applications that use embedded SQL, they are
seeing much slower performance, versus what they saw a week ago, when
they were still running on V5R3.

Does anyone have any ideas about where to look, or what to look for?
Perhaps some values changed in QAQQINI?

Thanks in advance for any suggestions, hints or tips.

Regards,

Mark S. Waterbury


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.