|
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. However index
advisor does not show any long running indexing going on.
As an Amazon Associate we earn from qualifying purchases.
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.