dbTalk Databases Forums  

table extents

comp.databases.informix comp.databases.informix


Discuss table extents in the comp.databases.informix forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Rüdiger Mähl
 
Posts: n/a

Default table extents - 09-15-2003 , 08:52 AM






Alarmed by the extent discussion some days ago,
I checked the number of extents of all "my"
tables in all databases. The result was terrifying:
there are a lot of tables with over 20 extents
and even some tables with more than 100 extents.

So, what can I do to get rid of fragmentation?
I know of dbexport and dbimport. How about:
ALTER INDEX <idx> TO CLUSTER
and back again?

Any other smart tricks?

TIA,

Rüdiger

Reply With Quote
  #2  
Old   
Obnoxio The Clown
 
Posts: n/a

Default Re: table extents - 09-15-2003 , 12:37 PM






Rüdiger Mähl wrote:

Quote:
Alarmed by the extent discussion some days ago,
I checked the number of extents of all "my"
tables in all databases. The result was terrifying:
there are a lot of tables with over 20 extents
and even some tables with more than 100 extents.

So, what can I do to get rid of fragmentation?
I know of dbexport and dbimport. How about:
ALTER INDEX <idx> TO CLUSTER
and back again?
ALTER FRAGMENT?

--
"C'est pas parce qu'on n'a rien à dire qu'il faut fermer sa gueule"
- Coluche


Reply With Quote
  #3  
Old   
Rüdiger Mähl
 
Posts: n/a

Default Re: table extents - 09-16-2003 , 03:29 AM



"Rüdiger Mähl" <ruediger.maehl (AT) web (DOT) de> wrote:

Thanks a lot.

Rüdiger

Reply With Quote
  #4  
Old   
Neil Truby
 
Posts: n/a

Default Re: table extents - 09-17-2003 , 10:06 AM



"Gorazd Hribar Rajteriè" <gorazd.hribar (AT) telekom (DOT) si> wrote

Quote:
Use:
ALTER TABLE <table name> INIT IN <dbspace name
you can use the same dbspace, where your table is created originally. The
whole table will be rebuilt and number of extents will be minimized. You
can
use:
ALTER TABLE <table name> MODIFY NEXT SIZE <new number
prior running ALTER FRAGMENT clause to ensure sane values for next extent
sizes. Note that on IDS 7.31 and prior values over 2 GB have no effect (at
least on Sun machines).
Well, on any platform.
"Fixed" in IDS 9.40.
A few other things to bear in mind: if the target dbspace is itself
fragmented (ie lots of small blocks of free space) the ALTER FRAGMENT can
fail through exceeding the maximum number of extents for a tablespace.
Also, on large tables this is best done with database logging off for
performance and for avoidance of long transactions.




Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.