> For the complete documentation index, see [llms.txt](https://docs.collibra.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.collibra.com/data-quality-self-hosted/installation/upgrade-data-quality-observability-self-hosted/upgrade-collibra-data-quality-observability.md). # Upgrade Collibra Data Quality & Observability {% tabs %} {% tab title="Standalone" %} {% hint style="info" %} Before proceeding with any upgrades, [back up your Collibra DQ metastore](/data-quality-self-hosted/installation/upgrade-data-quality-observability-self-hosted/prepare-your-environment-for-an-upgrade/create-and-restore-a-backup.md). {% endhint %} {% hint style="danger" %} Rolling back Collibra DQ to an older version is not supported. Please contact [Collibra Support](https://support.collibra.com) with any questions. {% endhint %} {% hint style="warning" %} Data Quality & Observability (self-hosted) 2026.07 and newer require Java 21 and Spark 4.1.0. Data Quality & Observability (self-hosted) 2026.02 through 2026.06 require Java 17 and Spark 4.1.0. For Data Quality & Observability (self-hosted) versions 2025.08 through 2026.01, you must upgrade to Java 17 and Spark 3.5.6. For more information about version compatibility, click "Java and Spark compatibility matrix" below.

Java and Spark compatibility matrix

| Data Quality & Observability (self-hosted) version | Java 11 | Java 17 | Java 21 | Spark versions | Additional notes | | -------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------- | ----------------------------------------------------------------------------------------------------- | | 2025.08 |

No |

Yes |

No |

Yes |

No |

Yes |

No |

Yes | 4.1.0 only | |

{% endhint %} ## Download the Collibra DQ Upgrade Package {% hint style="info" %} All Collibra DQ customers upgrading or patching receive the full package, not the base package, and should follow the same upgrade steps described in this section. {% endhint %} You can download the DQ installation package from the [Collibra Product Resource Center](https://productresources.collibra.com/downloads/?query=1#data-quality). {% hint style="info" %} For additional download options, contact your Account Team. {% endhint %} Save the package in a directory on the CDQ VM. Extract the file: ``` tar -xvf dq-full-package.tar.gz ``` (Optional) Clean up: ``` rm dq-full-package.tar.gz ``` ## Upgrade steps {% hint style="warning" %} Verify the Data Quality & Observability (self-hosted) version from which you are upgrading before proceeding with the upgrade. To do this, sign into your Collibra DQ instance and click the

in the upper-right corner of any page. The **App Version** lists your current Collibra DQ version. {% endhint %} *** **Upgrade with Java 21 packages** {% stepper %} {% step %} Copy the contents of the provided package, for example, dq-\-\-package-full.tar.gz to the system being upgraded (extract contents). {% hint style="success" %} Untar the contents into a uniquely named folder, for example *2025-02-dq-upgrade*. {% endhint %} {% endstep %} {% step %} Stop the Collibra DQ Web process. ``` cd /owlhome/owl/bin ./owlmanage.sh stop=owlweb ``` {% endstep %} {% step %} Stop the Collibra DQ Agent process. ``` cd /owlhome/owl/bin ./owlmanage.sh stop=owlagent ``` {% endstep %} {% step %} Move the old jars from the **owl/bin** folder. ``` mv dq-webapp--.jar /tmp mv dq-agent--.jar /tmp mv dq-core--.jar /tmp ``` {% endstep %} {% step %} Copy the new jars into the **owl/bin** folder from the extracted package. ``` mv dq-webapp--.jar /home/owldq/owl/bin mv dq-agent--.jar /home/owldq/owl/bin mv dq-core--.jar /home/owldq/owl/bin ``` {% endstep %} {% step %} Copy the latest `owlcheck` and `owlmanage.sh` to **/opt/owl/bin** directory. ``` mv owlcheck /home/owldq/owl/bin mv owlmanage.sh /home/owldq/owl/bin ``` {% endstep %} {% step %} Start the Collibra DQ Web application. ``` ./owlmanage.sh start=owlweb ``` {% endstep %} {% step %} Start the Collibra DQ Agent. ``` ./owlmanage.sh start=owlagent ``` {% endstep %} {% step %} Validate the number of active services. ``` ps -ef | grep owl ``` {% endstep %} {% step %} Restart the Collibra DQ Web and Collibra DQ Agent services. ``` ./owlmanage.sh stop=owlweb ./owlmanage.sh stop=owlagent ./owlmanage.sh start=owlweb ./owlmanage.sh start=owlagent ``` {% hint style="warning" %} If you use file-based SAML authentication with the `SAML_METADATA_USE_URL` variable set to `true` in the owl-env.sh script, update the Meta-Data URL option on the SAML Security Settings page with your metadata file. Use the **file:/opt/owl/config/idp-metadata.xml** format, ensuring the file name begins with the prefix **file:**. For additional steps on how to configure this, go to the "Enable the SAML SSO sign in option" section in [Configuring SAML authentication](/data-quality-self-hosted/security-configuration/saml-authentication/configuring-saml-authentication.md). {% endhint %} {% endstep %} {% endstepper %} *** **Upgrade with Java 17 packages** {% stepper %} {% step %} Copy the contents of the provided package, for example, dq-\-\-package-full.tar.gz to the system being upgraded (extract contents). {% hint style="success" %} Untar the contents into a uniquely named folder, for example *2025-02-dq-upgrade*. {% endhint %} {% endstep %} {% step %} Stop the Collibra DQ Web process. ``` cd /owlhome/owl/bin ./owlmanage.sh stop=owlweb ``` {% endstep %} {% step %} Stop the Collibra DQ Agent process. ``` cd /owlhome/owl/bin ./owlmanage.sh stop=owlagent ``` {% endstep %} {% step %} Move the old jars from the **owl/bin** folder. ``` mv dq-webapp--.jar /tmp mv dq-agent--.jar /tmp mv dq-core--.jar /tmp ``` {% endstep %} {% step %} Copy the new jars into the **owl/bin** folder from the extracted package. ``` mv dq-webapp--.jar /home/owldq/owl/bin mv dq-agent--.jar /home/owldq/owl/bin mv dq-core--.jar /home/owldq/owl/bin ``` {% endstep %} {% step %} Copy the latest `owlcheck` and `owlmanage.sh` to **/opt/owl/bin** directory. ``` mv owlcheck /home/owldq/owl/bin mv owlmanage.sh /home/owldq/owl/bin ``` {% endstep %} {% step %} Start the Collibra DQ Web application. ``` ./owlmanage.sh start=owlweb ``` {% endstep %} {% step %} Start the Collibra DQ Agent. ``` ./owlmanage.sh start=owlagent ``` {% endstep %} {% step %} Validate the number of active services. ``` ps -ef | grep owl ``` {% endstep %} {% step %} {% hint style="warning" %} If you are installing a Data Quality & Observability (self-hosted) version 2025.02 or newer, you only need to follow steps 10a and 10b once. For instance, if you performed these steps while upgrading to 2025.02, you do not need to follow them again when you upgrade to 2025.03. These steps are not required for Data Quality & Observability (self-hosted) 2025.01 or older. {% endhint %} 1. Add the following environment variable to the owl-env.sh file.

If you already have this variable set, you need to update it to include the following values.

``` export EXTRA_JVM_OPTIONS="--add-opens java.base/java.util=ALL-UNNAMED --add-opens java.base/java.net=ALL-UNNAMED --add-opens java.base/sun.nio.ch=ALL-UNNAMED --add-opens java.base/java.nio=ALL-UNNAMED --add-opens java.base/sun.util.calendar=ALL-UNNAMED" ``` 2. Restart the Collibra DQ Web and Collibra DQ Agent services. ``` ./owlmanage.sh stop=owlweb ./owlmanage.sh stop=owlagent ./owlmanage.sh start=owlweb ./owlmanage.sh start=owlagent ``` {% hint style="warning" %} If you use file-based SAML authentication with the `SAML_METADATA_USE_URL` variable set to `true` in the owl-env.sh script, update the Meta-Data URL option on the SAML Security Settings page with your metadata file. Use the **file:/opt/owl/config/idp-metadata.xml** format, ensuring the file name begins with the prefix **file:**. For additional steps on how to configure this, go to the "Enable the SAML SSO sign in option" section in [Configuring SAML authentication](/data-quality-self-hosted/security-configuration/saml-authentication/configuring-saml-authentication.md). {% endhint %} {% endstep %} {% endstepper %} *** ## Upgrading data source drivers When new data source drivers are available, they are listed in the [Release notes](/data-quality-self-hosted/release-notes.md) or recommended to you directly by Collibra. Determine which drivers need to be updated and follow these steps: {% stepper %} {% step %} Review the release notes to see which drivers need to be updated. {% endstep %} {% step %} From the previously extracted tarball provided to you by Collibra, locate the **drivers.tar.gz** file and extract the contents into a new directory called *drivers*. {% endstep %} {% step %} Rename your **/owl/drivers** folder "**/owl/old\_drivers/**" to create a backup of the old drivers. {% endstep %} {% step %} Replace the drivers from the /owl/old\_drivers/ folder with the new drivers extracted from the tarball /owl/drivers/. Example: If you replace an old Databricks driver with a new one, the file path might look like /owl/drivers/databricks. *** {% endstep %} {% endstepper %} {% endtab %} {% tab title="Kubernetes" %} Deploy the new Collibra DQ Helm Chart on your Kubernetes cluster to upgrade to a new version of Collibra DQ. {% stepper %} {% step %} Download the Docker **key.json** from the Object Store and run the following command. ``` docker login -u _json_key -p "$(cat client-repo-key.json)" https://gcr.io ``` {% endstep %} {% step %} Using the Docker Pull Commands you obtained from the Collibra Downloads page, run one command per container to pull the Collibra DQ containers. The Docker pulls should follow a similar format to the ones in the following example: ``` docker pull gcr.io/owl-hadoop-cdh/dq-web:2026.02-ABDGCSHILM-123 docker pull gcr.io/owl-hadoop-cdh/dq-agent:2026.02-ABDGCSHILM-123 docker pull gcr.io/owl-hadoop-cdh/dq-livy:4.1.0-2025.02-ABDGCSHILM-123 docker pull gcr.io/owl-hadoop-cdh/dq-spark:4.1.0-2025.02-ABDGCSHILM-123 ``` {% endstep %} {% step %} Tag the pulled containers and upload them to your internal Artifactory for deployment. {% endstep %} {% step %} To deploy the new Collibra DQ Helm Chart on your Kubernetes cluster and upgrade to a new version of Collibra DQ, run the following Helm commands, replacing the placeholder values with the actual values described in the table below. {% hint style="warning" %} The following example command may vary depending on the options your organization supplied during the initial installation.When upgrading, it's crucial to consider Helm properties provided through extra options or defaulting in Helm Charts to avoid losing any existing configurations.Be sure to replace the entire Helm Chart package with each release. {% endhint %} ``` helm upgrade --install --namespace \ --set global.version.dq= \ --set global.version.spark= \ --set global.configMap.data.license_key= \ --set global.configMap.data.license_name= \ --set global.web.admin.email=${email} \ --set global.web.admin.password=${password} \ --set global.web.service.type=ClusterIP \ --set global.image.repo= \ \ /path to the helm chart root folder> ```

Value	Description
<namespace>	The namespace that you created and into which you deployed Collibra DQ.
<cdq_version>	The version from the web image suffix. For example, 2026.02 from the image, dq-web:2026.02.
<cdq_spark_version>	The Spark version from the Spark image suffix. For example, 4.1.0-2026.02 from the image, spark:4.1.0-2026.02.
<cdq_license_key>	The license key provided to you by Collibra.
<your_license_name>	The license name provided to you by Collibra.
${email}	The default admin user email associated with the admin account.
${password}	The default admin user password for the admin account. The password must adhere to the following password policy: A minimum of 8 characters. A maximum of 72 characters. At least one upper-case character. At least one numeric character. At least one supported special character (`!@#%$^&*?_~`). Cannot contain the user ID (admin). If a password that does not meet the password policy is entered, the install process proceeds as though the password is accepted, but the admin user becomes locked out. If this occurs, rerun the Helm command with a password that meets the password policy and restart the web pod.
<pathTolmageRepo>	This is your private registry key, where the Collibra images are available. When this is not provided, you will pull the images from the Collibra image registry, for which you should create a pull secret with the repo key provided by Collibra. See the Cloud native install documentation for more details about how to create a pull secret.
<deployment_name>	Any name of your choice for this deployment.

{% endstep %} {% step %} Check that all required Kubernetes resources are available and running. 1. List all of the resources of the namespace in your Kubernetes cluster into which Collibra DQ is deployed, including pods, Ingress/LoadBalancer, and statefulsets. ``` kubectl get all -n \ ``` {% endstep %} {% step %} [Create a test DQ job](/data-quality-self-hosted/core-concepts/explorer.md) without any optional DQ layers or rules to verify that the Spark driver, executors, and containers are able to launch successfully. {% endstep %} {% endstepper %} {% hint style="warning" %} If you use file-based SAML authentication with the `SAML_METADATA_USE_URL` variable set to `true` in the owl-web ConfigMap, update the Meta-Data URL option on the SAML Security Settings page with your metadata file. Use the **file:/opt/owl/config/idp-metadata.xml** format, ensuring the file name begins with the prefix **file:**. For additional steps on how to configure this, go to the "Enable the SAML SSO sign in option" section in [Configuring SAML authentication](/data-quality-self-hosted/security-configuration/saml-authentication/configuring-saml-authentication.md). {% endhint %} {% endtab %} {% endtabs %} ## What's next * [Create a basic job](/data-quality-self-hosted/core-concepts/explorer.md) to test that your upgrade was successful. * [Troubleshoot your upgrade](/data-quality-self-hosted/installation/upgrade-data-quality-observability-self-hosted/troubleshooting-the-upgrade.md), as needed.