From: "Ivan Boesing" <boesing@geocities.com>
Subject: Re: ORA-01562 message, WHO CAN SOLVE MY PROBLEM?
Date: 1997/08/08
Message-ID: <01bca44b$68979bc0$46013396@Ivan.tre-rs.gov.br>#1/1
References: <01bca35f$da1d38a0$044c12c3@t273862>
Organization: TRE
Newsgroups: comp.databases.oracle,comp.databases.oracle.marketplace,comp.databases.oracle.misc,comp.databases.oracle.server



Hi Jouke,

      This kind of error happens because your rollback segment has been
full. Look, you are inserting 2 millions rows that generate a big volume of
information if you need rollback the transaction. I have 3 tips to you:
    1- Create a higher size rollback segments.
    2- Create a new big (really big) rollback segment and use the SET
TRANSACTION USE ROLLBACK SEGMENT new_rollback; Preferentially, create this
new segment as private (so it is not online every time).
    If any of the 2 above works....
    3- Pray :-)

Kind Regards

Ivan Boesing
boesing@geocities.com


Jouke Wilkens <jouke.wilkens@tip.nl> escreveu no artigo
<01bca35f$da1d38a0$044c12c3@t273862>...
> We use ORACLE vs.7.1.
> 
> 3 jobs were running at the same time:
> 	a.	a job inserting 2 million rows in a table
> 	b.	a direct path SQLLOAD
> 	c.	a large query of 2 tables, resulting in a flat file after a sort.
> 
> In all the 3 jobs was the error "ORA-01562: failed to extend rollback
> segment (id=1)"
> Job a. noticed on the next line "ORA-01650: unable to extend rollback
> segment ROLLBACK2 by 3839 in tablespace ROLLB".
> 
> 1.	Who can explain me what these errors mean?
> 2.	In which situations does this error appear?
> 3.	What are the most likely solutions to this?
> 
> Thank you for your reaction!
> 
> Jouke   Wilkens
> The Netherland.
>   
>