Message-Id: <10508.106777@fatcity.com> From: Colin.Shaw@phs.com Date: Thu, 25 May 2000 13:46:01 -0700 Subject: RE: Index organized tables This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01BFC68A.3CAEAC10 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Igor: ...empty space in the indexes will not be reused... Not true - if you re-insert the same index values, they will go to the "old" index nodes. Remember it's a sorted index - data *must* go in the correct place. Colin. -----Original Message----- From: Igor Neyman [mailto:ineyman@perceptron.com] Sent: Wednesday, May 24, 2000 8:19 AM To: Multiple recipients of list ORACLE-L Subject: Index organized tables 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 ------_=_NextPart_001_01BFC68A.3CAEAC10 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 7bit
Igor:
 
...empty space in the indexes will not be reused...
 
Not true - if you re-insert the same index values, they will go to the "old" index nodes.  Remember it's a sorted index - data *must* go in the correct place.
 
Colin.
-----Original Message-----
From: Igor Neyman [mailto:ineyman@perceptron.com]
Sent: Wednesday, May 24, 2000 8:19 AM
To: Multiple recipients of list ORACLE-L
Subject: Index organized tables

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