Rollback segment size is not the primary reason for this error.
Basic reason is, the tables that you are trying to export are getting changed (UPD/INs/DEL) while the export is on. And ORACLE's attempt to get a read consistent copy of a table is failing.
Sure solution for this is : Stop those changes happening during exports.
If I know what kind of operations are happening, I can demonstrate this error irrespective of rollback segment size and number of rollback segments.
ORA-1555 is probably the most discussed oracle error on the Net. You can find it at quite a few places that ORACLE's error message for this number is mis-leading.
Its also known that howsoever huge rollbacks you create, you can not gurantee that this error will not occur during export if data changes are happening simultaneously.
In my mind the problem not in size of rollback segment(s),
most probability, problem in not enougth RBS for new transaction during export.
Oracle use READ ONLY transactions in exp utility, and all RBS for uncommited and commited trasactions should be store all(or part) export time. If doesn't exists free RBS for new transaction, oracle generate error ORA-1555.
Problem in number :
#RBS(online) * TRANSACTION_PER_ROLLBACK_SEGMENT (init.ora)
and summary number transaction during export process.
You are getting ORA-1555, because Oracle cannot create a read consistent picture of the table. Getting the ORA-1555 on an export with 'consistent=Y' is common. Are you making a consistent export?
A rollback segment will not extend to preserve read consistent information for the export. Make the export when other people are not accessing the DB.
well the main problem is the rollback segment is too small...you can increase the size of them next time...but on the interim solution you can bring the rollback segment that is full offline and the next available rollback segment will take over and complete your export....but afterward try to increase your rollback segment.....
Bookmarks