RE: Tuning methodology (was T3's) and use of NetApp's

2002-08-19 Thread Cary Millsap
Thank you, Anjo. Cary Millsap Hotsos Enterprises, Ltd. http://www.hotsos.com Upcoming events: - Hotsos Clinic, Oct 1-3 San Francisco, Oct 15-17 Dallas, Dec 9-11 Honolulu - 2003 Hotsos Symposium on OracleR System Performance, Feb 9-12 Dallas - Next event: Miracle Database Forum, Sep 20-22 Middel

Re: Tuning methodology (was T3's) and use of NetApp's

2002-08-19 Thread Anjo Kolk
On the total_timeouts column: This column has the same meaning for all events (how can it be different?). There are basically two kinds of events: 1) That specificies a timeout value for the wait and can be posted (not needed though) if (posted = wait(max_wait_time)) {

RE: Tuning methodology (was T3's) and use of NetApp's

2002-08-18 Thread Cary Millsap
Mladen, Read http://www.hotsos.com/dnloads/1.Holt2000.02.01-Backwards.pdf (by Jeff Holt) for complete details about the difference between Oracle's "scattered" and "sequential" reads. Read http://www.ixora.com.au/tips/tuning/redo_latches.htm (by Steve Adams) for details on the redo latch questio

Re: Tuning methodology (was T3's) and use of NetApp's

2002-08-18 Thread Mladen Gogala
On 2002.08.18 23:48 Cary Millsap wrote: > > > > 4. 'db file sequential read' does *not* typically indicate a > > full-table scan, because 'db file sequential read' events, since > > Oracle8.0 are almost always single-block read calls (before that, the > > event could indicate multi-blocks rea

RE: Tuning methodology (was T3's) and use of NetApp's

2002-08-18 Thread Cary Millsap
> > 4. 'db file sequential read' does *not* typically indicate a > full-table scan, because 'db file sequential read' events, since > Oracle8.0 are almost always single-block read calls (before that, the > event could indicate multi-blocks reads of sort segment blocks into a > PGA). [DM] Doe