simply spent 5 minutes redo my test and you knows.
--build tablespace a with blocksize 8k, 101m.
in oracle 9i+ this statement build a autoallocate tablespace.
Sybrand Bakker wrote:
> On 31 Jul 2006 13:29:10 -0700, "Zhu Chao" <zhuchao_at_gmail.com> wrote:
>
> >I was wrong about the max-extent, but right on next_extent;
> >not much usage to dig that detail, but it is that;
> >
> >--build tablespace a with blocksize 8k, 101m.
> >create table a as select * from dual;
> >create table b as select * from dual;
> >for i in 1..10 loop execute immediate 'alter table a, b allocate
> >extent';
> >while true loop execute immediate alter table a allocate extent;
> >...then it fails when run out of space;
> >
> >now I drop table b, there is free space big enough for next_extent a
> >need, it is 5177k. next_extent for a is 4m. but it fails.
>
> Actually you are altering the rules, because you don't disclose the
> properties of the affected tablespace. Who can tell it isn't a DMT or
> an uniformly managed LMT.
> Your little experiment is not to be trusted.
>
> Also there seems to be something wrong with your hands or your eyes,
> or even both,as you stick to the stupid TOP-POSTING!!!!!
>
> --
> Sybrand Bakker, Senior Oracle DBA
Received on Mon Jul 31 2006 - 20:04:11 CDT
