MySQL Bugs: #56869: Unhandled exception: 'ascii' codec can't decode byte 0xc3 in position 25:

Bug #56869	Unhandled exception: 'ascii' codec can't decode byte 0xc3 in position 25:
Submitted:	20 Sep 2010 10:08	Modified:	29 Nov 2011 16:20
Reporter:	Pep Pla	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S2 (Serious)
Version:	5.2.28 CE	OS:	Windows (Windows7)
Assigned to:	Alfredo Kojima	CPU Architecture:	Any
Tags:	ASCII, dump, exception, workbench

Description:
Trying to export to disk some schemas the following message is displayed:
Unhandled exception: 'ascii' codec can't decode byte 0xc3 in position 25: ordinal not in range(128)

Status bar displays a message: Error in dump module: error calling WbAdmin.openExportImport: see output for details.

Start and Stop Export buttons are grayed.

I think this a duplicate of bug#55315 but my chinese is not that good (or is it japanese?)

How to repeat:
Server is installed on RedHat Enterprise Linux. Version 5.1.48-enterprise-gpl-adv.
Client is Windows7. Version installed is Workbench 5.2.28 CE.

Trying to dump the database the error appears.

Trying to export to disk some schemas the following message is displayed:
Unhandled exception: 'ascii' codec can't decode byte 0xc3 in position 25: ordinal not in range(128)

Status bar displays a message: Error in dump module: error calling WbAdmin.openExportImport: see output for details.

Start and Stop Export buttons are grayed.

Frustrating to see that bug#55315 was closed for such stupid formal reason.
It is fully understandable what reporter tells.

Looks like Workbench does not understand that in MySQL 5.1+ the full unicode character range may be used in identifiers.

@Pep: I think you should tell your locale and what that particular character is in this locale.

Peter
(not a MySQL person).

Hello Pep,
do you know what specific character triggers that problem? maybe you can add an example like Peter noted - would be great.
thanks in advance

I don't know which caracter triggers the error. The dump is not being done so I can't search for a 0xc3 byte in position 25.

If you have any idea about enabling a verbose mode or something like that, then maybe I'll be able to provide this kind of information.

Do you have any schema names with non-ascii characters?

This happens when schemas and tables have non-ascii characters in their names.

I think it is triggered when you try data export with non-ascii character in export path.

I met the same problem in korean.

Good Luck :)

Bug #57935 was marked as duplicate of this one

Please follow the discussion about this issue in bug #62767.

Fixed as of 5.2.36:
+        &workbench; did not fully adhere to locale settings, which could
+        result in unhandled exceptions.

Really the (only) problem here?

Now what if I have a database with identifiers in Czech language and is using a Western locale?

I had this same error when importing into workbench.

My database password (the one it asks for when your start import) contained a "£" character, I removed it and import worked fine.

So if your MySQL password has these type of characters try changing or removing it. 

Thanks

Mark
www.assertdesign.co.uk