<?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>article Qlik Stitch Database integration extraction error: Fatal Error Occured &amp;lt;&amp;gt;decimal SQL type for value type class clojure.core$val is not implemented in Official Support Articles</title>
    <link>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Stitch-Database-integration-extraction-error-Fatal-Error/ta-p/2538388</link>
    <description>&lt;P&gt;This article addresses the error encountered during extraction when using &lt;STRONG&gt;log-based incremental replication&lt;/STRONG&gt;&amp;nbsp;for MySQL integration:&lt;/P&gt;
&lt;P style="padding-left: 40px;"&gt;&lt;FONT face="courier new,courier"&gt;&lt;SPAN&gt;[main] tap-hp-mysql.sync-strategies.binlog - Fatal Error Occurred - &amp;lt;ColumnName&amp;gt; - decimal SQL type for value type class clojure.core$val is not implemented.&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Resolution&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;P&gt;There are two recommended approaches:&lt;/P&gt;
&lt;P&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Option 1: Enable Commit Order Preservation&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;Run the following command in your MySQL instance:&lt;/P&gt;
&lt;PRE class="ckeditor_codeblock"&gt;SET GLOBAL replica_preserve_commit_order = ON;&lt;/PRE&gt;
&lt;P&gt;Then, &lt;STRONG&gt;reset the affected table(s)&lt;/STRONG&gt; through the integration settings.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Option 2: Validate Replication Settings&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;Ensure that either:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;CODE&gt;replica_preserve_commit_order&lt;/CODE&gt; (MySQL 8.0+), or&lt;/LI&gt;
&lt;LI&gt;&lt;CODE&gt;slave_preserve_commit_order&lt;/CODE&gt; (older versions)&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;is enabled. These settings maintain commit order on multi-threaded replicas, preventing gaps and inconsistencies.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;How to Check if Setting is Enabled&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;P&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Run:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;PRE class="ckeditor_codeblock"&gt;SHOW GLOBAL VARIABLES LIKE 'replica_preserve_commit_order';&lt;/PRE&gt;
&lt;P&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Expected Output:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;TABLE border="1" width="100%"&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD colspan="1" rowspan="1" width="25.793650793650798%" height="24px"&gt;&lt;CODE&gt;Variable_name&lt;/CODE&gt;&lt;/TD&gt;
&lt;TD colspan="1" rowspan="1" width="25.793650793650798%" height="24px"&gt;&lt;CODE&gt;Value&lt;/CODE&gt;&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD colspan="1" rowspan="1" width="25.793650793650798%" height="24px"&gt;&lt;CODE&gt;replica_preserve_commit_order&lt;/CODE&gt;&lt;/TD&gt;
&lt;TD colspan="1" rowspan="1" width="25.793650793650798%" height="24px"&gt;&lt;CODE&gt;ON&lt;/CODE&gt;&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;For older versions:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;PRE class="ckeditor_codeblock"&gt;SHOW GLOBAL VARIABLES LIKE 'slave_preserve_commit_order';&lt;/PRE&gt;
&lt;P&gt;For more information, reference MySQL Documentation&lt;/P&gt;
&lt;P&gt;&lt;A href="https://dev.mysql.com/doc/refman/8.0/en/replication-features-transaction-inconsistencies.html" target="_blank" rel="noopener"&gt;replication-features-transaction-inconsistencies | dev.mysql.com&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;STRONG&gt;&lt;FONT color="#339966"&gt;Cause&lt;/FONT&gt; &lt;/STRONG&gt;&lt;/H3&gt;
&lt;P&gt;When using &lt;STRONG&gt;log-based incremental replication&lt;/STRONG&gt;, Stitch reads changes from MySQL’s binary log (binlog). This error occurs because the source database provides events &lt;STRONG&gt;out of order&lt;/STRONG&gt;, which leads to mismatched data types during extraction. In this case, the extraction encounters a decimal SQL type where the value type is unexpected.&lt;/P&gt;
&lt;P&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Why does this happen?&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Non-transactional DML statements that do not guarantee ordering.&lt;/LI&gt;
&lt;LI&gt;Misconfigured or inconsistent replication setup.&lt;/LI&gt;
&lt;LI&gt;Multi-threaded replication without commit order preservation, causing commit gaps and inconsistencies.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H4&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Environment&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H4&gt;
&lt;P&gt;&lt;LI-PRODUCT title="Stitch" id="qlikStitch"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 09 Dec 2025 05:38:42 GMT</pubDate>
    <dc:creator>David_Apodaca</dc:creator>
    <dc:date>2025-12-09T05:38:42Z</dc:date>
    <item>
      <title>Qlik Stitch Database integration extraction error: Fatal Error Occured &lt;&gt;decimal SQL type for value type class clojure.core$val is not implemented</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Stitch-Database-integration-extraction-error-Fatal-Error/ta-p/2538388</link>
      <description>&lt;P&gt;This article addresses the error encountered during extraction when using &lt;STRONG&gt;log-based incremental replication&lt;/STRONG&gt;&amp;nbsp;for MySQL integration:&lt;/P&gt;
&lt;P style="padding-left: 40px;"&gt;&lt;FONT face="courier new,courier"&gt;&lt;SPAN&gt;[main] tap-hp-mysql.sync-strategies.binlog - Fatal Error Occurred - &amp;lt;ColumnName&amp;gt; - decimal SQL type for value type class clojure.core$val is not implemented.&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Resolution&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;P&gt;There are two recommended approaches:&lt;/P&gt;
&lt;P&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Option 1: Enable Commit Order Preservation&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;Run the following command in your MySQL instance:&lt;/P&gt;
&lt;PRE class="ckeditor_codeblock"&gt;SET GLOBAL replica_preserve_commit_order = ON;&lt;/PRE&gt;
&lt;P&gt;Then, &lt;STRONG&gt;reset the affected table(s)&lt;/STRONG&gt; through the integration settings.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Option 2: Validate Replication Settings&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;Ensure that either:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;CODE&gt;replica_preserve_commit_order&lt;/CODE&gt; (MySQL 8.0+), or&lt;/LI&gt;
&lt;LI&gt;&lt;CODE&gt;slave_preserve_commit_order&lt;/CODE&gt; (older versions)&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;is enabled. These settings maintain commit order on multi-threaded replicas, preventing gaps and inconsistencies.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;How to Check if Setting is Enabled&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;P&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Run:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;PRE class="ckeditor_codeblock"&gt;SHOW GLOBAL VARIABLES LIKE 'replica_preserve_commit_order';&lt;/PRE&gt;
&lt;P&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Expected Output:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;TABLE border="1" width="100%"&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD colspan="1" rowspan="1" width="25.793650793650798%" height="24px"&gt;&lt;CODE&gt;Variable_name&lt;/CODE&gt;&lt;/TD&gt;
&lt;TD colspan="1" rowspan="1" width="25.793650793650798%" height="24px"&gt;&lt;CODE&gt;Value&lt;/CODE&gt;&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD colspan="1" rowspan="1" width="25.793650793650798%" height="24px"&gt;&lt;CODE&gt;replica_preserve_commit_order&lt;/CODE&gt;&lt;/TD&gt;
&lt;TD colspan="1" rowspan="1" width="25.793650793650798%" height="24px"&gt;&lt;CODE&gt;ON&lt;/CODE&gt;&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;For older versions:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;PRE class="ckeditor_codeblock"&gt;SHOW GLOBAL VARIABLES LIKE 'slave_preserve_commit_order';&lt;/PRE&gt;
&lt;P&gt;For more information, reference MySQL Documentation&lt;/P&gt;
&lt;P&gt;&lt;A href="https://dev.mysql.com/doc/refman/8.0/en/replication-features-transaction-inconsistencies.html" target="_blank" rel="noopener"&gt;replication-features-transaction-inconsistencies | dev.mysql.com&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;STRONG&gt;&lt;FONT color="#339966"&gt;Cause&lt;/FONT&gt; &lt;/STRONG&gt;&lt;/H3&gt;
&lt;P&gt;When using &lt;STRONG&gt;log-based incremental replication&lt;/STRONG&gt;, Stitch reads changes from MySQL’s binary log (binlog). This error occurs because the source database provides events &lt;STRONG&gt;out of order&lt;/STRONG&gt;, which leads to mismatched data types during extraction. In this case, the extraction encounters a decimal SQL type where the value type is unexpected.&lt;/P&gt;
&lt;P&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Why does this happen?&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Non-transactional DML statements that do not guarantee ordering.&lt;/LI&gt;
&lt;LI&gt;Misconfigured or inconsistent replication setup.&lt;/LI&gt;
&lt;LI&gt;Multi-threaded replication without commit order preservation, causing commit gaps and inconsistencies.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H4&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Environment&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H4&gt;
&lt;P&gt;&lt;LI-PRODUCT title="Stitch" id="qlikStitch"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 09 Dec 2025 05:38:42 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Stitch-Database-integration-extraction-error-Fatal-Error/ta-p/2538388</guid>
      <dc:creator>David_Apodaca</dc:creator>
      <dc:date>2025-12-09T05:38:42Z</dc:date>
    </item>
  </channel>
</rss>

