Re: Opinions for this storage parameters.

Good Evening Norman,

This is a classic example of why others suggested I was too idealistic and pedantic about pushing this. The obvious answer to your issue is not to compress extents (being the default doesn't help). But I agree, it wasn't always easy to control.

I guess the harder you try to get to Shangri-La, the closer you get (but by setting PCTINCREASE to 1 you're moving in the wrong direction :)

I'm with you on LMT.

PS. Go Lleyton Hewitt in the tennis !!

Regards

Richard
"Norman Dunbar" <Norman.Dunbar_at_lfs.co.uk> wrote in message news:E2F6A70FE45242488C865C3BC1245DA702505E97_at_lnewton.leeds.lfs.co.uk...
> Morning Richard,
>
> you wrote :
>
> >> Now, EVERY object that lives in the tablespace has EXACTLY the same
> sized
> >> extents.
>
> True, but then some silly b*gg*r goes and exports a table (or all of
> them) using the default COMPRESS=Y, drops them from the above tablespace
> and re-imports them. Not to get any perceived performance benefits of
> having all data in one extent (I know there are none !) but just because
> they wanted to. Now, your nicely set up tablespace has gone to hell and
> back.
>
> The number of problems I'v had with this sort of thing, and being sent
> exports of databases where this has gone on has caused me no end of
> problems.
>
> I love LMT with uniform sizes - what an absolute relief.
>
> Cheers,
> Norman.
>
> PS. I'm just having a bit of a rant because I've hit the above problem
> and the bleeding import won't work because the constraints are being
> created with stupid values which exceed the available space in the
> tablespace etc etc.
> :o(
>
>
> -------------------------------------
> Norman Dunbar
> Database/Unix administrator
> Lynx Financial Systems Ltd.
> mailto:Norman.Dunbar_at_LFS.co.uk
> Tel: 0113 289 6265
> Fax: 0113 289 3146
> URL: http://www.Lynx-FS.com
> -------------------------------------
>
Received on Wed Jul 03 2002 - 07:48:43 CDT