Upgrade to Collibra Platform Self-Hosted

This section describes how you can upgrade an on-premises Collibra Data Governance Center 5.9.1 to Collibra Platform Self-Hosted 2025.10.

Important  If your environment is configured with repository clusters, make sure that you have executed this procedure before you start the upgrade.

Steps

  1. Stop the environment:
    1. Open Collibra Console with a user profile that has at least the ADMIN role.Collibra Console opens with the Infrastructure page.
    2. Click the environment that you want to stop.
    3. Click Stop.
      The Stop environment dialog box appears.
    4. Click Stop environment.
    5. Wait until all the nodes of the environment have the status Stopped.
    6. Stop Collibra Console and the Collibra DGC Agent. In the terminal of the node that runs Collibra Console:
      1. As root:
        service collibra-agent stop
service collibra-console stop
      2. Manual stop of the services: 
        /opt/collibra/console/bin/console stop
/opt/collibra/agent/bin/agent stop
  2. Start the installer and follow the instructions.
    Note 
    • The path to the most stable version of PostgreSQL 14.xx installation differs per Linux operating system. In the following example, the path is of a default installation on Red Hat, Rocky Linux, or CentOS.
    • The amount of time it takes to upgrade your environment depends on the size of your repository. The larger the database, the more time it takes to upgrade.
    # ./dgc-linux-2025.10.0.sh 
Verifying archive integrity...  100%   All good.
Uncompressing DGC Installer  100%  
Specify the installation directory [/opt/collibra]:

/opt/collibra contains a previous installation. Do you want to perform an update? [y/N]
y
Before you can schedule an upgrade, you need to:
 - Create a backup of the entire environment.
 - In Collibra Console, stop all running services on this node.
Have you completed these steps? [yes,NO]

yes
2023-10-16 10:32:51.581 - SUCCESS - Check umask settings
2023-10-16 10:32:51.592 - SUCCESS - Create installation and data directories
2023-10-16 10:32:51.597 - SUCCESS - Check Search system requirements
2023-10-16 10:32:52.030 - SUCCESS - Remove Agent system service
2023-10-16 10:32:52.280 - SUCCESS - Remove Console system service
2023-10-16 10:32:54.773 - SUCCESS - Extract JRE
2023-10-16 10:32:54.893 - SUCCESS - Copy server files
2023-10-16 10:32:54.894 - SUCCESS - Create PostgreSQL temporary directories
2023-10-16 10:32:54.896 - SUCCESS - Move old postgresql files to temporary directory
2023-10-16 10:32:54.897 - SUCCESS - Install PostgreSQL configuration files to temporary directory
2023-10-16 10:33:12.658 - SUCCESS - Update postgresql
2023-10-16 10:33:12.706 - SUCCESS - Update postgresql path in configuration files
2023-10-16 10:33:12.711 - SUCCESS - Remove tracing directories
2023-10-16 10:33:12.790 - SUCCESS - Prepare for jobserver update
2023-10-16 10:33:12.790 - SUCCESS - Create spark directories
2023-10-16 10:33:14.324 - SUCCESS - Extract Spark
2023-10-16 10:33:14.333 - SUCCESS - Replace variables in spark files
2023-10-16 10:33:14.342 - SUCCESS - Set permissions on Spark directory

    ...

    2023-10-16 10:33:36.422 - SUCCESS - Create installation configuration file
2023-10-16 10:33:36.468 - SUCCESS - Create uninstall script
2023-10-16 10:33:36.473 - SUCCESS - Cleanup temporary directories
2023-10-16 10:33:36.474 - SUCCESS - Cleanup old Postgres binaries
2023-10-16 10:33:36.679 - SUCCESS - Make sure all permissions are correct
2023-10-16 10:33:37.089 - SUCCESS - Install Agent system service
2023-10-16 10:33:37.312 - SUCCESS - Install Console system service
2023-10-16 10:33:41.431 - SUCCESS - Start Agent
2023-10-16 10:33:45.620 - SUCCESS - Start Console
2023-10-16 10:33:45.620 - COMPLETED - Installation finished in 54352ms.
    Note 
    • If you have a multi-node installation, repeat this step on every node of the environment until you have upgraded all nodes.
    • If you have a node that only runs the Monitoring service, you don't have to upgrade that node.
  3. Start the environment:
    1. Open Collibra Console with a user profile that has at least the ADMIN role.

      Collibra Console opens with the Infrastructure page.

    2. Click the name of an environment to show its details.
    3. Remove the Monitoring service from the environment if it is still available. If this service was installed on a dedicated node, you can remove that node too.

      Tip If the Monitoring service was installed together with other services, the Monitoring service is automatically removed during the upgrade.

    4. Click Start.
  4. Reindex Collibra.
  1. Stop the environment.
    1. Open Collibra Console with a user profile that has at least the ADMIN role.Collibra Console opens with the Infrastructure page.
    2. Click the environment that you want to stop.
    3. Click Stop.
      The Stop environment dialog box appears.
    4. Click Stop environment.
    5. Wait until all the nodes of the environment have the status Stopped.
    6. Stop Collibra Console and the Agent via the Windows services window. The services to be stopped are Agent and Management Console.
  2. In the command prompt, start the installer: setup.bat.
    Note 
    • The amount of time it takes to upgrade your environment depends on the size of your repository. The larger the database, the more time it takes to upgrade.
    # ./setup.bat 
Verifying archive integrity...  100%   All good.
Uncompressing DGC Installer  100%  
Specify the installation directory [C:\collibra]:

C:\collibra contains a previous installation. Do you want to perform an update? [y/N]
y
Before you can schedule an upgrade, you need to:
- Create a backup of the entire environment.
- In Collibra Console, stop all running services on this node.
Have you completed these steps? [yes,NO]

yes
2023-10-16 10:32:51.592 - SUCCESS - Create installation and data directories
2023-10-11 11:43:17.841 - SUCCESS - Stop Agent
2023-10-16 10:32:52.030 - SUCCESS - Remove Agent system service
2023-10-11 11:43:22.368 - SUCCESS - Stop Console
2023-10-16 10:32:52.280 - SUCCESS - Remove Console system service
2023-10-16 10:32:54.773 - SUCCESS - Extract JRE
2023-10-16 10:32:54.893 - SUCCESS - Copy server files

    ...

    2023-10-16 10:33:36.422 - SUCCESS - Create installation configuration file
2023-10-16 10:33:36.468 - SUCCESS - Create uninstall script
2023-10-16 10:33:36.473 - SUCCESS - Cleanup temporary directories
2023-10-11 11:45:24.755 - SUCCESS - Cleanup obsolete installation files
2023-10-11 11:45:24.757 - SUCCESS - Cleanup legacy installation files
2023-10-16 10:33:36.474 - SUCCESS - Cleanup old Postgres binaries
2023-10-16 10:33:37.089 - SUCCESS - Install Agent system service
2023-10-16 10:33:37.312 - SUCCESS - Install Console system service
2023-10-16 10:33:41.431 - SUCCESS - Start Agent
2023-10-16 10:33:45.620 - SUCCESS - Start Console
2023-10-16 10:33:45.620 - COMPLETED - Installation finished in 54352ms.
    Note 
    • If you have a multi-node installation, repeat this step on every node of the environment until you have upgraded all nodes.
    • If you have a node that only runs the Monitoring service, you don't have to upgrade that node.
  3. Start the environment:
    1. Open Collibra Console with a user profile that has at least the ADMIN role.Collibra Console opens with the Infrastructure page.
    2. Click the name of an environment to show its details.
    3. Remove the Monitoring service from the environment if it's still available. If this service was installed on a dedicated node, you can remove that node too.

      Tip If the Monitoring service was installed together with other services, the Monitoring service is automatically removed during the upgrade.

    4. Click Start.
  4. Reindex Collibra.