Re: Index organised table

On 2 Dec 2005 07:29:07 -0800, "Pradeep" <agarwalp_at_eeism.com> wrote:

>I am reading tom kytes Expert ....
>
>1. I am unable to understand the statement
> "with IOT logical I/O would be the same, the physical I/O would be
>less"
>May be because i don't know how data is physically stored with IOT.
records are physically stored in order of the pk of the table
>
>Suppose if I have a Index organised table with colum "ename", then is
>it that all the blocks containing enames begining with "A" will be
>together followed by the very next block with next sequence of enames,
>or is it sorted within the block ??
>

If ename is the pk, they are stored in order of ename
>2. It also states that in IOT data must go where it belongs. now
>suppose if in the above table if i have a block with all rows with
>enames beginning with "A" except one which begins with "B". Now if i
>add a row with ename beginning with "A" then what happens ?
>
>
>Thanks

Indexes are ordinary b-tree indexes. If the record needs to be in that bucket and the bucket is full, you'll get bucket split.

--
Sybrand Bakker, Senior Oracle DBA