Re: Rollback

To assign a (big) rollback segment to a session you have to issue a "alter session" command before(!!) any transaction occurs. You can also do this with a dbms_-package command. Can't remember the name right now.
If large rollback segments are no solution you may want to look for the unrecoverable option of the create table command. Thus you should be able to create a temporary table with updated data. Then drop the old table and create it in the same way. But make sure that you understand the problems this way can cause. You may suffer loss of data unless you do a cold backup.

Greetinx
Meinolf

On Tue, 17 Mar 1998 15:19:52 +0000, Raffaele Sena <raff_at_aromatic.com> wrote:

>Jaap W. van Dijk wrote:
>>
>> "Joseph Manuel Camilleri" <jm_c_at_bov.com>
 ...
>> > clause). I keep getting problems with the size of the rollback segment.
>> >
>> > Is there someway I can turn off the rollback facility for this update only?
>> >
>
>Jaap W. van Dijk wrote:
>> >
>> No. you can't. Rollback information is not only kept for your update,
>> but also for read consistency for other sessions: while
>> you are updating, Oracle shows other session the unchanged records by
>> retrieving the old values from the rollbacksegments.
>
>What you can do is increase the rollback segments size
>and extents. If you run the Oracle Storage Manager
>you can manupulate them to do almost everything you
>want. You can create a big rollback segment (also give
>them enough number of extents and reasonable extent size).
>
>There is also an SQL command to associate a rollback
>segment to your transaction, but I really don't remember
>the name. In that way you can have a single big rollback
>segment and make sure your transaction use that one and
>not the current one.
>
>Hope this help
>
> Raffaele
Received on Mon Mar 30 1998 - 00:00:00 CST