We are testing one of our applications and some of tests fail with the following error
I would start, checking the "Session Character set" option in ODBC DSN. Does it appropriately set to match your character data?
the session character set is set to match the character data correctly. still the tests fail...are there any reported issues on the odbc dirvers ?
It seems that the Teradata Database generated the error:
"[Teradata Database] Unicode Conversion Error"
This application is using the "Microsoft .NET Data Provider for ODBC". Therefore the incoming data is Unicode and the Data will be passed to the Teradata Database without conversion when the session character set is UTF16.
If the issue persist with the UTF16 session character set; then you must check the column attributes; specifically the "Character Set" attribute (e.g. "Col1 VarChar(100) Character Set UNICODE").