topic Oracle issue in logstream task in Qlik Replicate

Oracle issue in logstream task

Titus — Sat, 02 Dec 2023 18:32:24 GMT

When running Oracle source, we are facing the issue 'trying to retrieve the next change record from the source side,' but all table metadata is loaded, and log stream tasks are in a running state. please find below screenshots.
kindly help me to why this is happen and how to resolve it.

Re: Oracle issue in logstream task

john_wang — Sun, 03 Dec 2023 13:53:43 GMT

Hello @Titus ,

Welcome to Qlik Community and thanks for reaching out here!

It's hard to tell this time by the picture only. Would you please set SOURCE_CAPTURE to Verbose, re-create the issue and then check the task log file to see if there is any helpful clue there?

Regards,

John.

Re: Oracle issue in logstream task

Titus — Mon, 04 Dec 2023 09:54:04 GMT

Hi @john_wang ,
I attached here source capture verbouse level log file ,please give solution .

regards,
Titus

Re: Oracle issue in logstream task

SushilKumar — Mon, 04 Dec 2023 09:37:42 GMT

Hello Team,

Thanks for reaching out to Qlik via Qlik Community Support page. We request you to not to upload logs and DP here in Community portal. Such issue requires through analysis of Task Settings, hence request you to reach out to technical Support via a case and provide Diagnostics package.

Regards,

Sushil Kumar

Re: Oracle issue in logstream task

john_wang — Mon, 04 Dec 2023 09:53:42 GMT

Hello @Titus ,

Thanks for the files - please do not attach task log files in Qlik Community in the future. As it's public to all visitors, your task log file contains sensitive information including server IP Address and username etc.

I'm deleting the task log file for you right now.

You are facing the exact same error "ORA-15173" with another article:

OCI error 'ORA-15173: entry 'CECXA23' does not exist in directory '/'

Please check my answer in that article and try to run the script against your Oracle database and see if it's helpful.

Regards,

John.

Re: Oracle issue in logstream task

john_wang — Thu, 07 Dec 2023 03:35:46 GMT

Hello @Titus ,

In another article @suvbin confirmed the root cause is that the inaccurate credentials were provided. Fix the credentials solved the problem completely. I really appreciate @suvbin feedback!

Hope it helps.

Regards,

John.