After finished running full load on 125 tables (approx. 4 billion record), which took about 15-17 hours to complete without any error, the task have switched to CDC since.
I noticed a few things on my CDC Monitor:
1. The incoming changes is getting very large, 17 Million per this thread is created, about 2.4 million transactions.
2. The 17 million is building up on Apply On Disk. It also says applying 2.4 million transactions (until target commit).
3. The Apply latency actually continues to drop from 11 hours about 2 hours ago before this thread is created, to 3 hours when this thread is created.
The attached screenshot depicts the above.
![Name: attunity_screenshot.JPG
Views: 9
Size: 45.6 KB]()
Question:
- What is actually happening?
- Is this normal behavior after a very long full load duration?
- Is there some tuning that can be done?
Thanks!
Kind regards,
R
I noticed a few things on my CDC Monitor:
1. The incoming changes is getting very large, 17 Million per this thread is created, about 2.4 million transactions.
2. The 17 million is building up on Apply On Disk. It also says applying 2.4 million transactions (until target commit).
3. The Apply latency actually continues to drop from 11 hours about 2 hours ago before this thread is created, to 3 hours when this thread is created.
The attached screenshot depicts the above.
Question:
- What is actually happening?
- Is this normal behavior after a very long full load duration?
- Is there some tuning that can be done?
Thanks!
Kind regards,
R