> 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/release-notes/data-quality-observability-self-hosted-release-archive/release-2025-06.md).

# Release 2025.06

* [Announcement](#announcement)
* [New and improved](#new-and-improved)
* [Fixes](#fixes)

## Release Information

* Release date of Data Quality & Observability (self-hosted) 2025.06: June 30, 2025
* Release notes publication date: June 3, 2025

## Announcement

{% hint style="warning" %}
As a security measure, we are announcing the end of life of the Java 8 and 11 versions of Data Quality & Observability (self-hosted), effective in the August 2025 (2025.08) release.**In this release (2025.06)**, Data Quality & Observability (self-hosted) is only available on Java 17 and Spark 3.5.3. Depending on your installation of Data Quality & Observability (self-hosted), you can expect the following in this release:

* **Kubernetes installations** 
  * Kubernetes containers automatically contain Java 17 and Spark 3.5.3.
  * If you use custom drivers, ensure they are compatible with Java 17 and Spark 3.5.3.
  * If you use file-based SAML authentication with the `SAML_METADATA_USE_URL` variable set to `false` 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 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).
* **Standalone installations**
  * To install Data Quality & Observability (self-hosted) 2025.06, you must [upgrade to Java 17](https://support.collibra.com/hc/en-us/articles/29404286691991-Upgrading-Java-on-CentOS-RHEL-7-8-or-9) and [Spark 3.5.3](/data-quality-self-hosted/installation/agent/upgrade-spark.md).
  * If you use custom drivers, ensure they are compatible with Java 17 and Spark 3.5.3.
  * Follow the latest [steps to upgrade](/data-quality-self-hosted/installation/upgrade-data-quality-observability-self-hosted/upgrade-collibra-data-quality-observability.md) to Data Quality & Observability (self-hosted) 2025.06 with Java 17.
  * If you use file-based SAML authentication with the `SAML_METADATA_USE_URL` variable set to `false` 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 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).
  * We encourage you to migrate to a Kubernetes installation to improve the scalability and ease of future maintenance.

In the 2025.06 and 2025.07 releases, only critical and high-priority bug fixes will be made for Java 8 and 11 versions of Data Quality & Observability (self-hosted). For a breakdown of Java and Spark availability in current and upcoming releases, click "See what is changing" below.

<details>

<summary>See what is changing</summary>

| Data Quality & Observability (self-hosted) version | Java 11                                                                                                                                                                                                                                           | Java 17                                                                                                                                                                                                                                           | Java 21                                                                                                                                                                                                                                         | Spark versions | Additional notes                                                                                      |
| -------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------- | ----------------------------------------------------------------------------------------------------- |
| 2025.08                                            | <img src="https://4121921244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWCrP7Albs8DfJjIQxUxw%2Fuploads%2Fgit-blob-de45f34193ae06a2b093c2dfb8fb80cfda945166%2Fclose-large%402x.png?alt=media" alt="" data-size="line"> No | <img src="https://4121921244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWCrP7Albs8DfJjIQxUxw%2Fuploads%2Fgit-blob-d06dd40622fc7d030e21f7c0303a90eb28d229fc%2Fok-large%402x.png?alt=media" alt="" data-size="line"> Yes   | <img src="https://4121921244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWCrP7Albs8DfJjIQxUxw%2Fuploads%2Fgit-blob-d06dd40622fc7d030e21f7c0303a90eb28d229fc%2Fok-large%402x.png?alt=media" alt="" data-size="line"> Yes | 3.5.6 only     | Fixes for Java 8 and 11 build profiles will be available only for critical and high-priority defects. |
| 2025.09 through 2026.01                            | <img src="https://4121921244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWCrP7Albs8DfJjIQxUxw%2Fuploads%2Fgit-blob-de45f34193ae06a2b093c2dfb8fb80cfda945166%2Fclose-large%402x.png?alt=media" alt="" data-size="line"> No | <img src="https://4121921244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWCrP7Albs8DfJjIQxUxw%2Fuploads%2Fgit-blob-d06dd40622fc7d030e21f7c0303a90eb28d229fc%2Fok-large%402x.png?alt=media" alt="" data-size="line"> Yes   | <img src="https://4121921244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWCrP7Albs8DfJjIQxUxw%2Fuploads%2Fgit-blob-d06dd40622fc7d030e21f7c0303a90eb28d229fc%2Fok-large%402x.png?alt=media" alt="" data-size="line"> Yes | 3.5.6 only     |                                                                                                       |
| 2026.02 through 2026.06                            | <img src="https://4121921244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWCrP7Albs8DfJjIQxUxw%2Fuploads%2Fgit-blob-de45f34193ae06a2b093c2dfb8fb80cfda945166%2Fclose-large%402x.png?alt=media" alt="" data-size="line"> No | <img src="https://4121921244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWCrP7Albs8DfJjIQxUxw%2Fuploads%2Fgit-blob-d06dd40622fc7d030e21f7c0303a90eb28d229fc%2Fok-large%402x.png?alt=media" alt="" data-size="line"> Yes   | <img src="https://4121921244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWCrP7Albs8DfJjIQxUxw%2Fuploads%2Fgit-blob-d06dd40622fc7d030e21f7c0303a90eb28d229fc%2Fok-large%402x.png?alt=media" alt="" data-size="line"> Yes | 4.1.0 only     |                                                                                                       |
| 2026.07 and newer                                  | <img src="https://4121921244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWCrP7Albs8DfJjIQxUxw%2Fuploads%2Fgit-blob-de45f34193ae06a2b093c2dfb8fb80cfda945166%2Fclose-large%402x.png?alt=media" alt="" data-size="line"> No | <img src="https://4121921244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWCrP7Albs8DfJjIQxUxw%2Fuploads%2Fgit-blob-de45f34193ae06a2b093c2dfb8fb80cfda945166%2Fclose-large%402x.png?alt=media" alt="" data-size="line"> No | <img src="https://4121921244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWCrP7Albs8DfJjIQxUxw%2Fuploads%2Fgit-blob-d06dd40622fc7d030e21f7c0303a90eb28d229fc%2Fok-large%402x.png?alt=media" alt="" data-size="line"> Yes | 4.1.0 only     |                                                                                                       |

</details>

&#x20;For more information, go to the [Data Quality & Observability (self-hosted) Java Upgrade FAQ](https://support.collibra.com/hc/en-us/articles/27421373124503-Collibra-Data-Quality-Observability-Java-upgrade-FAQ).
{% endhint %}

## New and improved

### Platform

{% hint style="info" %}
We updated Tomcat to address several security vulnerabilities (CVEs). The maximum part size for multipart requests is now set to 80 by default. This default limit might affect APIs that process datasets with an large number of columns. If necessary, you can change this limit using the property "DQ\_SERVLET\_MULTIPART\_MAXPARTCOUNT" in the owl-env.sh file for Spark Standalone installations or the owl-web-configmap for Kubernetes environments.
{% endhint %}

* This application, which was previously known as Collibra Data Quality & Observability, is now called Data Quality & Observability (self-hosted). This change reflects the introduction of the new Data Quality & Observability as part of the unified Collibra Platform. For more information about Data Quality & Observability, go to About Data Quality & Observability.

### Jobs

* When [archiving break records](/data-quality-self-hosted/core-concepts/findings/break-records-and-link-ids/archiving-break-records-from-pushdown-jobs.md) for Pushdown jobs, [link IDs](/data-quality-self-hosted/core-concepts/findings/break-records-and-link-ids.md) are now optional. This change provides greater flexibility in storing and accessing break records and offers a more scalable solution for remediating records outside of Data Quality & Observability Classic. (idea # CDQ-I-155, DCC-I-2566, DCC-I-5726, CDQ-I-90, CDQ-I-137)
  * If Data Quality & Observability (self-hosted) does not have permission to write to tables in your source database, Pushdown jobs with or without link IDs selected require you to run an `ALTER` statement on the **COLLIBRA\_DQ\_RULES** table to add the new results column for JSON data. Data Quality & Observability (self-hosted) will attempt this alteration automatically, which will cause the rule to fail because it will attempt to write to a column that doesn’t exist in your source database. For more information, go to [ALTER statement requirements for optional link IDs](https://support.collibra.com/hc/en-us/articles/32696441163799-ALTER-statement-requirements-for-optional-link-IDs).

    <div data-gb-custom-block data-tag="hint" data-style="warning" class="hint hint-warning"><p>If you don’t use a link ID, the results column in the <strong>COLLIBRA_DQ_RULES</strong> table will become exponentially larger, leading to unintended storage and compute costs in your source database. To minimize these costs, you can use a link ID or move these results out of your source database and into a remote file storage system, such as Amazon S3.</p></div>
* Data Quality & Observability (self-hosted) now checks that a link ID is set in the settings dialog on Explorer when creating a DQ job, to ensure the archive break records feature works when enabled. If one or more link ID columns are selected, a checkbox and drop-down list appear next to the **Archive Breaking Records** option in the settings dialog. If no link ID columns are selected, the checkbox and drop-down list are unavailable, and a tooltip appears when you hover over the option. (idea #DCC-I-2746)
* [Oracle Pushdown](/data-quality-self-hosted/core-concepts/explorer/processing-methods/pushdown-processing.md) is now generally available.
* Oracle Pushdown connections do not support the following data types:
  * LONG RAW
  * NCHAR
  * NVARCHAR2
  * ROWID
  * BYTES
* [Trino Pushdown](/data-quality-self-hosted/core-concepts/explorer/processing-methods/pushdown-processing.md) jobs now support source-to-target analysis for datasets within the same Trino Pushdown connection.
* SAP HANA, Snowflake, SQL Server, and Trino Pushdown connections do not support the VARBINARY [data type](/data-quality-self-hosted/connections/supported-connections/unsupported-data-types.md).
* The **valsrclimitui** admin limit, which controls the number of Validate Source records shown in the UI, now works as expected. For example, if **valsrclimitui** is set to 3, the UI shows 3 records from the Column Schema and 3 records from the Cell Panels.

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>The <strong>fpglimitui</strong>, <strong>histlimitui</strong>, and <strong>categoricallimitui</strong> admin limits are not working as expected today. Further, any admin limit ending “ui”, such as <strong>valsrclimitui</strong>, is intended only for updates made via the Admin Limits page of the Admin Console. Changes made to these admin limits via the command line will not be reflected.</p></div>

### Rules

* Rules that use `$colNm` in the query, such as data class, template, and data type checks, no longer perform automatic rule validation.
* The [Rule Workbench](/data-quality-self-hosted/core-concepts/dq-rules/rule-builder/working-with-the-rule-workbench/create-a-data-quality-rule.md) now has a warning message when the preview limit exceeds the recommended maximum of 500 records.
* The maximum length of the name of a rule is now 250 characters.
* The Preview Breaks modal now indicates the name of the rule.
* The [**Low**, **Medium**, and **High**](/data-quality-self-hosted/core-concepts/dq-rules/rule-builder/working-with-the-rule-workbench/understanding-the-rules-score.md) buttons now correctly reflect your selection when you reopen the Rule Details dialog box after automatically changing a rule's points. (idea #CDQ-I-150)
  * Additionally, if you manually update the score, the button automatically adjusts to match the corresponding scoring range:
    * **Low**: 1-4 points
    * **Medium**: 5-24
    * **High**: 25-100

### Admin Console

* Business unit names on the [Business Unit](/data-quality-self-hosted/admin-configuration/admin-console/business-unit-management.md) page in the Admin Console cannot contain the special characters / (forward slash), \`(backtick), | (pipe), or $ (dollar sign). If you use any of these special characters, an error message appears, and the Edit Business Unit dialog box remains open until the special characters are removed.
* [Data retention policies](/data-quality-self-hosted/admin-configuration/admin-console/data-retention-policy.md) now apply to the following metastore tables:
  * alert\_output
  * behavior
  * dataset\_activity
  * dataset\_schema\_source
  * hint
  * validate\_source
* The **Title** and **Story** fields of the User Story section of the User Profile page cannot contain the following special characters:

  * ‘ (single quote)
  * “ (double quote)
  * \-- (double dash)
  * < (less than)
  * \> (greater than)
  * & (ampersand)
  * / (forward slash)
  * \` (backtick)
  * \| (pipe)
  * $ (dollar sign)

  If you use any of these special characters, an error message appears, and the Edit User Story dialog box remains open until the special characters are removed.

## Fixes

### Rules

* You can now apply rule filter queries to rules created using rule templates on Pushdown datasets.
* Duplicated data quality rules no longer appear after you import data assets using CMA.
* Rules now run without errors when you use a single link ID to archive break records with SQL Server Pushdown.

### Profile

* Divide-by-zero errors and issues with empty histograms are now resolved. Calculations and visualizations now work as expected without interruptions.

### Findings

* You can now export rule break records with accurate counts. The total number of rule break records for a rule now matches the number in the **Breaking Records** column of the exported file.

### Integration

* When you rename a rule in Data Quality & Observability (self-hosted) that is part of a dataset integrated with Collibra Platform, additional Data Quality Rule assets are no longer created during the next integration. The existing Data Quality Rule asset is also no longer unintentionally set to a “suppressed” state during the next integration, and its name is updated to match the name in Data Quality & Observability (self-hosted).