Re: TBLSPACE table extents.
Delete row are not REUSED!!! You have to ALTER table: Best ALTER index to
CLUSTER or UNLOAD(TBUNLOAD)/LOAD(TBLOAD). I'v find if you have an existing
DB and have been keep stats on growth estimates work out GOOD!!! But
that's an IF!!!
-------------------------------------------------------------------------
Cheryl Kendricks
Internet:cherylk@prod1.jcdc.doleta.gov OR cherylk@gwysmtp.jcdc.doleta.gov
DTSI, Inc.
Database Administrator - DOL Job Corps San Marcos, Texas
------------------------------------------------------------------------
On 18 Jun 1996 dstafford@krames.com wrote:
} > 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.
}