fix pack summary

fix packs contain important technical changes and new functionality that might affect your product usage.

To download a DB2® fix pack for your installed DB2 product, go to the Download DB2 Fix Packs by version page (https://www.ibm.com/support/docview.wss?uid=swg27007053). The page for each fix pack includes the list of fixed APARs.

If you did not apply the fix packs or did not update your local information center since was available, review the following sections and topics to understand the technical changes included in the fix packs. Each fix pack for a release is cumulative; a fix pack contains all of the technical changes and new functionality that were shipped in previous fix packs for that release.

Fix Pack 11

Refer to System requirements update for IBM Db2 10.5 Releases for changes on platform support, software, and any other system requirements for this release.

Fix Pack 10

DB2 Version 10.5 Fix Pack 10 contains the functionality of previous fix packs. However, Fix Pack 10 does not contain new enhancements, and there were no changes to the existing functionality.

Fix Pack 9

DB2 Version 10.5 Fix Pack 9 contains the functions of the previous fix packs. This fix pack and future fix packs deliver APAR and security vulnerability fixes.

Fix Pack 8

DB2 Version 10.5 Fix Pack 8 contains the functions of the previous fix packs. This fix pack and future fix packs deliver APAR and security vulnerability fixes. Furthermore, SA MP 4.1.0.3 + efix1 are now delivered with this Fix Pack. However, it is required to manually download and apply the SA MP license file (sam41.lic). For instructions on how to download and apply the SA MP license file, refer to the Resolving the problem section of Upgrading DB2 LUW Purescale or non-purescale to Fixpack 8 may stop TSA working.

Fix Pack 7

DB2 Version 10.5 Fix Pack 7 contains the functionality of previous fix packs. However, Fix Pack 7 does not contain new enhancements, and there were no changes to the existing functionality. This fix pack and future fix packs will deliver only APAR and security vulnerability fixes.

When you upgrade the SQL Replication servers to DB2 Version 10.5 Fix Pack 7, you must migrate the replication control tables to architecture level 1021. For further information on migrating the replication control tables to architecture level 1021, refer to Migrating to SQL Replication ARCH_LEVEL 1021 on Linux, UNIX, and Windows.

Fix Pack 6

DB2 Version 10.5 Fix Pack 6 contains the functionality of previous fix packs. However, Fix Pack 6 does not contain new enhancements, and there were no changes to the existing functionality. This fix pack and future fix packs will deliver only APAR and security vulnerability fixes.

Fix Pack 5

contains the functionality of the previous fix pack and also includes the following enhancements:
  • Product packaging enhancement, and new licensing option:
    • The following new DB2 offerings are available as add-ons to different DB2 product editions:
      • Offering
      • Offering
      • Offering
      • Offering.

      The Offering provides new encryption functionality. The other three DB2 add-on offerings package existing functionality that can be added to certain DB2 editions.

      Some DB2 product editions include these DB2 offerings by default. Otherwise, a license for each DB2 offering is available for purchase.

      For more information about these DB2 offerings and the DB2 product editions they are included with or can be added to, see DB2 database product editions and DB2 offeringsDB2 database product editions and DB2 offerings in .

    • introduces a new licensing option for and that run a environment. If your configuration contains a member that is used only for administrative or failover purposes, licensing requirements for this administrative member can be reduced. For details, see License Information documents at http://www.ibm.com/software/sla/sladb.nsf/search.
  • DB2 native encryption:
    • adds native database encryption to the DB2 database server. This enhancement is easy to implement and requires no application or schema changes. DB2 native encryption provides transparent and secure key management that is based on Public Key Cryptography Standard #12 (PKCS#12). DB2 native encryption enables you to meet compliance requirements in a cost effective manner.

      For more information, see DB2 native encryption DB2 native encryption in the .

      The encryption functionality that is introduced through DB2 native encryption is included by default in these DB2 product editions: DB2 Express-C, DB2 Advanced Workgroup Server Edition, DB2 Advanced Enterprise Server Edition, and the DB2 Developer Edition. The encryption functionality is also available for purchase to add to these DB2 editions: DB2 Express® Server Edition, DB2 Workgroup Server Edition, DB2 Enterprise Server Edition. For more information, see DB2 database product editions and DB2 offeringsDB2 database product editions and DB2 offerings in .

  • Column-organized tables enhancements:
  • High availability disaster recovery (HADR) enhancements:
    • introduced HADR database support of column-organized tables. introduces BLU Acceleration support on Windows operating systems, including HADR databases. See Column-organized tables enhancements Column-organized tables in .
    • Version 4.1 is now supported in a high availability environment. For more information about high availability, see High availabilityHigh availability in .
  • Feature enhancements:
    • A geographically dispersed cluster (GDPC) environment is now supported on any x64 Intel compatible rack mounted server which supports these Ethernet RoCE adapters:
      • Mellanox ConnectX-2 generation card supporting RDMA over converged Ethernet (RoCE)
      • Mellanox ConnectX-3 generation card supporting RDMA over converged Ethernet (RoCE)
      For prerequisite information, see Installation prerequisites for DB2 pureScale® Feature (Linux)Installation prerequisites for DB2 pureScale Feature (Linux) in .
    • On supported AIX® and Linux operating systems, you can now run the geographically dispersed cluster (GDPC) feature on a Transmission Control Protocol/Internet Protocol over Ethernet (TCP/IP) network without special remote direct memory access (RDMA) capable adapters.
    • Cluster caching facility (CF) self-tuning memory can now be explicitly enabled to help optimize performance and avoid out of memory conditions. For more information, see c0061366.html.
  • Application interface enhancements:
    • The driver that is included with this fix pack contains several enhancements. For more information, see c0060895.html.
    • The IBM Data Server Provider for .NET that is included with this fix pack contains several enhancements. For more information, see c0060908.html.
    • Use of the client information IBM data server driver configuration keywords are now supported by embedded SQL applications. See Use of the db2dsdriver.cfg configuration file by embedded SQL applicationsthe Use of the db2dsdriver.cfg configuration file by embedded SQL applications topic in .
  • Other miscellaneous enhancements:
    • The execution of scalar user-defined functions (scalar UDFs) with column-organized tables is improved. This enhancement can be particularly beneficial when scalar UDFs that meet the following criteria are included in the predicate of a query.
      • UDFs are defined as NO SQL and ALLOW PARALLEL.
      • Input and output data types are supported in column-organized tables.
      For more information, see User-defined functionsUser-defined functions in .
    • You can now specify one or more network interface cards (NICs). When a DB2 member starts, it attempts to acquire exclusive access to a specific port on one or more network interface cards on the host where it resides. The DB2 instance uses these ports to service remote clients or drivers. Starting in , you can specify one or more network interface cards (NICs) through which a DB2 member can acquire exclusive access to a specific port. You can specify a particular NIC by its IP address or by the host name that maps to that address in the nicbinding.cfg file. For more information, see Specifying the NIC through which a DB2 member can acquire exclusive access to a portSpecifying the NIC through which a DB2 member can acquire exclusive access to a port in .
    • The db2cli command now includes the following enhancements:
      • You can now configure the IBM data server driver configuration file (db2dsdriver.cfg) with information from the LDAP catalog entries when you specify the -refreshldap option. See db2cli - interactive commandthe db2cli - interactive command topic in the .
      • You can now use the LDAP catalog entries to register data source names (DSNs) in the Microsoft ODBC Driver Manager with the -includeldap option. See db2cli - interactive commandthe db2cli - interactive command topic in the .
    • On supported AIX operating systems, now supports Version 4.1. For details and the most up-to-date installation requirements for DB2 database products, see System requirements for IBM DB2 for Linux, UNIX, and Windows (http://www-01.ibm.com/support/docview.wss?uid=swg27038033).
    • User IDs and group IDs can now be up to 128 bytes on Linux and UNIX operating systems, but any operating system naming restrictions still apply. In previous releases, user and group IDs were limited to 8 characters. For more information, see User, user ID and group naming rulesUser, user ID and group naming rules in .
Important:
  • If, after applying , you want to revert to an earlier fix pack, use a new utility, db2checkCOL, to determine whether any tables in your database cannot be accessed in that earlier fix pack before reverting to that fix pack. For more information, see db2checkCOL - Check database for table accessibility in a prior fix packdb2checkCOL - Check database for table accessibility in a prior fix pack in the .
  • If you are currently using tables with CHAR or GRAPHIC columns, you must follow the instructions in this technoteSteps to determine whether APAR IV53366 is affecting your DB2 databases (see http://www-01.ibm.com/support/docview.wss?uid=swg21663252) before applying Fix Pack 3, , or .

Fix Pack 3

Important: If you are currently using tables with CHAR or GRAPHIC columns, you must follow the instructions in this technoteSteps to determine whether APAR IV53366 is affecting your DB2 databases (see http://www-01.ibm.com/support/docview.wss?uid=swg21663252) before applying Fix Pack 3, or .
Fix Pack 3 contains the functionality of the previous fix pack and also includes the following enhancement:

Fix Pack 2

DB2 Fix Pack 2 updates the clients and drivers for AIX, HP-UX, Linux, Solaris, and Windows operating systems to support DB2 for z/OS® 11.

Fix Pack 2 contains the functionality of the previous fix pack and includes the following changes:
Fix Pack 2 contains the functionality of the previous fix pack and includes the following enhancements:
  • The driver that is included with this fix pack contains several enhancements. For more information, see c0060895.html.
  • The IBM Data Server Provider for .NET that is included with this fix pack contains several enhancements. For more information, see c0060908.html.

Fix Pack 1

Fix Pack 1 includes the following changes:
Fix Pack 1 also contains the following enhancements:
  • The is now supported on any x86 (x64) Intel compatible rack mounted server which supports these InfiniBand QDR or Ethernet RoCE adapters:
    • Mellanox ConnectX-2 generation card supporting RDMA over converged Ethernet (RoCE) or InfiniBand
    • Mellanox ConnectX-3 generation card supporting RDMA over converged Ethernet (RoCE) or InfiniBand
    Support of on any x64 Intel compatible rack mounted server in a geographically dispersed clusters (GDPC) added in and later fix packs.

    For prerequisite information, see Installation prerequisites for DB2 pureScale Feature (Linux)Installation prerequisites for DB2 pureScale Feature (Linux) in .

  • The performance of a select, update, or delete operation that affects only one row in a table can be improved if the table has unique indexes, because the query optimizer can now use an index scan instead of a full table scan. For more information, see Types of index accessthe Types of index access topic in .