The only correct resolution to this is to ensure that DML transactions referencing the tables being backed up, are not run at the same time. Bringing the big rollback segment online wont buy you anything. You could delay the inevitable by removing the optimal clauses if set.
Raj
Erik Williams
<ewilliams@br To: Multiple recipients of list ORACLE-L
<[EMAIL PROTECTED]>
ownco.com> cc:
Sent by: Subject: Specify Rollback for an Export
root@fatcity.
com
October 18,
2002 10:13 AM
Please
respond to
ORACLE-L
I am performing an export of a set of very large tables. I am not using
CONSISTENT mode. The exports are failing due to snapshot too old errors.
The
application uses many small rollback segments, but has one large one for
big
transactions. Is it possible to force the export to use the large segment
without taking all the others (except System) offline? I have seen this
question asked on the list before, but did not find a definitive follow-up
answer.
Thanks
Erik
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author:
INET: [EMAIL PROTECTED]
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: [EMAIL PROTECTED] (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).
