OGG How to address Extract Performance Issue When Reading Archive Logs stored in Oracle ASM
Last updated on JANUARY 22, 2018
Applies to:Oracle GoldenGate - Version 18.104.22.168 and later
Information in this document applies to any platform.
There is increasing lag on an extract and the archive logs are stored on ASM.
Using TRACE/TRACE2 will display summary stats where Extract is spending the majority of time reading records from the redo.
04:11:13.008 (+0,0,0) Redo log statistics:
04:11:13.008 (+0,0,0) 82.70% Reading record from redo log file
04:11:13.008 (+0,0,0) 8.64% Extracting subrecord from redo record
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms