Maybe you could use the ALTER table ALLOCATE EXTENT ( bla bla)
If it succeeds, then do ALTER table DEALLOCATE UNUSED
If it fails, do alert.
Mike
"Chuck" <chuckh_nospam_at_softhome.net> wrote in message
news:Xns9445946ADA16Echuckhsofthomenet_at_130.133.1.4...
> "Howard J. Rogers" <hjr_at_dizwell.com> wrote in
> news:3fcce521$0$20482$afc38c87_at_news.optusnet.com.au:
>
> > If you've got 9i, why do you care about segments extending?
> >
> > If you're using LMT, it's a matter of utter indifference, except in
> > the sense that additional disk space might be required to accommodate
> > all that growth. But if the thing is going to grow anyway, you'll have
> > the space ready to allocate anyway. The sort of close monitoring you
> > describe is exactly what was needed back in the days of dictionary
> > managed tablespaces because extent allocations were expensive affairs,
> > and a source of possible contention. But now they're not, and there
> > are better things to worry about.
> >
> > Not the answer you hoped for, probably (because I don't have such a
> > custom event to hand... but then I wouldn't even want one). So
> > apologies.
> >
> > Regards
> > HJR
> >
> > "Chuck" <chuckh_nospam_at_softhome.net> wrote in message
> > news:Xns94455C169629chuckhsofthomenet_at_130.133.1.4...
> >> Has anyone ever written a custom OEM event they'd be willing to share
> >> that checks the number of times a segment can extend before running
> >> out of space? I don't want to use the prepackaged Tablespace Full or
> >> Chunk Small events as they both fall short of what I want. I size my
> >> extents to give me 3-4 days of growth. I want to alarm when there are
> >> 2 free extents remaining. Chunk small requires the free extents to be
> >> contiguous which isn't always the case and yields plenty of false
> >> alarms. Tablespace full is based on percentages and the threshholds
> >> would constantly need to be tweaked as the tablespace grows. Since my
> >> tablespaces are all LMT's, I'm looking for something that just
> >> divides the total free space available in the tablespace by the next
> >> extent size. It sounds simple but I haven't had time to write
> >> something and integrate it with OEM. I was hoping someone else has
> >> already done it and would be willing to share what they've done.
> >>
> >> Our environment is a 9.2 OMS, with agents ranging from 8.1.7.4 up
> >> through 9.2.
> >> --
> >> Chuck
> >> Remove "_nospam" to reply by email
> >
> >
> >
>
> The databases I'm concerned about are 8i with LMT's. I'm concerned about
> running out of space in a tablespace. It's not about number of extents in
> a segment. I just want to know when I've got about a weeks worth of space
> left so I can add a datafile.
>
> --
> Chuck
> Remove "_nospam" to reply by email
Received on Tue Dec 02 2003 - 20:40:22 CST
