Output JSON as CLOB to Teradata - Error
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
I have a flow that results in a two column table, one integer ID column, and a JSON object (text). At the step where we have an Output Data object to get this to Teradata, it results in an error:
Error: Output Data (4): Error SQLPrepare: [Teradata][ODBC Teradata Driver][Teradata Database] LOBs are not allowed to be selected in Record or Indicator modes.
We have other processes (that just execute SQL, nothing in Alteryx) that can load JSON into tables in Teradata just fine as CLOB, but no matter what method I try within Alteryx, that error still appears. Same error when using the Teradata Bulk Loader.
JSON Column type in Teradata:
JSON(2097152) INLINE LENGTH 64000 CHARACTER SET LATIN NOT NULL
I'm relatively new to Alteryx, so there is likely something simple that I'm missing. This error is really confusing because I'm not attempting to read anything from the table, just dump this data there in JSON form. Research on Record or Indicator modes in Teradata shows that neither is the default mode, and I don't see anything in the connection string or Output Data object that would change the mode.
Solved! Go to Solution.
- Labels:
- Database Connection
- Output
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
In the ODBC Driver settings, do you know if the box is checked for "Use Native Large Object Support" under options of the ODBC DSN?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Also have you tried using the SIMBA driver instead? https://help.alteryx.com/current/designer/teradata
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
"Use native large object support" almost didn't work - at first it started generating an internal Teradata error. One of our DBAs reached out and had me try it on a box they had set up with 16.20 (production is currently 16.10) and it worked like a charm! Thank you so much!
