R
Richard Banville
Guest
Thanks. That will help get the right resources to investigate the issue and determine if there is a bug here and if so how to fix it. If I am understanding this properly, the reads of the existing history1 table (where all object references should be in primary om cache if set large enough at startup) are incurring om latch activity after the secondary om cache contains entries for the CDC change capture tables. Am I properly interpreting what you are encountering?
Continue reading...
Continue reading...