What does "[Easysoft ODBC][unixODBC][Driver Manager]Can't initiate unicode conversion" mean?

The unixODBC Driver Manager may return this diagnostic message when calling SQLConnect, SQLDriverConnect, or SQLBrowseConnect and results in a SQL_SUCCESS_WITH_INFO return value. This is not an error. The message means that unixODBC was built with iconv support, but could not find a conversion map in iconv. It's not a matter of concern for most people.

iconv support in unixODBC is used to translate ASCII to UNICODE and vice versa. If your application is not making UNICODE ODBC calls (SQLxxxW functions), and most do not, you're not using iconv in unixODBC anyway.

Some releases of the Easysoft ODBC-ODBC Bridge contain a unixODBC Driver Manager that was built with iconv support unnecessarily. Red Hat distribute unixODBC with iconv support. If you build unixODBC yourself, you'll probably get iconv support by default. You can turn off iconv support when configuring a unixODBC build using the configure option --enable-iconv=no.