User bio
404 bio not found
Member since Dec 28, 2015
Posts:
Replies:
I installed the driver by downloading ODBC-2023.1.0.229.0-macos.tar.gz from the community github repo. I am not sure *-macos.tar.gz is for Apple Silicon.
odbcinst -j gives:
$ odbcinst -j
unixODBC 2.3.11
DRIVERS............: /opt/homebrew/etc/odbcinst.ini
SYSTEM DATA SOURCES: /opt/homebrew/etc/odbc.ini
FILE DATA SOURCES..: /opt/homebrew/etc/ODBCDataSources
USER DATA SOURCES..: /Users/horita/.odbc.ini
SQLULEN Size.......: 8
SQLLEN Size........: 8
SQLSETPOSIROW Size.: 8
and sudo fs_usage isql | grep ini :
15:36:23 open /opt/homebrew/etc/odbcinst.ini 0.000021 isql
15:36:23 open /Users/horita/.odbcinst.ini 0.000012 isql
15:36:23 open /opt/homebrew/etc/odbcinst.ini 0.000021 isql
15:36:23 open /Users/horita/.odbcinst.ini 0.000003 isql
15:36:23 open /Users/horita/.odbc.ini 0.000024 isql
15:36:23 open /Users/horita/.odbc.ini 0.000011 isql
15:36:23 open /opt/homebrew/etc/odbc.ini 0.000015 isql
15:36:23 open /opt/homebrew/etc/odbc.ini 0.000011 isql
15:36:23 open /opt/homebrew/etc/odbcinst.ini 0.000015 isql
15:36:23 open /Users/horita/.odbcinst.ini 0.000003 isql
15:36:23 open /opt/homebrew/etc/odbcinst.ini 0.000011 isql
15:36:23 open /Users/horita/.odbcinst.ini 0.000002 isql
15:36:23 open /Users/horita/.odbc.ini 0.000010 isql
15:36:23 open /Users/horita/.odbc.ini 0.000010 isql
15:36:23 open /opt/homebrew/etc/odbc.ini 0.000010 isql
15:36:23 open /opt/homebrew/etc/odbc.ini 0.000009 isql
15:36:23 open /Users/horita/.odbc.ini 0.000010 isql
15:36:23 open /Users/horita/.odbc.ini 0.000009 isql
15:36:23 open /opt/homebrew/etc/odbc.ini 0.000009 isql
15:36:23 open /opt/homebrew/etc/odbc.ini 0.000009 isql
15:36:23 open /Users/horita/.odbc.ini 0.000009 isql
15:36:23 open /Users/horita/.odbc.ini 0.000008 isql
15:36:23 open /opt/homebrew/etc/odbc.ini 0.000009 isql
15:36:23 open /opt/homebrew/etc/odbc.ini 0.000008 isql
15:36:23 open /opt/homebrew/etc/odbcinst.ini 0.000010 isql
15:36:23 open /Users/horita/.odbcinst.ini 0.000002 isql
15:36:23 open /opt/homebrew/etc/odbcinst.ini 0.000009 isql
15:36:23 open /Users/horita/.odbcinst.ini 0.000002 isql
15:36:23 open /opt/homebrew/etc/odbcinst.ini 0.000009 isql
15:36:23 open /Users/horita/.odbcinst.ini 0.000002 isql
15:36:23 open /opt/homebrew/etc/odbcinst.ini 0.000010 isql
15:36:23 open /Users/horita/.odbcinst.ini 0.000002 isql
15:36:23 open /opt/homebrew/etc/odbcinst.ini 0.000010 isql
15:36:23 open /Users/horita/.odbcinst.ini 0.000002 isql
15:36:23 open /opt/homebrew/etc/odbcinst.ini 0.000009 isql
15:36:23 open /Users/horita/.odbcinst.ini 0.000002 isql
15:36:23 open /opt/homebrew/etc/odbcinst.ini 0.000010 isql
15:36:23 open /Users/horita/.odbcinst.ini 0.000002 isql
15:36:23 open /opt/homebrew/etc/odbcinst.ini 0.000010 isql
15:36:23 open /Users/horita/.odbcinst.ini 0.000002 isql
15:36:23 open /opt/homebrew/etc/odbcinst.ini 0.000008 isql
15:36:23 open /Users/horita/.odbcinst.ini 0.000002 isql
15:36:23 open /opt/homebrew/etc/odbcinst.ini 0.000009 isql
15:36:23 open /Users/horita/.odbcinst.ini 0.000002 isql
15:36:23 open private/etc/odbc.ini 0.000017 isql
15:36:23 open private/etc/odbc.ini 0.000009 isql
15:36:23 open private/etc/odbc.ini 0.000009 isql
15:36:23 open private/etc/odbc.ini 0.000007 isql
15:36:23 open private/etc/odbc.ini 0.000008 isql
15:36:23 open private/etc/odbc.ini 0.000008 isql
so it looks like the driver is reading the correct configuration files.
The log file shows:
--> SQLConnect: (05/22/23-15:36:23:501) hdbc = 0x138020000
DSN: user
USERNAME: (null)
ERROR: Connect: (05/22/23-15:36:23:501) Connect via irisconnect returned: 0x8 , getaddrinfo(, , 0, 0) failed in s_TCPConnect, reason = nodename nor servname provided, or not known.
<-- SQLConnect: (05/22/23-15:36:23:501) Returning -1
and this looks like the problem. The error was the same in both HOST=localhost and HOST=127.0.0.1.
There was a typo in my code, and just copying the stream to the new call request worked as expected.
Thanks for your comment!
Certifications & Credly badges:
Global Masters badges:
Followers:
Minoru has no followers yet.
Following:
Minoru has not followed anybody yet.
Solved. This was due to network configuration and the Java Server settings.