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.
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.
I know this is not the proper way to do it, but I worked around this issue by deleting the line for zlib1g in the file, package/requirements_check/requirements.lnxubuntu2004arm64.isc.
Looks like the instance is working fine, so I suspect there is something wrong with requirement checking in installation.
Thanks. But looks like zlib1g is already installed..
$ sudo apt install zlib1g
Reading package lists... Done
Building dependency tree
Reading state information... Done
zlib1g is already the newest version (1:1.2.11.dfsg-2ubuntu1.2).
0 upgraded, 0 newly installed, 0 toremoveand 11 not upgraded.
Calling SetParameter() after saving the created domain worked perfectly.
I understand that working with Domain Definitions is more convenient in most cases, but I was looking for a way to deal with a situation where several domains need to be created by a user who is not so familiar with COS, and I thought it would be good to write code that creates a domain and feeds data.
go to post
Solved. This was due to network configuration and the Java Server settings.
go to post
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 -junixODBC 2.3.11DRIVERS............: /opt/homebrew/etc/odbcinst.iniSYSTEM DATA SOURCES: /opt/homebrew/etc/odbc.iniFILE DATA SOURCES..: /opt/homebrew/etc/ODBCDataSourcesUSER DATA SOURCES..: /Users/horita/.odbc.iniSQLULEN Size.......: 8SQLLEN Size........: 8SQLSETPOSIROW Size.: 8and sudo fs_usage isql | grep ini :
so it looks like the driver is reading the correct configuration files.
The log file shows:
and this looks like the problem. The error was the same in both HOST=localhost and HOST=127.0.0.1.
go to post
There was a typo in my code, and just copying the stream to the new call request worked as expected.
Thanks for your comment!
go to post
Ah.. That was it.
I was switching to root while building the image for installing jdk.. Adding 'USER irisowner' at the end of Dockerfile solved the issue. Thank you!
go to post
Thanks. I thought that was relevant, but even with the directory and files owned by 51773.52773, it failed with the same error.
It fails even without mounting a volume outside the container and no durable %SYS, so I was wondering if the image itself had the problem.
go to post
I tried to run the docker image on my Apple Silicon, but the docker run fails with the following error:
-----
[INFO] Executing command /home/irisowner/irissys/startISCAgent.sh 2188...
[INFO] Writing status to file: /home/irisowner/irissys/iscagent.status
Reading configuration from file: /home/irisowner/irissys/iscagent.conf
ISCAgent[18]: Starting
ISCAgent[19]: Starting ApplicationServer on *:2188
[INFO] ...executed command /home/irisowner/irissys/startISCAgent.sh 2188
[INFO] Copying InterSystems IRIS license key from /durable/iris.key to /usr/irissys/mgr...
[INFO] ...copied key
[INFO] Starting InterSystems IRIS instance IRIS...
[INFO] Invalid registry ownership
[ERROR] Command "iris start IRIS quietly" exited with status 256
[ERROR] See the above messages or /durable/iris/mgr/messages.log for more information
[FATAL] Error starting InterSystems IRIS
-----
I get the same error on Ubuntu ARM. I am using the image, containers.intersystems.com/intersystems/iris-arm64:2022.1.0.114.0.
go to post
I know this is not the proper way to do it, but I worked around this issue by deleting the line for zlib1g in the file, package/requirements_check/requirements.lnxubuntu2004arm64.isc.
Looks like the instance is working fine, so I suspect there is something wrong with requirement checking in installation.
go to post
Thanks. But looks like zlib1g is already installed..
$ sudo apt install zlib1g
Reading package lists... Done Building dependency tree Reading state information... Done zlib1g is already the newest version (1:1.2.11.dfsg-2ubuntu1.2). 0 upgraded, 0 newly installed, 0 to remove and 11 not upgraded.go to post
I was trying to install the preview version on Ubuntu 20.04.3 LTS ARM64(in a VM on Mac M1).
But irisintall gave the the following error. Installing zlib1g-dev did not solve the problem. Could anyone suggest me what I was missing?
-----
Your system type is 'Ubuntu LTS (ARM64)'.
zlib1g version 1 is required.
** Installation aborted **
go to post
Congratulations on achieving this milestone! Let's keep going!
go to post
みなさん、ありがとう！
We're very excited to be part of this global community. Look forward to talking to you in the Japanese Community !
go to post
Thanks, Benjamin.
I meant that the row I created through the API did not show up via SQL so that your explorer demo didn't work.
I checked the domain definition, and the allowCustomUpdates flag was true.
I will look and see if there is anything else that I am missing, and get back here..
go to post
Thanks, Benjamin.
Calling SetParameter() after saving the created domain worked perfectly.
I understand that working with Domain Definitions is more convenient in most cases, but I was looking for a way to deal with a situation where several domains need to be created by a user who is not so familiar with COS, and I thought it would be good to write code that creates a domain and feeds data.