<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Qlik Replicate Log Reader- Throwing error even if ASM not enabled at Oracle source- Cannot connect to ASM server in Qlik Replicate</title>
    <link>https://community.qlik.com/t5/Qlik-Replicate/Qlik-Replicate-Log-Reader-Throwing-error-even-if-ASM-not-enabled/m-p/2124907#M7527</link>
    <description>&lt;P&gt;Is this the same site/problem as&amp;nbsp;&lt;A href="https://community.qlik.com/t5/Qlik-Replicate/How-do-we-configure-Replicate-Log-Reader-on-Qlik-Replicate-when/td-p/2124759" target="_blank" rel="noopener"&gt;https://community.qlik.com/t5/Qlik-Replicate/How-do-we-configure-Replicate-Log-Reader-on-Qlik-Replicate-when/td-p/2124759&lt;/A&gt;&amp;nbsp; &amp;nbsp;???&lt;/P&gt;
&lt;P&gt;The error looks different yet both mention ASM. Please stick to a single topic if it is the same site/problem&lt;/P&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;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&amp;nbsp;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.&lt;/P&gt;
&lt;P&gt;The task JSON, and notably the source endpoint section might provide insight.&lt;/P&gt;
&lt;P&gt;Btw... next time you &amp;lt;snip&amp;gt; the log after 5 or 10 repeats&amp;nbsp; and indicate &amp;lt;snipped 1000+ repeats in XX minutes&amp;gt;&lt;/P&gt;
&lt;P&gt;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?&lt;/P&gt;
&lt;P&gt;Next time, maybe run with LOGGING SOURCE_CAPTURE VERBOSE to hopefully get relevant details. Kill after first errors.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hein.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 04 Oct 2023 12:01:52 GMT</pubDate>
    <dc:creator>Heinvandenheuvel</dc:creator>
    <dc:date>2023-10-04T12:01:52Z</dc:date>
    <item>
      <title>Qlik Replicate Log Reader- Throwing error even if ASM not enabled at Oracle source- Cannot connect to ASM server</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Qlik-Replicate-Log-Reader-Throwing-error-even-if-ASM-not-enabled/m-p/2124902#M7525</link>
      <description>&lt;P&gt;Hi There,&lt;/P&gt;
&lt;P&gt;I am trying to enable CDC in my Qlik task with Oracle DB as source. I don't have ASM enabled at the source. Hence, I just selected Replicate Log reader and kept rest everything default in the advanced page of EndPoint setting. Connection test is working fine and data load working when using just full load but when we run the task with CDC enabled, it failed throwing below error: Kindly refer attached configuration, log file and error message and help me to resolve the issue.&lt;/P&gt;
&lt;P&gt;Cannot connect to ASM server ''(user '', Redo Thread 1, OCIthread 0)&lt;BR /&gt;Cannot attach OCI server&lt;BR /&gt;OCI error 'ORA-12560: TNS:protocol adapter error'&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Oct 2023 02:30:16 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Qlik-Replicate-Log-Reader-Throwing-error-even-if-ASM-not-enabled/m-p/2124902#M7525</guid>
      <dc:creator>sanjeevbind</dc:creator>
      <dc:date>2023-10-04T02:30:16Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Replicate Log Reader- Throwing error even if ASM not enabled at Oracle source- Cannot connect to ASM server</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Qlik-Replicate-Log-Reader-Throwing-error-even-if-ASM-not-enabled/m-p/2124907#M7527</link>
      <description>&lt;P&gt;Is this the same site/problem as&amp;nbsp;&lt;A href="https://community.qlik.com/t5/Qlik-Replicate/How-do-we-configure-Replicate-Log-Reader-on-Qlik-Replicate-when/td-p/2124759" target="_blank" rel="noopener"&gt;https://community.qlik.com/t5/Qlik-Replicate/How-do-we-configure-Replicate-Log-Reader-on-Qlik-Replicate-when/td-p/2124759&lt;/A&gt;&amp;nbsp; &amp;nbsp;???&lt;/P&gt;
&lt;P&gt;The error looks different yet both mention ASM. Please stick to a single topic if it is the same site/problem&lt;/P&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;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&amp;nbsp;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.&lt;/P&gt;
&lt;P&gt;The task JSON, and notably the source endpoint section might provide insight.&lt;/P&gt;
&lt;P&gt;Btw... next time you &amp;lt;snip&amp;gt; the log after 5 or 10 repeats&amp;nbsp; and indicate &amp;lt;snipped 1000+ repeats in XX minutes&amp;gt;&lt;/P&gt;
&lt;P&gt;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?&lt;/P&gt;
&lt;P&gt;Next time, maybe run with LOGGING SOURCE_CAPTURE VERBOSE to hopefully get relevant details. Kill after first errors.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hein.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Oct 2023 12:01:52 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Qlik-Replicate-Log-Reader-Throwing-error-even-if-ASM-not-enabled/m-p/2124907#M7527</guid>
      <dc:creator>Heinvandenheuvel</dc:creator>
      <dc:date>2023-10-04T12:01:52Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Replicate Log Reader- Throwing error even if ASM not enabled at Oracle source- Cannot connect to ASM server</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Qlik-Replicate-Log-Reader-Throwing-error-even-if-ASM-not-enabled/m-p/2125240#M7547</link>
      <description>&lt;P&gt;Switch logging for SOURCE_READER to VERBOSE.&lt;/P&gt;
&lt;P&gt;Maybe there is, or there was at some point, ASM usage after all.&lt;/P&gt;
&lt;P&gt;Search the log for a string like :&amp;nbsp;&lt;STRONG&gt;Going to open Redo Log with original name '+DATA_A&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;I suspect it is good enough to just look for&lt;FONT color="#FF0000"&gt;&lt;STRONG&gt; '+&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;You'll get a couple of hits for TIMEZONE, but that should be all if ASM was not in play (at some point in time)&lt;/P&gt;
&lt;P&gt;Hein.&lt;/P&gt;</description>
      <pubDate>Wed, 04 Oct 2023 17:42:08 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Qlik-Replicate-Log-Reader-Throwing-error-even-if-ASM-not-enabled/m-p/2125240#M7547</guid>
      <dc:creator>Heinvandenheuvel</dc:creator>
      <dc:date>2023-10-04T17:42:08Z</dc:date>
    </item>
  </channel>
</rss>

