It IS block cleanout.
Try a select count(*) from table
before creating the index.
--
Jonathan Lewis
Yet another Oracle-related web site: http://www.jlcomp.demon.co.uk
Adam Roze wrote in message <38C7A1BC.748D3882_at_royalpbk.com>...
>Disklayout is:
>temp, system, rbs - disk1
>redo logs - disk2
>users - disk3
>big table - disk4
>ind - disk5
>ind2 - disk6
>ind3 - disk7
>
>Disk array monitor + v$filestat shows that oracle reads & writes to the
>datafile that contains the big table.
>All this happens during import of the user - owner of this table.
>Yesterday I divided import process into 3 steps :
> 1) import with indexfile=.... to get file with definition of the
indexes
> 2) import the tables only - indexes=n in the parfile
> 3) create indexes from the file from step 1
>I did not change anything compared to the import in one step, the whole
process
>was even longer.
>Today I dropped the index on the big table and recreated it from sqlplus
and
>this time oracle made no write to disk4.
Received on Fri Mar 10 2000 - 00:00:00 CST
