× 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.



Depending if your OS version and your i Series Nav version are more recent, you could check the SQL Cache. Expand Databases, then (I think, doing this from memory) right click your database (typically the machine name) and you should see SQL Cache somewhere. Once into it, you can select statements in the cache by time, and/or file, most expensive, most frequent and a whole host of other things. You can see the SQL statement executed and the access plan.

If you have this ability and can do it right after a problem occurs, then it might show you what was going on.

Now it might be limited to only SQE executed statement and I suppose ODBC might push you towards CQE. But it is a quick way to get info and stuff tends to stay in the cache for a longish time, though I believe it is totally cleared by an IPL.

Sam

On 2/23/2012 2:31 PM, Mike Cunningham wrote:
We have an application running on a Linux server making a database connect via ODBC to DB2 on our iSeries. On some occasions CPU use on the iSeries goes sky high on the QZDASOINIT jobs that service the ODBC connection. This application has some components that were developed as DB2 stored procedures, all written in SQL (no high level RPG stored procedures). Looking at the jobs does not reveal much. We have hundreds of users on this system and the high CPU use is not consistent. We suspect that it might be one of the stored procedures that might be doing this but don't know which one. Is there any way to log every request coming in from an ODBC connection so the next time it happens we can see what was being run around the time of high CPU? We have dumped the DB2 database transaction journal records and they do not show high numbers during the busy time which makes me think it is either a loop in the code in a procedure doing calculations or is an index being built on the fly. Howe
ver index advisor does not show any long running indexing going on.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.