Re: Problem with rollback segment (ORA-01555)

If there is no other activity on your database (other than your single client application), and you've sized all of the rollback segments appropriately, then the problem is in the design of your application.

A design mistake I have seen developers make is "fetch across commits". That is, the app opens a cursor, performs some updates, performs a commit, and then fetches from the (already) open cursor.

I suggest you chec out this article on Steve Adam's site:

http://www.ixora.com.au/tips/admin/ora-1555.htm

<c_joh_at_my-deja.com> wrote in message news:93pvgj$m2g$1_at_nnrp1.deja.com...
> I have a problem with rollback segments that I don't understand. I'm
> running Oracle EE Ver. 8.0.5.1.0 and I have written a client
> application that will insert/update some tables in the database. It all
> works very well except that I now and then get the error message
> "ORA-01555: snapshot too old (rollback segment XX too small)". I have
> currently 5 rollback segments online. They all are quite big, more than
> should be needed for the transactions that occur from the client
> program. The database is in a test environment where there is no other
> users connected.
>
> When I query V$ROLLSTAT I can see that none of the rollbacksegments
> uses more then 2 extents and as the maxextent is set to 1000 there
> should be plenty of room to allocate more extents. The datafile is set
> to autoextend = ON.
>
> If anyone could give me a hint on what to look for I would be most
> grateful.
>
> -Carl
>
>
> Sent via Deja.com
> http://www.deja.com/
>
Received on Sat Jan 13 2001 - 15:47:18 CST