Re: TBLSPACE table extents. -Reply

You don't have to export. You can cluster the index to consolidate the file or you can use the alter fragment syntax to fool the rdbms into re-writing the file. This happens because the sizing for the table was not correct. You don't have to make extent sizes huge; you just need to make them as accurate as possible. rgds -- -- Peter Tashkoff NZ Kiwifruit Project Consultant/DBA Marketing Board. Standard Disclaimers apply This posting may not be used by any commercial organisation to vilify another. >>> <dstafford@krames.com> 18/June/1996 02:03pm >>> > paul.daniells@lovellwhitedurrant.com (Paul Daniels) writes: > We are using OnLine 7.12 on HP900's running HP-UX 10.01 > > On each system the TBLSPACE tables have developed many extents > and been fragmented throughout the dbspace(s). I don't remember this > happening the same on version 5 that we ran previously. > > The only method for recovery has been dbexport, re-initialise and then > rebuild (dbimport). > > Does anybody have an alternative suggestion or ideas on how to > prevent it happening ? > > TIA > > Paul > > --------------------------------------------------------------------------------- > Paul Daniells paul.daniels@lovellwhitedurrant.com > Lovell White Durrant > London, England > > >>>> I try to estimate the growth of the table over some period of time, say, 3 months, and create the table with the appropriate size first extent. Then, I calculate what the growth will be in each month, and define that as the next extent size. The only way to truly avoid this is to make the first extent HUGE. But who has enough disk space for that? I have a formula for calculating the first extent size. If you want it, please write me back. (I'm at home now at don't have it handy) P.S. Deleted rows are reused, so I've heard.