Coordinated replicat with kafka-handler in order to reduce the message latency, Message order was not maintained and duplicates are shown at target side - Why?
(Doc ID 2594636.1)
Last updated on JULY 20, 2024
Applies to:
Oracle GoldenGate Application Adapters - Version 12.3 and laterInformation in this document applies to any platform.
Purpose
User trying coordinated replicat with kafka-handler in order to reduce the message latency. They noticed that the message order is not being maintained in coordinated replicat for Kafka.
Question: How coordinated replicat preserves the data quality and make sure the data is not lost/wrongly applied.
Example:
{"table":"V500.ENCOUNTER","op_type":"U","op_ts":"2019-08-19 10:01:38.000000","current_ts":"2019-08-19T10:01:46.551000","pos":"00000091260112141465",
{"table":"V500.ENCOUNTER","op_type":"U","op_ts":"2019-08-19 10:01:38.000000","current_ts":"2019-08-19T10:01:46.552003","pos":"00000091260112230281",
{"table":"V500.ENCOUNTER","op_type":"U","op_ts":"2019-08-19 10:01:34.000000","current_ts":"2019-08-19T10:01:46.585000","pos":"00000091260110433398",
{"table":"V500.ENCOUNTER","op_type":"U","op_ts":"2019-08-19 10:01:38.000000","current_ts":"2019-08-19T10:01:46.625001","pos":"00000091260112141465",
Questions and Answers
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
Purpose |
Questions and Answers |