Alteryx error using inDB

[albert_alaluf]

Hello all,

I'm receiving an error when using inDB Teradata ODBC v16.x or v17.x. When my script is using '<' or '<>' operators it returns 

'Connect In-DB (1) Error parsing xml: Message=expected element name, Location=> (deleted field names)'

The same script works fine with Input Data method. This happens on my Designer 2022.3 and 2023.1 versions, as well as on the server 2022.3

I submitted a ticket with Alteryx and they were not able to replicate the issue. I tried another script in inDB SQL and worked fine. Same script works fine in Teradata.

I'm curious is there anybody else have the same problem? Because I have the issue on both server and my local computer, this shows the issue is not directly related to me.

This is the XML output and it looks fine for me. '>' operator works fine.

AND (C_A &lt;&gt; C_LSFDS) AND

Thanks

[danilang]

Hi @albert_alaluf 

It could be a particular issue with the ODBC driver that you're using.  Try using != instead of <>.  According to the TeraData documentation, this is accepted.

Dan

[albert_alaluf]

@danilang Unfortunately != is not working, it returns an error. I don't worry about this that much, I can use NOT IN instead. But, '<' is not working.

[albert_alaluf]

I decided to reopen my case with Alteryx support. 

Today I tested with Teradata ODBC 16.2. All worked fine with input data, but inDB is failed. This happens on both client and server. I run ODBC debug, provided to support.

[mttgbsn]

Did you ever get an answer to this albert? I am running into the same issue with Teradata. Non In-DB tools are running my queries successfully, but In-DB doesn't seem to allow <>, <=, or >= in teradata.

[BobbyD]

I'm encountering the same problem here with SQL Server - anyone got a solution?

[Brinker]

I am having the same issue with Athena in in-DB. The script works in Athena and in the normal input data tool.

I think the issue is with the generic odbc driver in the in-DB tool, it does not like some of the operators in the script and has trouble translating it from the generic odbc to Athena.

[DataNath]

Hey @Brinker - I replied to your post the other day, not sure if you missed it but if so:

I ran into this exact issue recently when querying Snowflake via the In-DB tools. I believe the problem is caused by the query not being escaped properly in terms of special XML characters (<> etc). I got around this by escaping them myself i.e. instead of <= or >= I would use &lt;= or &gt;= respectively. Escape characters found here: https://stackoverflow.com/questions/1091945/what-characters-do-i-need-to-escape-in-xml-documents. Hope this helps!

[mattnason1]

This is an old topic, but I ran into the same issue and the solution for me was pretty simple.

In my connection (within alteryx - update with manage connections) I unchecked DCM - Use Data Connection Manager (DCM).  Hopefully that saves someone a bit of time troubleshooting.

My snipping tool doesn't let me post in the community or I'd post images to show better.