Skip to main content

Upgrading or Modifying UNIX®, Linux, and macOS

This section describes the procedure to upgrade a single instance of InterSystems IRIS, InterSystems IRIS for Health, or HealthShare HealthConnect. Before proceeding, be sure to perform the tasks in the Before Upgrading section of this chapter. If you are upgrading a mirror or ECP configuration, also review the information in the Upgrading a Mirror and Upgrading ECP Configurations sections of this chapter.

If you are using a manifest as part of your upgrade process, see the instructions in Creating and Using an Installation Manifest before performing the standard installation steps.


Prior to beginning an upgrade of an instance, it is essential that the instance be shut down cleanly. To verify that the shutdown was clean, examine the messages.log file after the shutdown finishes. If the log contains entries similar to the following, then the shutdown was clean:

05/03/19-14:24:13:234 (5204) 0 Journal restore not required at next startup
05/03/19-14:24:13:234 (5204) 0 Transaction rollback not required at next startup

If these entries are not present, the instance did not shut down cleanly. Please contact the InterSystems Worldwide Response CenterOpens in a new tab before proceeding with the upgrade.

UNIX®, Linux, and macOS Upgrade Procedure

The installation script, irisinstall, provides all the functionality required to upgrade to a new version of InterSystems IRIS. To instead perform a silent upgrade, review the information in the UNIX®, Linux, and macOS Unattended Installation section of the “Installing on UNIX®, Linux, and macOS” chapter of this guide.


If the profile of the user executing irisinstall has a value set for the CDPATH variable, the upgrade fails.

To perform the upgrade:

  1. If your installation kit is in the form of a .tar file, you must first uncompress it (see Uncompress the Installation Kit).

  2. As a user with root privileges, start the installation procedure by running the irisinstall script, located at the top level of the installation files:

    # sudo sh /<pathname>/irisinstall

    where <pathname> is the location of the installation kit, typically the temporary directory to which you have extracted the kit.

  3. The script displays a list of all existing InterSystems IRIS instances on the host.

  4. At the Enter instance name: prompt, type the name of the InterSystems IRIS instance you want to upgrade, and press Enter.

  5. When prompted for a license key file, type keypath\iris.key, where keypath is the location of the new iris.key file. If the installation script detects the new license key in the install-dir/mgr directory, the script proceeds without prompting you for the license key file.

  6. If a local web server is detected, you will be asked if you would like to use the web server to connect to your installation. If you enter y, the web server will be connected automatically. If you enter n, the web server will not be connected automatically and you will have to configure it manually after the installation finishes. If a web server is not detected, you will be asked if you would like to abort. If you choose to continue the installation, you will have to configure your web server manually after the installation finishes.


    InterSystems recommends using the Apache httpd web server because it can be automatically configured during the upgrade process. Make sure it is installed and running before beginning the upgrade process. In most cases, it is not necessary to manually configure the Apache web server.

  7. The installation script summarizes the upgrade options and again asks you to confirm the upgrade. Press Enter to continue with the upgrade.


    Do not interrupt the installation while it is in progress. If the upgrade fails with any error messages, correct the issues and restart the upgrade installation.

  8. Examine messages.log, iboot.log, and ensinstall.log in the install-dir/mgr directory for any errors. If any fatal error is found, correct the error, and then run the installation script again.

After the upgrade finishes, the instance restarts and any installation manifest is run.


If your operating system is configured to use huge memory pages, check the startup messages to make sure shared memory is being allocated in accordance with these settings. If you see a message similar to the following, reboot your server to avoid an out-of-memory situation.

Failed to allocate 1468MB shared memory using Huge Pages. Startup will retry with standard pages.

Uninstalling on UNIX®, Linux, and macOS

To safely uninstall InterSystems IRIS, follow this procedure:

  1. Find the name of the InterSystems IRIS instance you wish to delete using the iris list command to list all the instances on your machine:

    iris list
  2. Verify the instance is stopped. If it is not, stop it with the iris stop command:

    iris stop <instname>

    Where instname is the instance name that you chose during the installation. If it hangs, force it down using iris force:

    iris force <instname>
  3. Remove the instance using the iris delete command:

    iris delete <instname>
  4. Remove the installation directory using the following operating system command:

    rm -r <directory>

    Be aware that this removes files you may wish to keep. For example: the license key (iris.key), the configuration file (iris.cpf), and the user database file (iris.dat).

The uninstall procedure removes all files installed and created during normal InterSystems IRIS processing, including journal and temporary database files.


The SUSE Linux Enterprise Server 9 platform uses asynchronous scriptlets, so the uninstall process cannot guarantee that InterSystems IRIS stops before it removes files.

FeedbackOpens in a new tab