Re: stange rollback behavior

Too an extent, this is just guess work, but I'm not sure it is the export session that needs to use a large rollback segment. I'd explore what other work is going on in the database at the time of the export and adjust those jobs, scripts, etc. to use your large rollback segment.  I'm thinking a more reliable way, though would be to not change any code, but instead, just make all rollback segments large enough to handle your longest transaction. Sometimes easier said than done with resource limitations.

>>> John.Hatzistavrou.sema_at_mail.tellas.gr 05/08/03 04:01AM >>>
Dear All,

In the past I had problem taking a consistent export from a very active database. At that time I had ORA-1555 error. I though if I created a big rollback and force the export use it I would resolve the problem.
Thus I created an after logon schema trigger on the user I was specifying on the export command .
I have tested it and for a number of days thinks were going as expected.
Yesterday the export failed with ORA-1555 again but on different rollback than the one I have set in the after logon trigger. May someone of you explain this?

Kind Regards,

Hatzistavrou Yannis
Database Administrator

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Darrell Landrum
  INET: dlandrum_at_zalecorp.com

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).