Mixed Up Output Messages When Working With TRAIL File From HP NONSTOP Base24 System (Doc ID 3032024.1)

Last updated on AUGUST 08, 2024

Applies to:

Symptoms

Our goal is to send TRAIL file content to Kafka (each record separately).
The source trail file - according to logdump utility - has two columns SYSKEY with 8 bytes length and FabCol1 with 4000 bytes length, but checking the records, FabCol1 has a variable length (always far less than 4000 bytes).
However Goldengate sends records to Kafka (we also tried FileWriter plugin, the result was the same) with content padded with 0x00 to match the 4000 bytes length. We could live with this "limitation" (but of course it is far not the most effective).
The main problem is as follows (not real messages, but readable for easy understanding):
Message id, message from trail file, message sent to Kafka (or FileWriter):
1,HELLO,HELLO
2,HELLO GOLDENGATE,HELLO GOLDENGATE
3,HELLO TEST,HELLO TESTENGATE
It seems like content from message 2 stays in some kind of "buffer", and message 3 uses the same "buffer" and content from previous (longer!) message appended to the newer (shorter!) message.
We don't use any special conversion, it is reproductible with a simple PARAM file with MAP *.*.* TARGET *.*.*

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.