Clob Data poor performance

[Sugu]

We encountered an issue with clob data.  Looks like alteryx is very slow performing while loading clob data to Oracle database. We need to figure a better way to handle the clob data.

[honeypot]

Yes when loading string values to our Oracle database, we first load into a TEMP table and then merge it into our FACT table, then drop the temp table.

When adding new fields to the workflow, sometime the workflow fails after running for a long time without writing any data. When we check the temp tablet that was created, NCLOB data types are seen and whenever these are present no data is written.

To fix this, usually we manually set the precision types in a Select tool right before the output tool. This happens when a field is too big, and when I check the precision that was automatically set by Alteryx when running, it is something huge. Manually setting it to 255 usually fixes this issue.

Sometimes, however, even with a precision set to 255 in Alteryx, the workflow will fail with an error stating that it is trying to insert something that is 256 length when the max field length in oracle is 255.

This has been very frustrating and only have found random solutions that sometimes work.

[vepp]

This is very important for DB's. Alteryx crashes when we use CLOB or takes huge time to load the  data even when we have just 2 records. This is core issue of the product.