Enabling Heartbeat Table Causes CPU Spike On The Target Database
Last updated on MAY 21, 2018
Applies to:Oracle GoldenGate - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
After enabling Heartbeat table at the target:
1) The heartbeat table gets Row Exclusive lock.
2) AWR report shows more "enq:TM - contention".
3) TOP SQL shows more elapsed time for heartbeat table update .
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms