Home » RDBMS Server » Server Administration » Storage (next extent)
Storage (next extent) [message #216752] Tue, 30 January 2007 04:38 Go to next message
chara
Messages: 81
Registered: April 2005
Location: th
Member
Dear all,

I tried to create a new table as the following :

CREATE TABLE test (
t1 CHAR(2)
)
TABLESPACE TBSTEST
PCTUSED 40
PCTFREE 10
INITRANS 1
MAXTRANS 255
STORAGE (
INITIAL 10M
NEXT 10M
MINEXTENTS 1
MAXEXTENTS 2147483645
PCTINCREASE 0
FREELISTS 1
FREELIST GROUPS 1
BUFFER_POOL DEFAULT
)
LOGGING
NOCACHE
NOPARALLEL;

After ,I tried to check initial_extent and next_extent as the following :
sql>select initial_extent,next_extent from user_tables where table_name ='TEST'
INITIAL_EXTENT NEXT_EXTENT
-------------- -----------
10485760 524288

sql>select tablespace_name, extent_management, allocation_type, segment_space_management
from dba_tablespaces
where tablespace_name = 'TBSDATA'
;
TABLESPACE_NAME EXTENT_MAN ALLOCATIO SEGMEN
------------------------------ ---------- --------- ------
TBSTEST LOCAL UNIFORM MANUAL


Why i got the value of "NEXT_EXTENT" = 524288 byte?
My db version is 9.2.0.8 .

Thanks for advance !

Chara

Re: Storage (next extent) [message #216792 is a reply to message #216752] Tue, 30 January 2007 07:32 Go to previous message
smartin
Messages: 1803
Registered: March 2005
Location: Jacksonville, Florida
Senior Member
Read carefully in the docs regarding locally managed tablespaces. Especially those with a uniform extent size. When you create a locally managed with uniform extent size, you specify a size, and all extents will be that size.

It is easier if you reduce your usage of storage params when moving to locally managed.
Previous Topic: tns and ora errors
Next Topic: 10g Express Enable bit-mapped indexes
Goto Forum:
  


Current Time: Thu Dec 08 08:29:44 CST 2016

Total time taken to generate the page: 0.23462 seconds