Re: What to keep in ASM?

Fairlie: Thanks for the advice, I've added his book to my list. Aside from my being off in the "hot-block" regard, I'm getting the vibe that you think my situation is unfit for ASM. My SA has dealt with ASM as well in another shop, and he's been the main push in this arena. I'm definitely all ears as to what you might have on your mind about it. Or was it just a test to see if I was getting into it for the right reasons? Basically right now, as I said, we're prepping to do the dev migration, and then have 4 months to get things working. That should be plenty of time to see if ASM will pay dividends, or be an albatross. If it doesn't work out, we can always fall back on normal filesystem files as we're doing now.

Alex G: I'll go over your questions with my SA and report back in the morning (22:45 here). I may even provide a fancy drawing he did on my whiteboard last week. It shows his inner artist. In the end the ASM was going to be striped across the LUNs. I'll see what he can share about the design so far.

Don.

On 2/26/07, fairlie rego <fairlie_r_at_yahoo.com> wrote:
> Hi Don,
>
> It is precisely for this reason that I asked for an explanation as to why
> you think that the load balancing of ASM is a big win.
> Perhaps you should read Gopal's 10G RAC handbook
>
> Regards
> Fairlie
>
> K Gopalakrishnan <kaygopal_at_gmail.com> wrote:
> Don,
>
> It is slightly incorrect. ASM does not work at block level. It works
> at extent level or allocation unit level (1MB most cases) and
> hotblocks exist in ASM too. You may have to tweak the block level
> parameters to avoid hotblocks.. You may want to use X$KSLHOT to nail
> down them.
>
>
> On 2/26/07, Don Seiler wrote:
> > My understanding is that ASM will also shift data around to avoid the
> > "hot block" scenario, avoiding I/O contention. It wasn't explicitly
> > stated in the passage I pasted, hopefully my understanding is correct.
> >
> > Don.
> >
> > On 2/26/07, Alexander Fatkulin wrote:
> > > > Am I giving this feature too much credit?
> > >
> > > ASM spread extents in proportion to the disk size regardless of the
> > > speed and workload characteristics of the underlying hardware (at
> > > least I never saw the opposite).
> > >
>
>
> --
> Best Regards,
> K Gopalakrishnan
> Co-Author: Oracle Wait Interface, Oracle Press 2004
> http://www.amazon.com/exec/obidos/tg/detail/-/007222729X/
>
> Author: Oracle Database 10g RAC Handbook, Oracle Press 2006
> http://www.amazon.com/gp/product/007146509X/
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>
>
>
>
>
>
>
>
> Fairlie Rego
> Senior Oracle Consultant
> http://www.linkedin.com/in/fairlierego
>
> http://el-caro.blogspot.com/
> M: +61 402 792 405
>
>
> ________________________________
> Never miss an email again!
> Yahoo! Toolbar alerts you the instant new Mail arrives. Check it out.
>
>

-- 
Don Seiler
http://seilerwerks.blogspot.com
--
http://www.freelists.org/webpage/oracle-l