Originally posted by Mr.Hanky
Hey Roger; Been there, done that.
I would create an export parfile and be sure to add
BUFFER=
COMMIT=Y
There is no INSERTS/UPDATES/DELETES performed during the export, so there is also no COMMIT= parameter available in EXPort! I belive you've confused this with IMPort.
Originally posted by rogerF
Is there a way to assign a special RBS to an export?
No, there isn't. And it wouldn't make sence. Export doesn't need rollback segments for writing undo information into them (as it doesn't change any data, anyway), but to constructs the read consistent view of table's data as it was when the export of that table begun. If during the proces of exporting other sessions are changing the contents of that table, export must find the values as they were at the begining of the table's export (Time 0). It can find this information only from the rollback segments into which other processes have wriiten their undo information about their changes. So it is not one RBS, there might be many of them that would help exp process to reconstruct the image of the data at Time 0. If any of that information in one of the rollback segment is allready overwritten, you'll get ORA-1555.

So you either follow mike73 advice (export when there is not much changes performed on those tables and don't use CONSISTENT=Y if it is not necessary), or make your rollback segments bigger (and/or make more of them). Your RB segments might be sized OK for your transactions, but they obviously are not sized OK for long running queries like EXP.