EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB289087: SQL Statements containing Line Feed fail when using Teradata ODBC Driver version 15.10 in a DSN-less connection in MicroStrategy Secure Enterprise Platform 10.x


Community Admin

• Strategy


If the user is using DSN-less connection to connect to the Database, and also has upgraded to using the Teradata ODBC Driver version 15.10.x, then there is an existing issue in MicroStrategy 10.x that prevents the user from executing SQL statements or pick tables for analysis.

SYMPTOM
If the user is using DSN-less connection to connect to the Database, and also has upgraded to using the Teradata ODBC Driver version 15.10.x, then there is an existing issue in Strategy 10.x that prevents the user from executing SQL statements or pick tables for analysis.
This issue is seen in Data Import/Web interface. When picking tables for the project and clicking on ‘Prepare Data’, it will throw the following error message:

ka04W000000Oee5QAC_0EM4400000029Ca.jpeg

 
Same error message will also be seen when the SQL is executed in the “Build a query” option in Data Import. The generated SQL can have multiple separate-line-feeds in the statements, and this throws an error message. Example for a sample SQL and the error message is below:


select CUST_CITY_ID,
           CALL_CTR_ID,
 from   CITY_CTR_SLS;

ka04W000000Oee5QAC_0EM4400000029Cc.jpeg

 
WORKAROUND
The Work-around for this issue is to use the older version of the Teradata ODBC driver (version 15.0.x or earlier).
 
SOLUTION
Teradata is planning on issuing an e-fix to ODBC 15.10.xx.xx in 2Q 2016, and add that into the upcoming ODBC 16.00.xx.xx driver
 
The Strategy Internal Reference number for the issue referenced in this technica note is DE18555.


Comment

0 comments

Details

Knowledge Article

Published:

June 8, 2017

Last Updated:

June 8, 2017