What's new and changed in Db2

Important: IBM Cloud Pak® for Data Version 4.6 will reach end of support (EOS) on 31 July, 2025. For more information, see the Discontinuance of service announcement for IBM Cloud Pak for Data Version 4.X.

Upgrade to IBM Software Hub Version 5.1 before IBM Cloud Pak for Data Version 4.6 reaches end of support. For more information, see Upgrading IBM Software Hub in the IBM Software Hub Version 5.1 documentation.

Db2® updates can include new features, bug fixes, and security updates. Updates 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 Cloud Pak for Data.

Installing or upgrading Db2

Ready to install or upgrade Db2?

Related documentation:

Cloud Pak for Data Version 4.6.4

A new version of Db2 was released in March 2023 with Cloud Pak for Data 4.6.4.

The 4.6.4 release of Db2 includes the following features and updates:

Audit logging for Db2 databases
You can now create and manage customized audit policies for each Db2 database instance. You can use the individualized audit policies to monitor data and detect concerning behaviors.

For more information, see Configuring audit logging for Db2.

Cloud Pak for Data Version 4.6.2

A new version of Db2 was released in January 2023 with Cloud Pak for Data 4.6.2.

The 4.6.2 release of Db2 includes the following features and updates:

New capabilities for deploying instances from the web client
You now have more control if you use the web client to deploy database instances. The following options are now available from the web client:
  • You can disable the non-SSL port to prevent non-SSL connections to the database instance.
  • You can create a separate persistent volume for Db2 archive logs.

For details, see Creating a Db2 deployment on the cluster.

Components updated to Python 3
Db2 components that use Python now use Python 3. Any Python 2 scripts that you created are no longer compatible, and you need to update them to work with Python 3.
Security fixes

This release includes fixes for the following security issues:

CVE-2022-37599, CVE-2022-37601, CVE-2022-37603

Cloud Pak for Data Version 4.6.0

A new version of Db2 was released in November 2022 with Cloud Pak for Data 4.6.0.

The 4.6.0 release of Db2 includes the following features and updates:

TLS certificates are automatically replaced before they expire
If you use the default certificates that are provided with Cloud Pak for Data, the TLS certificates will be automatically replaced. Shortly before a TLS certificate reaches its expiry date, a new certificate will automatically replace the expiring certificate.
Scale memory and resources
You can now scale the CPU and memory for a Db2 database after you provision it. For example, if you need more resources to support high availability or to increase processing capacity, you can run a patch command to modify the allocated resources. For details, see Scaling up Db2.
Security fixes

This release includes fixes for the following security issues:

CVE-2022-0001, CVE-2022-0002, CVE-2022-0286, CVE-2022-0322, CVE-2022-0391, CVE-2022-1011, CVE-2022-21426, CVE-2022-21434, CVE-2022-21443, CVE-2022-21476, CVE-2022-21496, CVE-2022-22950, CVE-2022-22968, CVE-2022-22970, CVE-2022-22971, CVE-2022-23852, CVE-2022-24615, CVE-2022-24785, CVE-2022-25235, CVE-2022-25236, CVE-2022-25315, CVE-2022-25636

CVE-2021-0941, CVE-2021-20322, CVE-2021-21781, CVE-2021-23358, CVE-2021-26401, CVE-2021-29154, CVE-2021-3612, CVE-2021-3669, CVE-2021-37159, CVE-2021-3733, CVE-2021-3743, CVE-2021-3744, CVE-2021-3752, CVE-2021-3759, CVE-2021-3764, CVE-2021-3772, CVE-2021-3773, CVE-2021-4002, CVE-2021-4028, CVE-2021-4037, CVE-2021-4083, CVE-2021-41182, CVE-2021-41183, CVE-2021-41184, CVE-2021-4157, CVE-2021-41617, CVE-2021-41864, CVE-2021-4197, CVE-2021-4203, CVE-2021-42739, CVE-2021-43056, CVE-2021-43389, CVE-2021-43818, CVE-2021-43976, CVE-2021-44733, CVE-2021-45485, CVE-2021-45486

CVE-2020-0404, CVE-2020-13974, CVE-2020-19131, CVE-2020-26160, CVE-2020-27820, CVE-2020-35492, CVE-2020-4788

CVE-2018-25032