In older versions of unixODBC this message might be:
"[Easysoft ODBC][unixODBC][Driver Manager]Can't initiate unicode conversion"
This ODBC diagnostic is from the unixODBC driver manager. This diagnostic may be returned by the unixODBC driver manager when calling SQLConnect, SQLDriverConnect or SQLBrowseConnect and results in a SQL_SUCCESS_WITH_INFO return. SQL_SUCCESS_WITH_INFO is not an error return, but some ODBC applications output informational diagnostics after connection. You should look at any subsequent diagnostics if your connection failed as this one does not cause connection failures. It means unixODBC was built with iconv support but it could not find a map in iconv. It is not a matter of concern for most people.
iconv support in unixODBC is used to translate ASCII to UNICODEand vice versa. If your application is not making UNICODE ODBC calls (SQLxxxW functions), and most do not, then you are not using iconv support anyway.
Some releases of OOB contain unixODBC which was built with iconv support unnecessarily. RedHat distribute unixODBC with iconv support. If you build unixODBC yourself then you will probably get iconv support by default. You can disable iconv support when configuring unixODBC using the configure option --enable-iconv=no.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates.