If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

The reason you are seeing this is is because in the first example you extent sizes are uniform, yet in your second example this would not be true hence the allocation type is defined as system which has a default extent size of 64k

Thats because the tablespace APP_DATA1 is not a uniform extent tablespace, its an auto allocate or SYSTEM Managed LMT. So no matter what for a SYSTEM or Autoallocate LMT the first few extents will be 64k in size.

Look at the ALLOCATION_TYPE column value of dba_tablespaces. You will see that its not uniform allocation but SYSTEM allocated.

HTH

Amar"There is a difference between knowing the path and walking the path."

by default the extent management is local in oracle9i.
but in case when i give default storage and no extent management clause as i gave while creating the tablespace what does it use( local or dictionary)

if i specify default storage clause and extent management local it gives me an error that default storage specifications cannot be specified for locally managed extents.

jovery i do not have access to metalink , hence i couldn't access it. moreover both the examples used the same size hence it is not clear as to why the server selected system for the second example and uniform for the first.

Originally posted by ser by default the extent management is local in oracle9i.
but in case when i give default storage and no extent management clause as i gave while creating the tablespace what does it use( local or dictionary)

LOCAL

if i specify default storage clause and extent management local it gives me an error that default storage specifications cannot be specified for locally managed extents.

Expected normal behavior.

Sanjay G.
Oracle Certified Professional 8i, 9i.

"The degree of normality in a database is inversely proportional to that of its DBA"

Originally posted by ser by default the extent management is local in oracle9i.
but in case when i give default storage and no extent management clause as i gave while creating the tablespace what does it use( local or dictionary)

Remember that when the system tablespace is Locally managed tablespace then all tablespaces created will be locally managed. You are confusing yourself with the Allocation Type. The question should be whether it would be an uniform allocated or system(auto) allocated tablespace. If you do not mention uniform clause while creating the tablespace the tablespace will be System allocated ie the extent management is autoallocate.

In Auto allocate the first few extents size will be 64K then 1M, then 8M and then 64M and so on. But in case of uniform allocation the tablespace will have uniform extents only ie extents of same size.

Originally posted by ser
if i specify default storage clause and extent management local it gives me an error that default storage specifications cannot be specified for locally managed extents.

You don't need to give storage clause, that does not work in Locally Managed Tablespaces, its either uniform extent or system(autoallocate).

See here i have not mentioned uniform extent clause so the extent allocation will always be autoallocate for system_tbs tablespace.

Originally posted by ser
jovery i do not have access to metalink , hence i couldn't access it. moreover both the examples used the same size hence it is not clear as to why the server selected system for the second example and uniform for the first.

The server selected uniform for the first because the INITIAL=NEXT and PCTINCREASE=0 is what a Uniform extent will have ie all extents are uniform. But in the second case you have INITAIL=NEXT and PCTINCREASE=50, here because of the clause PCTINCREASE=50 the extents allocations cannot be uniform. So the only other option left is Autoallocate and server makes it an System(Autoallocate) managed LMT.

Do not use storage clauses as it doesnot work with LMT. It has to be either UNIFORM LMT or SYSTEM MANAGED LMT.

And do not confuse yourself between Dictionary managed and SYSTEM Managed they are two different things.

HTH

Last edited by adewri; 05-30-2003 at 04:12 AM.

Amar"There is a difference between knowing the path and walking the path."