Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Good day
We are replicating data from DB2 LUW (via a logstream staging task) to AWS Kinesis, but the metadata stream is empty.
We did set this in the end point: "Publish metadata messages to a dedicated metadata stream", with a separate stream for data and metadata.
Any suggestions? Which log items should be selected to assist with debugging?
Thanx
Abrie Marais
Hello Abrie Marais, @sanlamZA
Thanks for reaching out to Qlik Community!
Please enable TARGET_LOAD & TARGET_APPLY to Trace, (or Verbose) and re-run the task, some lines should be printed in task log file, for example, in Full Load stage:
2025-02-04T03:28:39:230343 [TARGET_LOAD ]T: sending batch (id = 1) with 1 messages, total size 5196, to stream johwg.metadata (kinesis_client.c:957)
Hope this helps.
John.
Hello Abrie Marais, @sanlamZA
Thanks for reaching out to Qlik Community!
Please enable TARGET_LOAD & TARGET_APPLY to Trace, (or Verbose) and re-run the task, some lines should be printed in task log file, for example, in Full Load stage:
2025-02-04T03:28:39:230343 [TARGET_LOAD ]T: sending batch (id = 1) with 1 messages, total size 5196, to stream johwg.metadata (kinesis_client.c:957)
Hope this helps.
John.
Hi John
Thanx for the speedy reply. I've managed to get find the entries in the logfile and the developers could see the messages in their Kinesis stream.
It's our first time using Kinesis as a target, so we're still learning 🙂
Regards
Thank you so much for your great support @sanlamZA !