Rob, if your organization has support from InterSystems, then there is usually one of your colleagues who manages the people who have WRC credentials.  They should be able either to download the driver you need or to request credentials for you.  If you think you should have credentials, or you forgot username/password, send a request to support@intersystems.com asking for credentials (use your organization's email).

Erik

Hi Gary,

If you have a default Docker installation, there is no daemon.json there until you create one to alter the default behavior of Docker.  This external post discusses it in more detail.

Post more about what you are trying to achieve if this doesn't answer your question, or contact the WRC.

Erik

Earlier ODBC driver versions should be compatible with Caché 2018.1, but we recommend updating clients to the latest driver for your Caché version.  There aren't any 2021.x ODBC drivers for Caché on the WRC download page.  If you have one and you want to be sure you have a good driver, reach out to the WRC so we can understand your specific situation.

Erik

Rob, the ODBC drivers for IRIS are not compatible with Caché and Ensemble.

Erik

Hi Hoi, nice to see you in the community. You piqued my curiosity about FASP and I found this white paper about it: https://www.ibm.com/downloads/cas/7D3KBL9Z.

I don't see any support for this in our class reference.  If you are looking for support for this in InterSystems IRIS, I would start with your InterSystems account team to explore what you need and what alternatives might serve.

Scott, the WRC may be able to help if you haven't resolved this.  The details will matter a lot (what VM/OS version/Docker version/etc.).

I have seen troubles on Ubuntu VMs under WSL2 using SysV init rather than systemd, which causes trouble with software that expects systemd.

Thiago, I would try downloading the latest image again.  The embedded license expired a short time ago and the image was refreshed.  If you continue to have trouble, reach out to the WRC for help.

Kevin, manually allocating space for a database file allows you to (as Alexander mentioned) avoid expansions on-the-fly.  In some applications that extra overhead isn't desirable when the system is running.  Pre-expanding the database also commonly results in a contiguous file on disk, which can improve performance of storage and backup operations.  There can be other reasons, too, why limiting the size of a database would be desirable.

Robert, +1 for Kepner-Tregoe ATS.  That was one of the first seminars I took as a new engineer, and it still ranks as some of the most-useful training I ever had.

@Bren Mochocki , the link worked for me today; downloading is back.  Try it again, please, and post back if you still have troubles.

Erik