Arup and Jacques:
thanks for your help.
The command we are executing is alter table exchange
partition ... with table .. include indexes. We have
also a PK on each of the tables (local index on a
partitioned table). Go global indices. We have tried
the same command with novalidate and the
Are you using UPDATE GLOBAL INDEXES clause in the ALTER TABLE EXCHANGE
PARTITION? This causes significant IO.
Try tracing the session using 10046 trace and see exactly what statements
are being issued.
ALTER SESSION SET EVENTS '10046 trace name context forever, level 8';
ALTER TABLE EXCHANGE
Did you say alter table exchange partition ... validate or alter table exchange
partition ... novalidate? If you say novalidate then Oracle will sort the exchange
table to make sure that you are not creating duplicate rows for the PK constraint.
There is a Metalink note on that.
Does the table
Gene,
I doubt the procedures followed for 9.2 are the same as 8.1; Partition
exchange does not move any data, merely resets the pointers inside the data
dictionary; so it should not take more than 1 second as you saw earlier.
Check if you were doing an ALTER TABLE TAB1 EXCHANGE PARTITION P1 WITH