[Oracle Srv 126.96.36.199 on Solaris 2.8]
when exporting an instance sometimes the exp process is throwing snapshot too old msg on large table 2GB+ . the exp is done with consistent=y because consistent exp files might be needed in the QS department.
on metalink I found a document ref. advising how to allocate a large rbs to the specific batch process; unfortunately this document is unavailable.
Does anybody how how to attach a large rbs to the exp process?
the easiest way is to offline all the other rollback segments, leaving only the large rollback segment online, start the export running and then bring the other rollback segments back online. I'm not aware of any way of explicitly attaching an export command to a particular rollback segment.
then run your transaction in the same SQL*Plus session. However, you cannot do that with the exp process. You have to take offline all the small RBS and bring online a huge RBS able to handle the export rollback segment entries.