I am reviewing a 10046 trace file and have come across several questions (actually
more like hypothesis that I want to confirm).
- The first user statement executed waits only on SQL*Net to/from client and does not
wait on any db file activity. I presume this means that the data was found in the
buffer cache and did not have to be read on disk.
- The next user statement is preceeded by a recursive query on view$. The user
statement accesses a view, so this recursive query is part of the object resolution
phase of parsing.
- This 3rd user statement has a substantial number of waits on db file activities.
This indicates disk access.
- A subsequent statement has several space management (activity on fet$ and uet$)
activities. The tablespace/file that is passed in as a bind variable are associated
with a 'temp' tablespace. However, the tablespace is set up as dictionary managed.
This indicates that sorting is being done by this operation and that the sort segment
space management is being tracked in the data dictionary.
Thoughts?begin:vcard
n:Fink;Daniel
tel;cell:303.808.3282
tel;work:303.272.3225
x-mozilla-html:TRUE
adr:;;;;;;
version:2.1
email;internet:[EMAIL PROTECTED]
title:DB Services Lead
x-mozilla-cpt:;-4832
fn:Daniel Fink
end:vcard
Received on Thu Jun 26 2003 - 10:06:59 CDT
