RE: Redo latch contention

Looks like your itrprof id doing the same thing as Millsap's www.hotsos.com (available already or soon)for which they are going to charge $50-100 per upload. Alex Hillman -Original Message- [mailto:[EMAIL PROTECTED]] Sent: Saturday, June 16, 2001 12:26 PM To: Multiple recipients of list

RE: Redo latch contention

Any description of x$trace? In the docs ?. Alex Hillman -Original Message- Sent: Saturday, June 16, 2001 5:35 PM To: Multiple recipients of list ORACLE-L Or with Cary Millsap's hprof/Sparky stuff (hotsos.com). I'm deligthed that guys like you and Cary are writing tools/products that

Re: Redo latch contention

First of all, if you don't see cumulated waits for the 'latch free' event in either v$system_event or v$session_event (for a specific session/job) there is absolutely no need to do anything about these ratios. It's about the only two latches mentioned in the reference books and it's about the

Re: Redo latch contention

Rajesh: I'm a bit confused here. You say that you are going to tune your redo allocation latch contention, but, based on the output presented, you don't have any redo allocation latch contention. The threshold to determine contention is misses/gets = .01 or

Re: Redo latch contention

Mogens, You are right. nothing is a performance problem unless there is a time contention. In general, it's very hard to see time spent in each latch. itrprof SQL Analyzer with waitgroup=(name,P1,P2) can report time spent in each latch. So, you can see time spent in A latch, time spent in B

RE: Redo latch contention

Setting it too high may cause additional content switching. Walking on water and developing software from a specification are easy if both are frozen. Christopher R. Spence Oracle DBA Fuelspot -Original Message- Sent: Saturday, June 16, 2001 4:26 AM To: Multiple recipients of list

RE: Redo latch contention

10:17 AM To: Multiple recipients of list ORACLE-L Subject: Re: Redo latch contention First of all, if you don't see cumulated waits for the 'latch free' event in either v$system_event or v$session_event (for a specific session/job) there is absolutely no need to do anything about

Re: Redo latch contention

Or with Cary Millsap's hprof/Sparky stuff (hotsos.com). I'm deligthed that guys like you and Cary are writing tools/products that harvest the enormous amount of useful stuff available in 10046 level 8/12 trace files. You know what would be really cool? The same stuff is available via x$trace.