I get the below error message in my workflow when doing any of the following: * Using the Filter Tool to peform any column based filter eg apply IS NOT NULL on a column * Using the Data Stream Out Tool to the standard select tool * Using the InDB Browse Tool Error: Data Stream Out (57): Error SQLPrepare: [Teradata][ODBC Teradata Driver][Teradata Database] The object name is too long in NFD/NFC.

In-Database Error - The object name is too long in NFD/NFC when connected to Teradata

I get the below error message in my workflow when doing any of the following:

Using the Filter Tool to peform any column based filter eg apply IS NOT NULL on a column
Using the Data Stream Out Tool to the standard select tool
Using the InDB Browse Tool

Error: Data Stream Out (57): Error SQLPrepare: [Teradata][ODBC Teradata Driver][Teradata Database] The object name is too long in NFD/NFC.

Workflow

Developer Tools

Error Message

Output

Common Use Cases

Accepted answers

FogoFortitude

I have discovered the problem

The object name is too long in NFD/NFC when connected to Teradata Error occurs when you use SQL comments above the SELECT statement within the Connect In-DB customer query box. Once the comments are removed the problem is resolved. Pity I cant use comments though.

All comments

FogoFortitude

I have discovered the problem

pancy

Have the same problem, Filter, Browser, give "the object name is too long in NFD/NFC" error

The exact sql query works fine in Teradata, used recursive query to get the hierarchy.

And I have removed all comments in sql.

What can be the other reasons?

Any thoughts?

Gary_Reeve

I've had various forms of this issue which fall into two categories:

Comments: just generally delete / move these from the top of the code

Tabs/spacing/etc: this can be misinterpreted

Solution: use another tool to check formatting (I use freeware Notepad++ ) and then copy over with no formatting clear spaces and no tabs

cheangvi

Hi,

I have tried to remove comments, extra blank lines for the Connect In-DB tool, but still get the same error in the Filter In-DB tool. Is there a characters limit to the SQL query?

The original query worked but I am making some changes to it.

Thanks in advance.

Cheers

Vivien

m1patri

Comments do not seem to create this error. I managed to get the error to generate by not having a [space] between my select statement and the next command. For example while using the syntax for select all: "Select*" - Error, "Select *" - No error. The missing space appears to confuse Alteryx but not an SQL interface. In addition I placed comments before the select statement using various syntax methods, I also placed them throughout the SQL editor and the comments did not appear to change the Error message result at all.

lakshmysatheesh

I had the same error. Try avoiding shortforms for select (sel) ,delete (del) ,etc.

It worked for me .

Thanks

Finally something worked for me. Thanks!

Quick Links

This months top contributors

mceleavey 383

AkimasaKajitani 382

mbarone 337

Hollingsworth 335

LanisC 335