Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us in Bucharest on Sept 18th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
Architect
Partner - Creator
Partner - Creator

multi-byte character error

In my project, I have encountered one problem while loading data in QV app from the ODBC connection.
 
 Initially, I tried to connect with DB using below connection string,-->
"ODBC CONNECT TO [rt70-dareo;DBQ=rt70.XYZ.com] (XUserId is OTfWFMSLZeGBA, XPassword is BFDeDXFGUDdSXTJORBdIXK);" but having multibyte charecter error.
 
That is why I tried the below process.-->
 
"ODBC CONNECT TO [rt70-dareo;DBQ=rt70.XYZ.com] (XUserId is OTfWFMSLZeGBA, XPassword is BFDeDXFGUDdSXTJORBdIXK,CodePage is 65001);"--UTF-8
also I have used
"ODBC CONNECT TO [rt70-dareo;DBQ=rt70.XYZ.com] (XUserId is OTfWFMSLZeGBA, XPassword is BFDeDXFGUDdSXTJORBdIXK,CodePage is 20127);"--US-ASCII
 
Though, having the same error message.-->
 
"Error: QVX_UNEXPECTED_END_OF_DATA: SQL##f - SqlState: S1000, ErrorCode: 29275, ErrorMsg: [Oracle][ODBC][Ora]ORA-29275: partial multibyte character"
 
When investigating the data in Oracle that causes this error it is this string :
"ÂBATCH"
 
Most probably the “” is the reason behind the issue.
 
I am using qlik version 12.30.20000.0.

 
The current NLS character set in our Data Base is; AL16UTF16.
 
What our Client wants is to make the changes in QlikView end only to resolve the issue, without modifying the D
 
If you have any solution in your mind please let me know.
Labels (1)
11 Replies
Architect
Partner - Creator
Partner - Creator
Author

Thanks Brett.

The docs are very helpful.

Architect
Partner - Creator
Partner - Creator
Author

The issue got resolved by the below process I followed in Oracle 19c.

"maint.audit_0806test_tbr" was the table with corrupt data.

I did the below conversion on the responsible columns –

update maint.audit_0806test_tbr set OBJECT_SCHEMA=convert(OBJECT_SCHEMA,'US7ASCII','WE8ISO8859P1');

update maint.audit_0806test_tbr set OBJECT_NAME=convert(OBJECT_NAME,'US7ASCII','WE8ISO8859P1');

COMMIT;

While using the updated table maint.audit_0806test_tbr in QlikView.
Able to reload the data in QV from the temp table successfully.