<?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 Troubleshooting: Error: QVX_UNEXPECTED_END_OF_DATA: SQL##f - SqlState: S1000, ErrorCode: 50310, ErrorMsg: [Qlik][Support] (50310) Unrecognized ICU conversion error. in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/Troubleshooting-Error-QVX-UNEXPECTED-END-OF-DATA-SQL-f-SqlState/m-p/137703#M9694</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;Quick Background&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I wanted to share troubleshooting this issue when we had a QLIK Data Load.&lt;/P&gt;&lt;P&gt;We try to do the QVD extract/transform pull and generate so other apps can use them.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;Problem&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;During one of the QVD regen load scripts, an error was thrown:&lt;/P&gt;&lt;P&gt;QVX_UNEXPECTED_END_OF_DATA: SQL##f - SqlState: S1000, ErrorCode: 50310, ErrorMsg: [Qlik][Support] (50310) Unrecognized ICU conversion error.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;Search on Problem Results&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Looking at other sources, it pointed to odd characters in the data.&lt;/P&gt;&lt;P&gt;A list of these (QLIK community items) can be found at the bottom of the post titled "&lt;STRONG&gt;Other Resources&lt;/STRONG&gt;".&lt;/P&gt;&lt;P&gt;Please note that this method may have issues and there maybe more efficient and effective ways of doing it.&lt;/P&gt;&lt;P&gt;This is to help get the debugging / resolution going.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;Identify Trouble Data&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The first thing was to identify what data was causing it to abort.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;The script that was aborting was generic:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TABLE_IN_QUESTION:&lt;/P&gt;&lt;P&gt;LOAD *;&lt;/P&gt;&lt;P&gt;SQL &lt;/P&gt;&lt;P&gt;SELECT * &lt;/P&gt;&lt;P&gt;FROM "BICORE"."TABLE_IN_QUESTION";&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Store TABLE_IN_QUESTIONinto [lib://Qlik Data/QVD/Extract/TABLE_IN_QUESTION].qvd;&lt;/P&gt;&lt;P&gt;Drop Table TABLE_IN_QUESTION;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We copied this into another QLIK app so we could focus solely on this part.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So we did a query to get the data divided up by a major milestone (e.g. years).&lt;/P&gt;&lt;P&gt;When we did this, we had a span of data from 2007-2018.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So the first thing added was a where clause to break it up (starting point was (max-min)/2 approx.):&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TABLE_IN_QUESTION:&lt;/P&gt;&lt;P&gt;LOAD *;&lt;/P&gt;&lt;P&gt;SQL &lt;/P&gt;&lt;P&gt;SELECT * &lt;/P&gt;&lt;P&gt;FROM "SCHEMA"."TABLE_IN_QUESTION"&lt;/P&gt;&lt;P&gt;WHERE&lt;/P&gt;&lt;P&gt;YEAR &amp;lt;= '2010';&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It was ok, so increment by 1 or 2 (your choice) it until it bombed (2017 in this case).&lt;/P&gt;&lt;P&gt;Next we looked at the year in question to see what was going on.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;Identify Trouble Data Structure&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The script was modified from&lt;/P&gt;&lt;P&gt;&lt;EM&gt;SELECT * FROM&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;to &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;SELECT&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;column_1,&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;column_2,&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;......&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;column_10,&lt;BR /&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;......&lt;BR /&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;column_n&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;FROM&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;where&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;YEAR = '2017';&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;where column_i were the actual column names.&lt;/P&gt;&lt;P&gt;At the n/2 point, we added a&amp;nbsp; /* and at the end before the from added the last */.&lt;/P&gt;&lt;P&gt;It passed. (so these were not the issue columns)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So move the n/2 point up (by a few or by 1, whatever).&lt;/P&gt;&lt;P&gt;At one point it will fail.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When it failed, we realized this is the column that was having the issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The characters present were not in the normal range (ansi/utf8) and this was confirmed by the oracle query:&lt;/P&gt;&lt;P&gt;select&lt;/P&gt;&lt;P&gt;*&lt;/P&gt;&lt;P&gt;from&lt;/P&gt;&lt;P&gt;TABLE_IN_QUESTION&lt;/P&gt;&lt;P&gt;WHERE&lt;/P&gt;&lt;P&gt;length(asciistr(WHATEVERYOURCOLUMNISCALLED))!=length(WHATEVERYOURCOLUMNISCALLED)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;where the WHATEVERYOURCOLUMNISCALLED is the column that was having the issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;Possible Resolutions&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At this point, the question is what to do to resolve it:&lt;/P&gt;&lt;P&gt;1 - the data may need to be modified&lt;/P&gt;&lt;P&gt;2 - a function applied to strip them out&lt;/P&gt;&lt;P&gt;3 - the column can be left out&lt;/P&gt;&lt;P&gt;4 - there maybe some ODBC things that can be done&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For now, we are going to try option 2 (option 1 was out, option 3 had dependencies, option 4 not considered at this point)&lt;/P&gt;&lt;P&gt;REGEXP_REPLACE(WHATEVERYOURCOLUMNISCALLED, '[^a-zA-Z0-9]+', '') WHATEVERYOURCOLUMNISCALLED&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This strips out the offending parts.&amp;nbsp; Please note we have not tested this with other characters to see how it behaves. Important for international data sets.&lt;/P&gt;&lt;P&gt;This also assigns an alias back to itself so other apps that may use it can remain untouched.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Side note&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Data pull raw from Oracle it had this issue.&lt;/P&gt;&lt;P&gt;From a text file was able to load without the issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;Conclusion&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We went with a function (oracle supplied, will try to not have it as a manual one unless we have to) to try to solve the issue for now. &lt;/P&gt;&lt;P&gt;Hopefully this has helped some in debugging and figuring out &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;Other Resources&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Other Documents on the QLIK site on the issue and how they resolved them.&lt;/P&gt;&lt;P&gt;QVX_UNEXPECTED_END_OF_DATA: SQL##f - (50310) Unrecognized ICU conversion error.&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://community.qlik.com/thread/286582"&gt;https://community.qlik.com/thread/286582&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ErrorCode: 50310 loading from ODBC connected database&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://community.qlik.com/thread/266128"&gt;https://community.qlik.com/thread/266128&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;QVX_UNEXPECTED_END_OF_DATA:&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://community.qlik.com/thread/294175"&gt;https://community.qlik.com/thread/294175&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;QVX_UNEXPECTED_END_OF_DATA: SQL##f - (50310) Unrecognized ICU conversion error.&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://community.qlik.com/message/1410145#1410145"&gt;https://community.qlik.com/message/1410145#1410145&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Oracle Query used in identification of the odd data:&lt;/P&gt;&lt;P&gt;In the where clause:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Oracle part used on different data&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;length(asciistr(WHATEVERYOURCOLUMNISCALLED))!=length(WHATEVERYOURCOLUMNISCALLED)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 12 Jul 2018 21:49:43 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2018-07-12T21:49:43Z</dc:date>
    <item>
      <title>Troubleshooting: Error: QVX_UNEXPECTED_END_OF_DATA: SQL##f - SqlState: S1000, ErrorCode: 50310, ErrorMsg: [Qlik][Support] (50310) Unrecognized ICU conversion error.</title>
      <link>https://community.qlik.com/t5/App-Development/Troubleshooting-Error-QVX-UNEXPECTED-END-OF-DATA-SQL-f-SqlState/m-p/137703#M9694</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;Quick Background&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I wanted to share troubleshooting this issue when we had a QLIK Data Load.&lt;/P&gt;&lt;P&gt;We try to do the QVD extract/transform pull and generate so other apps can use them.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;Problem&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;During one of the QVD regen load scripts, an error was thrown:&lt;/P&gt;&lt;P&gt;QVX_UNEXPECTED_END_OF_DATA: SQL##f - SqlState: S1000, ErrorCode: 50310, ErrorMsg: [Qlik][Support] (50310) Unrecognized ICU conversion error.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;Search on Problem Results&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Looking at other sources, it pointed to odd characters in the data.&lt;/P&gt;&lt;P&gt;A list of these (QLIK community items) can be found at the bottom of the post titled "&lt;STRONG&gt;Other Resources&lt;/STRONG&gt;".&lt;/P&gt;&lt;P&gt;Please note that this method may have issues and there maybe more efficient and effective ways of doing it.&lt;/P&gt;&lt;P&gt;This is to help get the debugging / resolution going.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;Identify Trouble Data&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The first thing was to identify what data was causing it to abort.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;The script that was aborting was generic:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TABLE_IN_QUESTION:&lt;/P&gt;&lt;P&gt;LOAD *;&lt;/P&gt;&lt;P&gt;SQL &lt;/P&gt;&lt;P&gt;SELECT * &lt;/P&gt;&lt;P&gt;FROM "BICORE"."TABLE_IN_QUESTION";&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Store TABLE_IN_QUESTIONinto [lib://Qlik Data/QVD/Extract/TABLE_IN_QUESTION].qvd;&lt;/P&gt;&lt;P&gt;Drop Table TABLE_IN_QUESTION;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We copied this into another QLIK app so we could focus solely on this part.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So we did a query to get the data divided up by a major milestone (e.g. years).&lt;/P&gt;&lt;P&gt;When we did this, we had a span of data from 2007-2018.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So the first thing added was a where clause to break it up (starting point was (max-min)/2 approx.):&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TABLE_IN_QUESTION:&lt;/P&gt;&lt;P&gt;LOAD *;&lt;/P&gt;&lt;P&gt;SQL &lt;/P&gt;&lt;P&gt;SELECT * &lt;/P&gt;&lt;P&gt;FROM "SCHEMA"."TABLE_IN_QUESTION"&lt;/P&gt;&lt;P&gt;WHERE&lt;/P&gt;&lt;P&gt;YEAR &amp;lt;= '2010';&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It was ok, so increment by 1 or 2 (your choice) it until it bombed (2017 in this case).&lt;/P&gt;&lt;P&gt;Next we looked at the year in question to see what was going on.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;Identify Trouble Data Structure&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The script was modified from&lt;/P&gt;&lt;P&gt;&lt;EM&gt;SELECT * FROM&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;to &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;SELECT&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;column_1,&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;column_2,&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;......&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;column_10,&lt;BR /&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;......&lt;BR /&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;column_n&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;FROM&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;where&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;YEAR = '2017';&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;where column_i were the actual column names.&lt;/P&gt;&lt;P&gt;At the n/2 point, we added a&amp;nbsp; /* and at the end before the from added the last */.&lt;/P&gt;&lt;P&gt;It passed. (so these were not the issue columns)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So move the n/2 point up (by a few or by 1, whatever).&lt;/P&gt;&lt;P&gt;At one point it will fail.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When it failed, we realized this is the column that was having the issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The characters present were not in the normal range (ansi/utf8) and this was confirmed by the oracle query:&lt;/P&gt;&lt;P&gt;select&lt;/P&gt;&lt;P&gt;*&lt;/P&gt;&lt;P&gt;from&lt;/P&gt;&lt;P&gt;TABLE_IN_QUESTION&lt;/P&gt;&lt;P&gt;WHERE&lt;/P&gt;&lt;P&gt;length(asciistr(WHATEVERYOURCOLUMNISCALLED))!=length(WHATEVERYOURCOLUMNISCALLED)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;where the WHATEVERYOURCOLUMNISCALLED is the column that was having the issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;Possible Resolutions&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At this point, the question is what to do to resolve it:&lt;/P&gt;&lt;P&gt;1 - the data may need to be modified&lt;/P&gt;&lt;P&gt;2 - a function applied to strip them out&lt;/P&gt;&lt;P&gt;3 - the column can be left out&lt;/P&gt;&lt;P&gt;4 - there maybe some ODBC things that can be done&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For now, we are going to try option 2 (option 1 was out, option 3 had dependencies, option 4 not considered at this point)&lt;/P&gt;&lt;P&gt;REGEXP_REPLACE(WHATEVERYOURCOLUMNISCALLED, '[^a-zA-Z0-9]+', '') WHATEVERYOURCOLUMNISCALLED&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This strips out the offending parts.&amp;nbsp; Please note we have not tested this with other characters to see how it behaves. Important for international data sets.&lt;/P&gt;&lt;P&gt;This also assigns an alias back to itself so other apps that may use it can remain untouched.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Side note&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Data pull raw from Oracle it had this issue.&lt;/P&gt;&lt;P&gt;From a text file was able to load without the issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;Conclusion&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We went with a function (oracle supplied, will try to not have it as a manual one unless we have to) to try to solve the issue for now. &lt;/P&gt;&lt;P&gt;Hopefully this has helped some in debugging and figuring out &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;Other Resources&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Other Documents on the QLIK site on the issue and how they resolved them.&lt;/P&gt;&lt;P&gt;QVX_UNEXPECTED_END_OF_DATA: SQL##f - (50310) Unrecognized ICU conversion error.&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://community.qlik.com/thread/286582"&gt;https://community.qlik.com/thread/286582&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ErrorCode: 50310 loading from ODBC connected database&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://community.qlik.com/thread/266128"&gt;https://community.qlik.com/thread/266128&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;QVX_UNEXPECTED_END_OF_DATA:&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://community.qlik.com/thread/294175"&gt;https://community.qlik.com/thread/294175&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;QVX_UNEXPECTED_END_OF_DATA: SQL##f - (50310) Unrecognized ICU conversion error.&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://community.qlik.com/message/1410145#1410145"&gt;https://community.qlik.com/message/1410145#1410145&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Oracle Query used in identification of the odd data:&lt;/P&gt;&lt;P&gt;In the where clause:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Oracle part used on different data&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;length(asciistr(WHATEVERYOURCOLUMNISCALLED))!=length(WHATEVERYOURCOLUMNISCALLED)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 12 Jul 2018 21:49:43 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Troubleshooting-Error-QVX-UNEXPECTED-END-OF-DATA-SQL-f-SqlState/m-p/137703#M9694</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2018-07-12T21:49:43Z</dc:date>
    </item>
  </channel>
</rss>

