Known issues (IBM Db2)

Release 2025.1.0

Key

Summary

Workaround

DLPXECO-12057

In the IBM Db2 v4.9.0 connector, the default value of the skipDb2VersionCheck parameter was changed to True. This means the connector no longer performs validation of the Db2 server version—covering major, minor, fixpack, and modpack levels—during initialization.

As a result, the connector may attempt to provision VDBs on unsupported Db2 versions, which may fail due to compatibility issues.

If there are environments with more than one Db2 versions installed, it is recommended to explicitly set skipDb2VersionCheck=False in the db2_plugin.conf to make sure there are no unforeseen errors due to version compatibility issues.

Release 4.9.1

Key

Summary

Workaround

DLPXECO-12057

In the IBM Db2 v4.9.0 connector, the default value of the skipDb2VersionCheck parameter was changed to True. This means the connector no longer performs validation of the Db2 server version—covering major, minor, fixpack, and modpack levels—during initialization.

As a result, the connector may attempt to provision VDBs on unsupported Db2 versions, which may fail due to compatibility issues.

If there are environments with more than one Db2 versions installed, it is recommended to explicitly set skipDb2VersionCheck=False in the db2_plugin.conf to make sure there are no unforeseen errors due to version compatibility issues.

Release 4.9.0

Key

Summary

Workaround

DLPXECO-12057

In the IBM Db2 v4.9.0 connector, the default value of the skipDb2VersionCheck parameter was changed to True. This means the connector no longer performs validation of the Db2 server version—covering major, minor, fixpack, and modpack levels—during initialization.

As a result, the connector may attempt to provision VDBs on unsupported Db2 versions, which may fail due to compatibility issues.

If there are environments with more than one Db2 versions installed, it is recommended to explicitly set skipDb2VersionCheck=False in the db2_plugin.conf to make sure there are no unforeseen errors due to version compatibility issues.

Release 4.7.2

Key

Summary

Workaround

DB2-2231

During upgrade from 6.0.x to 7.0, 8.0, ….21.0 , Delphix engine destroys the plugin’s scratch path where all the plugin logs, configuration files are present. During the environment refresh, these paths and files are regenerated. However, any edits done in db2_plugin.conf will not be persisted

Before upgrading the engine, the user will have to make a copy of the db2_plugin.conf file to keep the changes intact.

Release 4.7.1

Key

Summary

Workaround

DB2-2056

Upgrade from lua version to VSDK has issues with VDB Snapsync

Re-provisioning the database with the dSource's snapshot fixes the issue.

DB2-2124

If the storage paths are subdirectories of another storage path, the instance name at target and true prod cannot be the same.

Create instance name on target different than true production

Release 4.7.0

Key

Summary

Workaround

DB2-2056

Upgrade from lua version to VSDK has issues with VDB Snapsync

Re-provisioning the database with the dSource's snapshot fixes the issue.

DB2-2124

If the storage paths are subdirectories of another storage path, the instance name at target and true prod cannot be the same.

Create instance name on target different than true production

Release 4.6.1

Key

Summary

Workaround

DB2-2056

Upgrade from lua version to VSDK has issues with VDB Snapsync

Re-provisioning the database with the dSource's snapshot fixes the issue.

DB2-2124

If the storage paths are subdirectories of another storage path, the instance name at target and true prod cannot be the same.

Create instance name on target different than true production

Release 4.6.0

Key

Summary

Workaround

DB2-2056

Upgrade from lua version to VSDK has issues with VDB Snapsync

Re-provisioning the database with the dSource's snapshot fixes the issue.

DB2-2124

If the storage paths are subdirectories of another storage path, the instance name at target and true prod cannot be the same.

Create instance name on target different than true production

Release 4.5.1

Key

Summary

Workaround

DB2-2107

db2ckbkp fails for Backup paths with spaces

Remove blank spaces from backup paths

DB2-2124

The instance name at target and true prod cannot be the same if the storage paths are sub directories of another storage path.

Create instance name on target different than true production

Release 4.5.0

Key

Summary

Workaround

DB2-2107

db2ckbkp fails for Backup paths with spaces

Remove blank spaces from backup paths

Release 4.4.2

There are no known issues in this release.

Release 4.4.1

There are no known issues in this release.

Release 4.4.0

There are no known issues in this release.

Release 4.3.2

There are no known issues in this release.

Release 4.3.1

There are no known issues in this release.

Release 4.3.0

There are no known issues in this release.

Release 4.2.1

There are no known issues in this release.

Release 4.2.0

There are no known issues in this release.

Release 4.1.3

There are no known issues in this release.

Release 4.1.2

There are no known issues in this release.

Release 4.1.1

There are no known issues in this release.

Release 4.1.0

There are no known issues in this release.

Release 4.0.1

There are no known issues in this release.

Release 4.0.0

There are no known issues in this release.

Release 3.1.1

There are no known issues in this release.

Release 3.1.0

There are no known issues in this release.

Release 3.0.2

There are no known issues in this release.

Release 3.0.1

There are no known issues in this release.

Release 3.0.0

Key

Summary

Workaround / Comments

DB2-1318

Jobs on UI might hang intermittently due to a known IBM Db2 bug

This issue will be only observed when multiple datasets jobs, within the same Db2 instance, will get executed at the same time.