Message-Id: <10507.106527@fatcity.com> From: "Igor Neyman" Date: Wed, 24 May 2000 10:13:19 -0400 Subject: Index organized tables This is a multi-part message in MIME format. ------=_NextPart_000_0198_01BFC568.AEFA8EB0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable My question is - how to reuse space in Index Organized Table (IOT) after = deleting substantial amount of rows. When I deal with regular table, after deleting a lot of rows I rebuild = the indexes in order not to leave gaps in the index blocks, because we = know that this empty space in the indexes will not be reused (unlike, = when it is reused in table blocks after PCTUSED threshold met in the = block). So, what could be done with IOT in order to prevent constant growth, = even after a lot of rows being deleted? Igor Neyman, OCP DBA Perceptron, Inc. (734)414-4627 ineyman@perceptron.com =20 ------=_NextPart_000_0198_01BFC568.AEFA8EB0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
My question is - how to reuse space in Index = Organized Table=20 (IOT) after deleting substantial amount of rows.
When I deal with regular table, after deleting = a lot of=20 rows I rebuild the indexes in order not to leave gaps in the index = blocks,=20 because we know that this empty space in the indexes will not be reused = (unlike,=20 when it is reused in table blocks after PCTUSED threshold met in the=20 block).
So, what could be done with IOT in order to prevent = constant=20 growth, even after a lot of rows being deleted?
 
Igor Neyman, OCP DBA
Perceptron,=20 Inc.
(734)414-4627
ineyman@perceptron.com
&nbs= p;=20