Re: Problem with Rollback segment

The problem is with another transaction the ran concurrently with your query. Your query needed the other transaction's rollback segment to construct a read-consistent view of the data as of the time when your query began. You need to identify what other transaction(s) are concurrently updating what you're querying and assign them to larger rollback segments, not the query itself. Or you need to schedule your query to run at a different time.

On 25 Mar 1998 16:28:20 -0600, dann_at_sky.net (Dan Norris) wrote:

>using "set transaction" for a query has no effect (that I know of).
>select's are not transactions. If you are doing updates, inserts, or
>deletes that are part of a large transaction, then your "set transaction"
>statement will have impact.
>
>Dan
>
>dtang_at_minn.net writes:
>
>>Hi:
 

>>I got a very serious problem. I have a huge query to update a large
>>table. It runs several hours, then dead with oraerr 01555. Snapshot
>>too old, the rollback segment R05 is too samll.
>>Then I creat a large rollbak segment O08, then
>> use set Transaction use rollback segment r08, and run that query
>>again.
>>After hours , it died again with same error 01555, but it still say:
>>"roll segment Ror (or whatever other than R08) is too small".
 

>>I don't understand why the engine doesn't usr rollback segment I
>>specified. Does anyone has any idea.
 

>>If anyone has experience running a large query, could you help me put
>>on this one. My email address is dtang_at_minn.net
>
>
>>Thanks ahead
>
>
>>Dong

--
Chuck Hamilton
chuckh_at_dvol.com

If at first you don't succeed, sky diving isn't for you.