RE: v$sql 'db block changes'

If only it were that easy. The problem here is that the application uses connection pooling, so there is no single session responsible for the heavy updates - it bounces around amongst 40 different sessions. The top statements in v$sql in terms of cpu, elapsed_time, buffer_gets and disk_reads are all SELECT statements, so I know they're not causing the write activity.

Thanks,
Brandon

-----Original Message-----

From: Ethan Post [mailto:post.ethan_at_gmail.com] Sent: Thursday, December 15, 2005 12:37 PM To: Allen, Brandon
Cc: Christo Kutrovsky; oracle-l_at_freelists.org Subject: Re: v$sql 'db block changes'

I don't disagree that the info could be useful, but since this is a problem that is likely occurring pretty regularly all you would need to do is get the information from v$sesstat and take a peek at the SQL the top writer sessions are issuing.

Privileged/Confidential Information may be contained in this message or attachments hereto. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of this company shall be understood as neither given nor endorsed by it.

--

http://www.freelists.org/webpage/oracle-l Received on Thu Dec 15 2005 - 13:45:10 CST