What's new and changed in Data Virtualization

Data Virtualization updates can include new features and fixes. Releases are listed in reverse chronological order so that the latest release is at the beginning of the topic.

You can see a list of the new features for the platform and all of the services at What's new in IBM Software Hub.

Installing or upgrading Data Virtualization

Ready to install or upgrade Data Virtualization?

  • To install Data Virtualization along with the other IBM® Software Hub services, see Installing IBM Software Hub.
  • To upgrade Data Virtualization along with the other IBM Software Hub services, see Upgrading IBM Software Hub.
  • To install or upgrade Data Virtualization independently, see Data Virtualization.
    Remember: All of the IBM Software Hub components associated with an instance of IBM Software Hub must be installed at the same version.

IBM Software Hub Version 5.2.2

A new version of Data Virtualization was released in October 2025 with IBM Software Hub 5.2.2.

Operand version: 3.2.2

This release includes the following changes:

Security issues fixed in this release
Version 5.2.2 of the Data Virtualization service includes various security fixes.

IBM Software Hub Version 5.2.1

A new version of Data Virtualization was released in August 2025 with IBM Software Hub 5.2.1.

Operand version: 3.2.1

This release includes the following changes:

New features
This release of Data Virtualization includes the following features:
Capture the schema name of objects audited in Db2 audit events
Db2 auditing events now capture schema names in addition to object names, allowing you to more precisely identify objects impacted by Data Virtualization operations as “SCHEMA_NAME”.“OBJECT_NAME”.

Updates
The following updates were introduced in this release:
New views and stored procedure property
  • Run the VIRTUALIZECOSOBJECT stored procedure to virtualize a table from a file or directory on a Cloud Object Storage (COS).
  • Run the NUMTABSREMOTE view to show the number of tables in a remote RDBMS source.
  • Use the BATCHSIZE_FOR_LISTSCHEMAS_OR_LISTTABLES property (as part of the SETCONFIGPROPERTY stored procedure) to specify the maximum number of schemas or tables retrieved through the LISTSCHEMAS and LISTTABLES APIs.
Issues fixed in this release
The following issues were fixed in this release:

Limited governance support for object or schema names that contain the double quotation ("), backslash (\) or both characters
Issue: When you publish an object or schema to a catalog or project, the action fails if the object or schema name contains a backslash (\) or double quotation marks (").
Note: Row filtering data protection rules do not apply to the objects with the backslash (\) character in their object or schema name.
The failed publish action for names that contain a backslash (\) displays this error: 
The assets request failed: CDICO2034E: The path (/CPADMIN/D/EMO] contains more path elements than defined for the connection [2).
The failed publish action for names that contain a double quotation mark (") displays this error: 
SQLExecDirectW: {42603} [IBM][CLI Driver][DB2/LINUXX8664] SQL0010N The string constant beginning with "" WHERE 0=1 FOR READ ONLY WITH UR" does not have an ending string delimiter. SQLSTATE=42603
Resolution: This issue is now fixed.
Some projects are not displayed for assignment in the Virtualized data page
Issue: When you attempt to assign virtualized objects to a project in the Virtualized data page, some projects might not be displayed in the list of projects.
Resolution: This issue is now fixed.
Previewing Cloud Object Storage (COS) data might cause a "This flat file is invalid" error
Issue: When you navigate to the Virtualize page and then select Files to preview COS data, you might encounter this error: This flat file is invalid. Try refreshing or remove the flat file before continuing. This error occurs when a database connection becomes inactive for an extended time without COS connectivity, which causes the database connection to time out and terminate.
Resolution: This issue is now fixed.
Upgrading your Data Virtualization instance from IBM Cloud Pak® for Data version 4.8 to 5.2.0 is in the FAILED state
Issue: When you attempt to upgrade your Data Virtualization instance from version 4.8 to 5.2.0, the upgrade fails and is in the FAILED state.

 Namespace           Service type        Version             ID                  Name                  Provision status    Service status 
 ---------           ------------        -------             --                  ----                  ----------------    -------------- 
 thanos              dv                  2.2.8               1748449428248716    watson-query-thanos   PROVISIONED         FAILED
Resolution: This issue is now fixed.
Ineligible query error displays when you create a cache that references non-virtual objects
Issue: If you attempt to create a cache for some SQL queries listed in the Queries tab from the Cache dashboard such as those that reference non-virtual objects (such as internal Db2 catalog tables), then the console displays an Ineligible query error because the non-virtual objects violate the Db2 MQT restrictions.

The error might resemble this example:

Ineligible query:

The request was invalid. SQL not supported. The statement failed because the fullselect specified for the materialized query table "CACHESYS.DVTMP22250507188049224632" violates a restriction. Reason code = "2".. SQLCODE=-20058, SQLSTATE=428EC, DRIVER=4.27.25
Resolution: This issue is now fixed.
setrdbcx fails with java.lang.NullPointerException error when connecting to the Snowflake data source
Issue: For assets that are in your cart, if you attempt to update the data file Cloud Object Storage (COS) column name or choose to change all the column names to uppercase, and then virtualize the asset, the column name fails to update.
Resolution: This issue is now fixed.

Customer-reported issues fixed in this release
For a list of customer-reported issues that were fixed in this release, see the Fix List for IBM Cloud Pak for Data on the IBM Support website.

Security issues fixed in this release
Version 5.2.1 of the Data Virtualization service includes various security fixes.

IBM Software Hub Version 5.2.0

A new version of Data Virtualization was released in June 2025 with IBM Software Hub 5.2.0.

Operand version: 3.2.0

This release includes the following changes:

New features
This release of Data Virtualization includes the following features:
Optimize processing and use of system resources with query banding in Teradata
You can now apply query banding when connecting to Teradata sources by attaching name-value pairs to your queries. Query bands help identify query context, such as task priority, which enables Teradata to optimize processing by adjusting the use of system resources when workload management policies are in place. To use query banding, create a new Teradata connection in the Data Virtualization web client and specify the query band expression.
Track the lineage of your data by using MANTA Automated Data Lineage
You can now track the linage of your data assets, including where your data comes from and goes to, by importing your metadata using MANTA Automated Data Lineage.

For more information, see Configuring Data Virtualization connections for lineage imports (MANTA Automated Data Lineage).

New "Mask at read" semantics for enhanced data protection
You can now configure Data Virtualization to mask data before evaluating query predicates, JOINs, GROUP BY, and ORDER BY clauses. By default, Data Virtualization applies masking data protection rules to the result set.
Updates
The following updates were introduced in this release:
Adoption of Db2 Datalake tables in place of external Hadoop tables
Data Virtualization now uses Db2 Datalake table syntax and semantics for Cloud Object Storage access and caches. You can now use CREATE and DROP Datalake table statements instead of the CREATE HADOOP TABLE statement and DROP TABLE statement. For more information, see  CREATE DATALAKE TABLE statement and DROP DATALAKE TABLE statement.
Consistently govern your governed catalog artifacts with shared properties
You can now consistently govern connected data assets across multiple governed catalogs by using shared properties. 
Connect to external connections using the out-of-the-box pass-through secure route
Data Virtualization now comes with a predefined passthrough OpenShift® route named c-db2u-dv-db2u that allows you to connect to the Db2 server by using the route host on port 443.

For more details, see Configuring network requirements.

Issues fixed in this release
The following issues were fixed in this release:
You cannot use special characters such as semicolons in schema names when you virtualize a table in MongoDB on Cloud
When you virtualize a table in a MongoDB on Cloud data source that has a semicolon in the schema name, you will not be able to virtualize the table. The MongoDB on Cloud data source removes the semicolon from the schema name and queries of this virtual table fail with error SQL5105N.
Resolution: This issue is now fixed.
Querying an object that uses double quotation marks (") in its name fails with an external authorizer error
When you attempt to query an object that uses double quotation marks (") in it's name, this error is displays: The statement failed because a Big SQL component encountered an error. Component receiving the error: "External authorizer". Component returning the error: "WKC Authorizer". Log entry identifier: "[SCL-0-6923de68f]". Reason: "EVAL-3".. SQLCODE=-5105, SQLSTATE=58040, DRIVER=4.32.28.
Resolution: This issue is now fixed.
Limited governance support for object or schema names that contain the slash (/) character
Publishing an object or schema to a catalog or project fails if the object or schema name contains a slash (/).
Resolution: This issue is now fixed.
Users cannot log out from the Data Virtualization interface
Users cannot lot out from Data Virtualization by using the Data virtualization web client.
Resolution: This issue is now fixed.

Unable to connect to the Db2 database if LDAP is enabled against IBM Cloud Pak for Data
When you have LDAP enabled against IBM Cloud Pak for Data, and then you attempt to connect to the Db2 database, an error message stating that the user ID and the password are wrong is displayed.
Resolution: This issue is now fixed.
Data Virtualization instance is unavailable and the web client is disabled after you upgrade from IBM Cloud Pak for Data 4.8.8 to IBM Software Hub 5.1.1
Resolution: This issue is now fixed.
Data Virtualization automatically restarts at 1PM UTC
An automatically scheduled job was failing and causing Db2 to restart once a day at 1PM UTC.
Resolution: This issue is now fixed.
Pre-backup phase fails when upgrading from IBM Cloud Pak for Data 4.8.x to 5.1.2
When you attempt to upgrade your Data Virtualization instance, the liveness probe fails with the error ERROR DV liveness probe failed during the liveness check. After this, the upgrade aborts and the pods restart with the message INFO Pod is still starting. Exit right away with state 0.
Resolution: This issue is now fixed.
Alert monitor is unable to detect the data policy service (DPS) during instance upgrade to IBM Cloud Pak for Data 5.1.2
Issue: When you upgrade your Data Virtualization instance to IBM Cloud Pak for Data 5.1.2 from any previous version, the platform reports a failure in the alert monitor to evaluate the DPS: ERROR Dummy evaluation against IKC DPS failed with output. This error occurs if the IBM Knowledge Catalog test table is missing from your instance.
Resolution: This issue is now fixed.
Support of timestamp data type up to nanoseconds
Issue: Data Virtualization supports the timestamp data type up to nanoseconds. When a remote data source's timestamp type is with a scale greater than 9 nanoseconds, Data Virtualization returns truncated timestamp column values up to nanoseconds. Additionally, for timestamp predicates, Data Virtualization compares only up to nanoseconds.
Resolution: This issue is now fixed.
Customer-reported issues fixed in this release
For a list of customer-reported issues that were fixed in this release, see the Fix List for IBM Cloud Pak for Data on the IBM Support website.

Security issues fixed in this release
Version 5.2.0 of the Data Virtualization service includes various security fixes.