Post-Upgrade Tasks
The post-upgrade tasks required depend on whether you have upgraded to a new major version or to a maintenance release of the installed version. Also note the following points:
-
If you changed an instance from 8–bit to Unicode during the upgrade, the upgrade does not automatically convert your databases. 8–bit databases may be compatible with Unicode in some cases (see Database Compatibility Considerations). If your locale is not compatible, you will need to manually convert the data from 8–bit to Unicode.
-
It is not necessary to re-import any OpenAPI 2.0 specificationOpens in a new tab files.
-
It is not necessary to re-import any Web Service Definition (WSDL) files.
-
Cached queries are always purged during upgrade. They are recompiled and cached as needed.
-
If you did not configure your web server automatically during the installation process, you will need to connect it manually.
-
If your web server is using a port number other than 80, you will need to change the CPF WebServerPort and WebServerURLPrefix parameters to your web server’s port number in order to connect with your IDE.
-
If you upgraded from an instance with a private web server (2023.1 or older), you should disable and remove the private web server.
-
If you are on Linux or AIX® and are using huge or large pages, confirm that they are still being used:
In the <install-dir>/mgr/messages.log file, confirm there is a message indicating shared memory has been allocated using huge or large pages.
If huge/large pages are not enabled, you may need to adjust the allocation to account for increases in shared memory with the new version. After reallocating, restart your system to allow the changes to take effect. See Configuring Huge and Large Pages for details on this process.
Maintenance Release Post-Upgrade Tasks
When the upgrade is complete, if your system runs any productions, follow the instructions in the Starting a Production section of the “Starting and Stopping Productions” chapter in Managing Productions to restart the productions.
Typically, maintenance release upgrades do not require you to change external files and clients, or to recompile classes and routines.
If you choose to recompile, review the information in the Major Version Post-Installation Tasks section.
Major Version Post-Installation Tasks
After upgrading to a new major version, it is important to follow the guidance provided in Special Considerations When Upgrading. You must also perform the following tasks (if you have not already done so as part of one of the previous procedures in this chapter):
InterSystems recommends that customers recompile all classes and all routines in each namespace. See How to Compile Namespaces for instructions. You may have your own tools and procedures for this purpose, taking into account any dependencies and other needs particular to the instance that was upgraded.
When you recompile a package, the class compiler automatically removes any classes that are marked deployed from that package, so it is necessary to reinstall those classes.
The %SYS namespace is skipped by default when compiling all classes and routines. Make sure you recompile the custom classes and routines in this namespace as well. See How to Compile Namespaces for instructions. Only classes and routines beginning with Z, z, %Z, or %z are preserved on upgrade. These classes and routines cannot be precompiled.
You must regenerate any proxy classes you had generated in the upgraded instance by following the instructions in the appropriate guides in the InterSystems IRIS Language Bindings set.
This item does not apply to web services and web clients; it is not necessary to re-import any Web Service Definition (WSDL) files.
If your instance is not running in Adaptive Mode, your query plans are frozen after upgrading. See Frozen Plans After Software Version Upgrade for details.
If your system runs any productions, follow the instructions in the Starting a Production section of the “Starting and Stopping Productions” chapter in Managing Productions.
If your Web Gateway is on a separate machine from the server you are upgrading, you must also upgrade the Web Gateway on that separate machine. You can accomplish this by following the Windows Upgrade Procedure in this chapter, or performing a silent installation with the ADDLOCAL property as discussed in Windows Unattended Installation.
Following upgrades you must deploy these using established practices at your site.
