Hi,
We have an Oracle to SQL transactional replication process set up and this process has been running fine until our business user decided to ran a large single batch update (60+ million records) which slowed down replication. Is there a way to update the number of commands the log reader is getting from the Oracle change tracking tables? I know that -ReadBatchSize is not supported for Oracle publishers, but what about -ReadBatchThreshold? To allow this large batch to replicate over, we had to stop SQL apply on the Oracle primary server and wait. It took about a day and a half for replication to get caught up. By default, how many transactions/rows/commands are in a batch and can we change this number? Any help will be appreciated. Thank you.
- Tae
tae yang