| intial extents question? [message #132643] |
Mon, 15 August 2005 08:13  |
confident
Messages: 28
Registered: March 2005
|
Junior Member |
|
|
My user schema is LMT tablespace with uniform size of 160k and space segments is manual.... i created the tables and unique index on that tablespace,
with out specifying the storage parameter, it's default takes inital extent and next extent is 160k, when i created the b-tree index on that tablespace without specify the storage parameters, its index shows inital extent is 32 K....
why its take 32k rather than 160k..?
one of more thing, these schema contains only materialized views table's and refresh with sysdate +1, only select operation is performed, and user data is around 600mb and when i check with blockid calculation in dba_extents, its occupys 1500mb due to fragementation...
my question when materialized view perform complete refresh, fragementation issue shouldn' occur, due to compelte refresh performs truncating the table and while truncating deallocate of extents will take place and after that insertion take place, at this time fragementation should n't occur....? if iam not wrong
is it possible, can we defrag when the tables are accessing? pls suggest me....
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
