Issue
Corrupted Data when writing to a CLOB using OCI and ODBC
Example:
Text Input Tool with one column with value with Umlaut (letters with two dots above like ä, ë, Ä): Financiële
Add Select Tool to change the data type of the column and add an Output Data Tool to update the table with CLOB field.
- When writing a V_STRING, V_WSTRING, WSTRING value to a CLOB field using OCI, the written data is corrupted. Also, the Output Data Tool shows the value incorrectly.
NOTE: On Designer versions 2021.1 or 2021.2 you could also get spaces between all characters (like: F i n a n c i □ l e) or you could get garbage (like: i n e _ 1 3 8 1 6 _ 2 4 c 4 d 1 7 a b d a 1 4 3 6 3 8 d d 3 b 6 6 5 f 0 e 0 2 b)
- When writing a V_STRING value to a CLOB field using ODBC, the written data is corrupted. When writing a V_WSTRING, WSTRING value to a CLOB field using ODBC, the written data is correct. In both cases the Output Data Tool shows the value incorrectly.
- Alteryx Designer
- Version(s) 2021.1, 2021.2, 2021.3
- Oracle
Defect TDCB-1610
Defect TDCB-1610/TDCE-262 is fixed in version 2023.2.
Workaround
Use ODBC and add a Select tool to change the data type to V_WSTRING, WSTRING value.