Hi

I am going to try SLIMDAVE's recommendation to use copy command. I looked into the SQL*Plus document about this command. It seems to suite my requirement.

Well, My (ERP)application creates the tables with company number attached to the tables' names. There is nothing much I can do about it.

As STMONTGO pointed out the regular/frequent commits may affect performance. But I don't see any other choice.

JMODIC, Well, I was wrong when I said redolog tablespace. I meant rollback tablespace. We do switch off archive logging while doing this copy. So there is no question of archive logs filling up the disk space. The situation here is the rollback tablespace fills up and it really hangs (at the application side) and when I see the alertlog there is a message/error "

Mon Oct 07 10:12:03 2002
ORA-1650: unable to extend rollback segment RB1 by 64 in tablespace ROLLBACK_DATA

Failure to extend rollback segment 2 because of 1650 condition
FULL status of rollback segment 2 set.

So I killed the copy process.

Jurij, I am not really into Skydiving sport....

I won't be using the ORDERBY in copy...select statement right now. I would introduce it once the copy is functional.

Thanks for your responses....

-Football