Is this the same site/problem as https://community.qlik.com/t5/Qlik-Replicate/How-do-we-configure-Replicate-Log-Reader-on-Qlik-Replic... ???
The error looks different yet both mention ASM. Please stick to a single topic if it is the same site/problem
You blanked out the connection string in the picture. Is that really a security issue? I don't think so. It might be incorrect. In the task log we can see "Going to connect to Oracle server //xxxx:1521/yyyy". - bbut in my test I don't see the // server name introducer. is the right syntax used - we can't see but it feels wrong? Can you use SQLserver or TNSping with that connection string? EDIT: I since tried the // on my source endpoint connection string and it does not seem to make a difference.
The Task log looks really bad with the uncontrolled and uncorrectable reconnection attempts. You may want to submit a support case to address both root cause and the reaction. Version V2023.5.0.152 is about as recent as it gets (it is what I test with ... and I connect fine to my Oracle source without ASM. Now your Windows server is just 2012 - old but that shouldn't matter much.
The task JSON, and notably the source endpoint section might provide insight.
Btw... next time you <snip> the log after 5 or 10 repeats and indicate <snipped 1000+ repeats in XX minutes>
Maybe there is something odd about the source DB, do you have an other one to connect to , just an express edition if you have to?
Next time, maybe run with LOGGING SOURCE_CAPTURE VERBOSE to hopefully get relevant details. Kill after first errors.
Hein.
