Re: Problem Creating Table

"Jiliang Chiu" <jchiu_at_gnncast.net> wrote in message news:qP8F4.6047$Tk.16372_at_news1.atl...
> Locally managed tablespaces.
>
> check extent_management of the tablespaces
>
> Hth
>
>
> "Louis" <frolio_at_videoshare.com> wrote in message
> news:8bdkfa$sir$1_at_bob.news.rcn.net...
> > Greetings All, I have this strange event taking place when I create a
 table
> > in my Oracle 8.1.5/Solaris 2.7 database. Here is the script:
> >
> > CREATE TABLE videoshare.tbCountry
> > (
> > siCountryId NUMBER(5) NOT NULL,
> > vcName VARCHAR2(100) NOT NULL,
> > vcAbbrev1 VARCHAR2(10) NULL,
> > vcAbbrev2 VARCHAR2(10) NULL,
> > tiActive NUMBER(1) DEFAULT 1 NULL
> >
> > )
> > PCTFREE 5 PCTUSED 60
> > STORAGE(INITIAL 100K NEXT 100K PCTINCREASE 0)
> > TABLESPACE USERPROD;
> >
> > GRANT SELECT, INSERT, UPDATE ON videoshare.tbCountry TO WebUser;
> >
> >
> > After this table is successfully built the "NEXT" clause always comes
> > up as 1024K and not 100K? I checked this in schema manager as well
> > as its entry in dba_tables? The tables space in which this table space
> > resides is set for "uniform allocation" with 1024k extents. The
 datafile
 in
> > which this table space resides is set to an initial value of 10240 K and
> > it is set to autoextend at 4096K at a time.
> >
> > Any help would be greatly appreciated.
> >
> > Louis
> > frolio_at_videoshare.com
> >

Has 'minimum extent' been specified for the tablespace? -if so, it doesn't matter what you specify at segment level, the extent sizes will always be rounded up to whole multiples of the minimum extent.

You don't say what the size of the initial extent is after table creation, though. So it is difficult to know for sure.

(And, incidentally, don't confuse 'minimum extent' with 'minextents')

Regards
HJR
> >
>
>
Received on Sat Apr 01 2000 - 00:00:00 CST