Skip to main content

Upgrade Considerations

The following is important information to know before you begin the upgrade procedure.

Definitions Used in the Upgrade Description​

The following definitions are used in the upgrade procedure (in Upgrade Steps):

  • vCurrent refers to the currently installed version of Code Insight (for example, Code Insight 2022 R1.

  • vNew refers to the Code Insight version to which you are upgrading (for example, Code Insight 2025 R3).

  • catalina.* refers to the catalina.bat file on Windows systems or catalina.sh file on Linux systems

Instance Upgrade​

The Code Insight 2025 R3 instance (vNew) is installed in parallel to your current instance (vCurrent) such that no files are overwritten.

Database Upgrade​

info

Ensure that you perform a full backup of the database schema prior to upgrade.

Note the following about the database upgrade:

  • The Code Insight 2025 R3 instance will use your vCurrent database schema.

  • Database schema changes have occurred beginning with Code Insight 2020 R2 up to and including the current release, Code Insight 2025 R3.

  • As of Code Insight 2019 R2, all database migration is performed automatically when you start Tomcat. Manual execution of database migration scripts is required only if you are migrating from Code Insight 2018 R2 (or earlier) to the current release.

  • Code Insight uses the database user assigned to Code Insight in core.db.properties to migrate the database during an upgrade. This user already has the minimum permissions required to manage (and initially install) Code Insight. While these permissions are sufficient for migrating a MySQL database, the migration of a SQL Server database requires that the user have the db_ddladmin role. If the user in core.db.properties is not currently assigned this role, add the role before the performing the upgrade. If necessary, you can revoke this role once the upgrade completes.

  • With the introduction of the View History feature for inventory in 2021 R3, an upgrade to the current version of Code Insight might take longer than previous upgrades, especially if the number of inventory items in your Code Insight system has increased since the last upgrade. For example, the upgrade for a system with about 1 million inventory items can now take around 15-20 minutes, which might be longer than your previous upgrades.

    • The extra time required for the upgrade is due to the processing of inventory items in all projects to ensure that the inventory is included in the history. However, once an inventory item is added to the history, it does not need to go through this initialization process in subsequent upgrades.
    note

    Even though the processing time for the database upgrade might be significant, Tomcat should never be restarted during this process. If you have any concerns about the processing time, contact Revenera Support for assistance.

Upgrade Limitations​

For any limitations or known issues related to the upgrade process, refer to the latest version of the Code Insight Release Notes.