iodbctest fails on Fedora 28 i686 with the following output: iODBC Demonstration program This program shows an interactive SQL processor Driver Manager: 03.52.1216.0712 1: SQLDriverConnect = ���������������������������������������� (20009) SQLSTATE= 2: SQLDriverConnect = ���������������������������������������� (20013) SQLSTATE= 3: SQLDriverConnect = ���������������������������������������� (0) SQLSTATE= 1: ODBC_Connect = ���������������������������������������� (20009) SQLSTATE= 2: ODBC_Connect = ���������������������������������������� (20013) SQLSTATE= 3: ODBC_Connect = ���������������������������������������� (0) SQLSTATE= Have a nice day.[gjohnson@X4 ~]$ The tsql and isql command work fine so the odbc should be set up correctly. This first failed in Fedora 22. In the original release of Fedora 22, the iodbctest command worked correctly. However, one of the patches to Freetds caused this to fail. Version-Release number of selected component (if applicable): libiodbc.i686 3.52.12-5.fc28 How reproducible: iodbctest "DSN=database;UID=userid;PWD=password" Steps to Reproduce: 1.iodbctest "DSN=database;UID=userid;PWD=password" Actual results: See above Expected results: iODBC Demonstration program This program shows an interactive SQL processor Driver Manager: 03.52.0709.0909 Driver: 0.91 (libtdsodbc.so) SQL> Additional info:
I (personally) don't use libiodbc anymore, nor am in a position to help debug this, sorry. Constructively though, you have some options: Probably the best (and maybe only) way to get this addressed is to report this upstream at https://github.com/openlink/iODBC/issues In addition, since you noticed a change in freetds may be related to causing this, would not be a bad idea to contact freetds maintainers as well for input.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.