|
I do not know whether this happens on your system but there was one issue I saw in the past. When there is a very long series of updates without commit (very long transaction) and then the transaction is aborted, system has to roll back all the changes. This could be a lot of work. The solution is not to do oversized transactions and insert commits every now and then. Alexei expressing only my personal opinion "Paul Holm" <pholm@xxxxxxxxxxxxxxxxx> Sent by: java400-l-bounces@xxxxxxxxxxxx 05/04/2006 09:46 AM Please respond to Java Programming on and around the iSeries / AS400 <java400-l@xxxxxxxxxxxx> To <java400-l@xxxxxxxxxxxx> cc Subject JDBC Job CPU Spike Issue on OS400 I got a situation where a large long running JDBC SQL is run from Window to iSeries. It can take 20 minutes to complete. If the end user kills the session, the OS400 QZDASOINIT job CPU spikes crippling the system. Someone on the list noted a similar issue but solution was mentioned. Anyone seen this issue and have insight? Thanks, Paul Holm Senior Web Architect PlanetJ Corp. Phone: 760-432-0600, Cell: 760-415-8830 WOW, Web Applications In Under 5 Minutes HYPERLINK "http://www.gotWebData.net" \nhttp://www.gotWebData.net
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.