A big table is updated during a day on primary location. This table has MV logcreated - using PK.Once a day changes to this table has to be propagated to a remote site(on-demand replication based on PK).

Most of times replication process works fine, however, there are times whenlarger number of rows are updated. Then replication fails with errors above.I know that most straightforward way would be to increase rollback tablespacesize on remote site, however, we are short of disk space on that site andgrowing rollback tablespace (already 1.2G) just to accommodate this case itdoesn't makes much sense (most of transactions on that database are small).

<b>Is there a way of splitting replication transaction into number oftransactions?</b>

May be I am looking for something what does not exists, however, I hope, thatothers might faced similar problem and can share how they solved that.