Direct path writes can be done by a shadow process (user session) so per sql you can have disk_writes. For example, create table as .. or insert /*+APPEND*/.. Christo Kutrovsky Senior Database/System Administrator The Pythian Group On 12/15/05, Allen, Brandon <Brandon.Allen@xxxxxxxxxxx> wrote: > Anybody have a good method for tracking top SQL by 'db block changes'? It > seems this statistic is only tracked by session and instance, but not by SQL > statement. The 'disk_reads' are tracked in v$sql and although it wouldn't > make sense to track 'disk_writes' (since physical writes are performed in > the background as needed by DBWR, not as a direct result of any particular > SQL statement), it seems like it would make sense to track 'db block > changes' by SQL, doesn't it? I've got heavy writes occurring on a RAID 5 > system and it's killing performance, but I'm having trouble identifying the > offending SQL. Any ideas? > > Thanks, > Brandon > > 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. -- Christo Kutrovsky Senior Database/System Administrator The Pythian Group -- //www.freelists.org/webpage/oracle-l