Tuning OGGBD replicat to process LOB data in Snowflake
(Doc ID 2956888.1)
Last updated on JULY 20, 2024
Applies to:
Oracle GoldenGate Big Data and Application Adapters - Version 21.8.0.0.0 and laterInformation in this document applies to any platform.
Goal
How can we improve the snowflake replicat performance when dealing with LOB Columns.
Log messages in OGGBD version < 21.10:
The following messages indicates LOB processing that can be tuned.
INFO 2023-03-29 16:29:37.000159 [main] - Operation aggregator is flushing
merged operations because the current operation contains at least one out of
line LOB column value that exceeds [16000] bytes.
Log messages in OGGBD version >= 21.10:
The current operation at position[<seqno>/<rba>] for table [<tablename>]
contains a LOB column [<column name>] of length [<N>] bytes that exceeds the
threshold of maximum inline LOB size [<N>].
Operation Aggregator will flush merged operations, this could degrade performance.
The maximum inline LOB size in bytes can be tuned using the configuration gg.maxInlineLobSize.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| References |