Re: log file sequential read - arguments P3
- From: Alexander Gorbachev <gorbyx@xxxxxxxxx>
- To: cary.millsap@xxxxxxxxxx
- Date: Wed, 1 Dec 2004 22:00:07 +0100
Carry,
I think we can do it with tusc on HP-UX. Or even easier... I just got
an idea that knowing size of my redo logs I can check what is the
biggest value for P2, which is the offset. I'll check it tomorrow.
Thanks,
Alex
On Wed, 1 Dec 2004 08:17:52 -0600, Cary Millsap <cary.millsap@xxxxxxxxxx> wrote:
> Alex,
>
> One way to find out for certain is to truss (strace, ktrace, tusc,
> whatever...) an Oracle kernel that logs time to the event--on a test =
> system.
> In the truss output, you'll be able to see the exact size of the read =
> calls.
>
> Sometimes, even when the manual appears to document something =
> completely,
> you find that it's possible to understand things a little more =
> thoroughly
> than the even the staff who wrote the manual.
>
> Cary Millsap
> Hotsos Enterprises, Ltd.
> http://www.hotsos.com
> * Nullius in verba *
>
> Upcoming events:
> - Performance Diagnosis 101: 1/4 Calgary
> - SQL Optimization 101: 12/13 Atlanta
> - Hotsos Symposium 2005: March 6-10 Dallas
> - Visit www.hotsos.com for schedule details...
>
>
>
>
> -----Original Message-----
> From: oracle-l-bounce@xxxxxxxxxxxxx =
> [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
> On Behalf Of Alexandre Gorbatchev
> Sent: Wednesday, December 01, 2004 7:52 AM
> To: Oracle-L@xxxxxxxxxxxxx
> Subject: log file sequential read - arguments P3
>
> Hi list.
> Does anybody know whether P2/P3 arguments for "log file sequential read"
> wait event are in database blocks or in log blocks?
> The manual is not clear but it seems to mean database block size. =
> However,=20
> I believe that it gotta be log block size. I couldn't find anything =
> useful=20
>
>
> on Metalink either.
>
> Thanks,
> Alex
>
> --
> //www.freelists.org/webpage/oracle-l
>
> --
> //www.freelists.org/webpage/oracle-l
>
--
Best regards,
Alex Gorbachev
--
//www.freelists.org/webpage/oracle-l
Other related posts:
