Re: Runaway Informix SQL Processes. Need Help!!

In article <19970906041300.AAA08963@ladder02.news.aol.com>, Paynesys <paynesys@aol.com> writes > > I ran the UNIX vmstat & sar commands and discovered that our > system's CPU idle time was at 0%. I then did a ps -ef and > discovered two processes ( SQL queries via dbaccess ) that > where started weeks ago where eating up CPU time. The users who > started these processes used the interrupt key to halt the queries. > For some reason, the SQL processes that where aborted using > the intrrupt key remained in the queue for weeks. After killing > these processes ( kill -9 ), our CPU idle percentage returned to > normal. > > Can someone please explain to me why SQL processes that are > aborted via the interrupt key continue to hog CPU time? > > > Please email your responses to: > > paynesys@aol.com The interrupt is only send to the dbaccess process. The sqlexec processes ignore them. They will die when they next try to communicate with dbaccess (to send query results to dbaccess) and receive an error. They reason they hog CPU time is that they are probably trying to execute the query and are trying to read every record in a very large table since no indexes are being used. -- David Williams