Rollback segment question?

Hi all,

Is there a way not to use roolback segement in a transaction?

What we are doing in our application (using Proc*C and OCI) are create a table, select data from some table, manipulate the data and insert the manipulated data into the just created table but because the data is quit big and we often running into the problems of out of space or cannot allocate extent (max. extents reached) in the rollback segment.

What we have done are:

1. Create large rollback segments
2. Committed every 50 (let say) insertions.

The problem with #1 is we need a lot of space. The problem with #2 is we cannot control the data consistency since we put a lock on the other table, the table that we select data from and once the transaction is committed, the lock is gone.

Is there other better way to handle this. I think this kind of operations are very common. It is just something like INSERT INTO ... SELECT .....

Your help is very much appreciated.

Tung Nguyen Received on Fri Dec 08 1995 - 00:00:00 CET