DB2 Version 10.1 for Linux, UNIX, and Windows fix pack summary

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

Start of change You can download fix packs from the DB2® Fix Packs by version page (https://www.ibm.com/support/docview.wss?uid=swg27007053). Use this page to download a DB2 fix pack for the installed DB2 product you have. The link to each fix pack includes the APAR Fix List. End of change

If you did not apply the Version 10.1 fix packs or did not update your local Information Center since Version 10.1 was available, review the following lists to understand the new and changed functionality included in the Version 10.1 fix packs. Each fix pack for a release is cumulative: a fix pack contains all of the new and changed functionality that was included in previous fix packs.

Fix Pack 6
Fix Pack 5
Fix Pack 4
Fix Pack 3
Fix Pack 2
Fix Pack 1

Fix Pack 6

DB2 Version 10.1 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 delivers only APAR and security vulnerability fixes.

Fix Pack 5

Fix Pack 5 contains the functionality of the previous fix pack and includes the following enhancements:

The following operating system support is added:
- Red Hat Enterprise Linux (RHEL) 7 (however, RHEL 7 is not supported in a DB2 pureScale® environment). 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).
- IBM Tivoli® System Automation for Multiplatforms Version 4.1 is now supported in a high availability environment. For more information about high availability, see High availability.

Fix Pack 4

Fix Pack 4 contains the functionality of the previous fix pack and includes the following changes:

Several performance related improvements are made by optimizing data warehouse queries. For more information, see FP4: Optimizing data warehouse queries

Fix Pack 4 contains the functionality of the previous fix pack and includes the following enhancements:

You can now configure high availability disaster recovery (HADR) using db2haicu if you are using internet protocol version 6 (IPV6) adapters. In previous releases, you had to either add an IPV4 interface or manually configure network monitoring using IBM Tivoli System Automation for Multiplatforms (SA MP) commands. For more information, see DB2 high availability instance configuration utility (db2haicu).
The db2look command supports two new parameters. You can now use the -createdb parameter to generate the CREATE DATABASE command that was used to create the source database. Also, you can use the new printdbcfg parameter to generate UPDATE DB CFG commands from the source database configuration parameters. For more information, see db2look - DB2 statistics and DDL extraction tool command.
Enhanced encryption is now possible with the adherence to NIST SP 800-131A. This compliance provides enhanced and stronger cryptographic keys along with more robust algorithms. For more information, see FP4: Enhanced encryption through NIST SP 800-131A compliance.
The following operating system support is added:
- Red Hat Enterprise Linux (RHEL) 5.9, 5.10, 6.4, and 6.5
- SUSE Linux Enterprise Server (SLES) 11 SP3
- Solaris 11
- Windows 8.1 and Windows 2012 R2
In addition, POWER8® support is added. However, POWER8 is not supported in a DB2 pureScale environment.
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).

Fix Pack 3

Fix Pack 3 contains the functionality of the previous fix pack and includes the following changes:

DB2 Text Search now provides more options for finer control for committing batches. For more information, see FP3: Committing batches for DB2 Text Search.

Fix Pack 3 contains the functionality of the previous fix pack and includes the following enhancements:

Two new index configuration options are available to control update processing. For more information, see FP3: DB2 Text Search index configuration options.
You can set command locks manually to ensure text indexes are not affected by operations which are not managed through the DB2 Text Search server. For more information, see FP3: Set manual command locks for DB2 Text Search.
The interface between custom scripts and DB2 has been greatly improved for users who write their own scripts to allow snapshot backup and restores on devices that don't provide a vendor library for DB2 Advanced Copy Services (ACS). The DB2 ACS API is now wrapped in the library for DB2 ACS, so they library invokes the customer script to perform the snapshot operation. The DB2 database manager takes over the error-prone actions like issuing the SET WRITE SUSPEND, SET WRITE RESUME, and db2inidb commands at the correct time. At the same time, because the DB2 ACS API is being used, an entry is made in the recovery history file for every snapshot operation, allowing you to monitor successful and unsuccessful backups. For more information, see DB2 Advanced Copy Services (ACS) scripted interface.

Fix Pack 2

Fix Pack 2 contains the functionality of the previous fix pack and includes the following changes:

The behavior of the non-seamless ACR feature is changed when connecting to the DB2 for z/OS® data sharing group. For more information, see Operation of the automatic client reroute feature for an application other than Java™ to the DB2 for z/OS server.

Fix Pack 2 contains the functionality of the previous fix pack and includes the following enhancements:

IBM Mobile Database and IBM Mobile Database Sync are now bundled with all DB2 product editions, and all InfoSphere® Warehouse product editions. For more information, see Functionality in DB2 features and DB2 product editions
The DB2 pureScale Feature is now supported on any x86 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 DB2 pureScale Feature on any x86 Intel compatible rack mounted server does not apply to geographically dispersed DB2 pureScale clusters (GDPC).
For prerequisite information, see Installation prerequisites for DB2 pureScale Feature (Linux).
In a DB2 pureScale environment, DB2 pureScale members now support multiple low-latency, high-speed cluster interconnects. With multiple cluster interconnects on members, you can connect each member to more than one switch. Adding cluster interconnects, and adding a switch to a DB2 pureScale environment both improve fault tolerance. For more information, see Network topology configuration considerations.
A new API called db2Ingest API is now available. With this API, you can now ingest data from an input file or pipe into a DB2 table. For more information see, db2Ingest API - Ingest data from an input file or pipe into a DB2 table.
The db2prereqcheck command has been enhanced with more options. For more information see, db2prereqcheck - Check installation prerequisites.
In a DB2 pureScale environment, the new default for a file system managed by DB2 no longer requires you to enable password-less root login for GPFS™. This allows you to know and track the user ID that logged in as root. Use new non-root SSH user ID, db2sshid, for a secure shell (SSH) network protocol between hosts. For more information, see FP2: Password-less remote root login for GPFS.
The GET_ROUTINE_NAME stored procedure has been added. This procedure returns the name of an SQL PL object given the object's LIB_ID column. For more information, see GET_ROUTINE_NAME procedure - get SQL PL object name.
The SET_MAINT_MODE_RECORD_NO_TEMPORALHISTORY procedure has been added. This procedure allows you to set the internal option to disable recording of temporal history for a system-period temporal table and allows values to be specified for the special temporal columns. For more information, see SET_MAINT_MODE_RECORD_NO_TEMPORALHISTORY procedure - disable recording of temporal history.
Environment routine support has been extended and now provides more operating system metrics for the HP-UX and Solaris platforms. For more information, see ENV_GET_NETWORK_RESOURCES table function - Return network information and ENV_GET_DB2_SYSTEM_RESOURCES table function - Return DB2 system information.
The MON_GET_ROUTINE table function has been added. This table function returns aggregated execution metrics for procedures, external procedures, compiled functions, compiled triggers, and anonymous blocks invoked since the database was activated. For more information, see MON_GET_ROUTINE table function.
The MON_GET_ROUTINE_DETAILS table function has been added. This table function returns aggregated execution metrics for procedures, external functions, compiled functions, compiled triggers, and anonymous blocks invoked since the database was activated. For more information, see MON_GET_ROUTINE_DETAILS table function.
The MON_GET_ROUTINE_EXEC_LIST table function has been added. This table function returns a list of all statements (sections) executed by each procedure, external function, compiled function, compiled trigger, and anonymous block invoked since the database was activated. For more information, see MON_GET_ROUTINE_EXEC_LIST table function.
The MON_GET_SECTION_ROUTINE table function has been added. This table function returns a list of all procedures, external functions, compiled functions, and compiled triggers that might be invoked during the execution of the input section. For more information, see MON_GET_SECTION_ROUTINE table function.
The mon_rtn_data configuration parameter has been added. This configuration parameter controls the capture of routine invocations. You can access the stored information using the MON_GET_ROUTINE and MON_GET_ROUTINE_DETAILS table functions. For more information, see mon_rtn_data - Monitoring routine capture configuration parameter.
The mon_rtn_execlist configuration parameter has been added. This parameter controls the monitoring of statements executed by routines. When you enable routine executable list collection, the routine executable lists are returned by the MON_GET_RTN_EXEC_LIST table function. For more information, seemon_rtn_execlist - Monitoring routine executable list configuration parameter.
Enhancements to the LTRIM, RTRIM, and MOD scalar functions make these functions more compatible with other database products. For more information, see FP2: Scalar function enhancements.
Enhancements to distinct types allow you to use strong typing or weak typing rules when creating this user-defined type. For more information, see FP2: Distinct type support for weak typing.
A new user-defined data type called SUBTYPE that is based on an existing built-in data types is now available. For more information, see FP2: SUBTYPE support added.
RDF application development support has been extended and store management simplified. For more information, see RDF application development enhancements.
The DB2DSDRIVER_CFG_SOURCE_PATH keyword now accepts a customized db2dsdriver configuration file during silent installation on Windows platforms. For more information, see IBM Data Server Driver Package (Windows).
If you have DBADM authority, you can now continue or cancel ongoing ADMIN_MOVE_TABLE operations. In previous releases, only the same authorization ID that initiated the online move table operation could continue or cancel it. For more information, see ADMIN_MOVE_TABLE procedure - Move tables online.
The ADMIN_MOVE_TABLE procedure now supports moving tables with referential integrity constraints. In previous releases, you needed to disable the referential integrity check temporarily before issuing the ADMIN_MOVE_TABLE procedure. For more information, see ADMIN_MOVE_TABLE procedure - Move tables online.
With the new DB2_MAX_GLOBAL_SNAPSHOT_SIZE registry variable, you can set the size of global snapshots. For more information, see the "DB2_MAX_GLOBAL_SNAPSHOT_SIZE" entry in General registry variables.
Backup and restore statistics are now automatically generated after the successful completion of the operation. For more information, see Backup and restore statistics.
DMS and AS page validation of backup images is now supported by the db2adutl db2ckbkp utilities, as well as during the execution of the BACKUP DATABASE command. For more information, see db2adutl, db2ckbkp, and BACKUP DATABASE .
You can now specify that some backups can succeed even if they do not contain all of the necessary log files. For more information, see BACKUP DATABASE.
The installDSDriver command can install the 32-bit libraries in the 64-bit IBM Data Server Driver Package installation. For more information, see Installing the IBM Data Server Driver Package software on the Linux and UNIX operating systems.
The installDSDriver command can upgrade the existing IBM Data Server Driver Package installation. For more information, see installDSDriver - Extract IBM Data Server Driver components command.
The DB2DSDRIVER_CFG_PATH registry variable can accept multiple paths for the db2dsdriver.cfg file. For more information, see Miscellaneous variables.
The CLI driver that is included with this fix pack contains several enhancements. For more information, see CLI driver enhancements.
The IBM Data Server Provider for .NET that is included with this fix pack contains several enhancements. For more information, see IBM Data Server Provider for .NET enhancements.
Specify the DB2_ODBC_DSN_TYPE and DB2_ODBC_DSN_ACTION keywords to register ODBC DSNs during silent installation on Windows platforms. For more information, see Connecting to databases for ODBC and CLI.
New table functions are available that allow the retrieval of information about routines. For more information, see FP2: Routines can be monitored.
The ARRAY_AGG aggregation function now supports the generation of associative arrays and arrays with a row element type. For more information, see FP2: ARRAY_AGG aggregate function enhancements.
The SQL communications area (SQLCA) structure now contains information about SQL PL and PL/SQL runtime errors. For more information, see FP2: Error locating in SQLCA expanded.
Enhancements are available that help support debugging in Optim™ Data Studio. For more information, see IBM Data Studio routine development support.
Support is added for pipelined table functions in PL/SQL and SQL PL. For more information, see FP2: Pipelined table function support added.
Versions of the IBM Data Server Driver for JDBC and SQLJ that are included with this fix pack contain several enhancements. For more information, see FP2: Driver enhancements.
Replication is now supported for bitemporal tables. For more information, see Utilities and tools.
Embedded SQL applications can use structure types, structure arrays, and structure indicator arrays. For more information, see Compatibility features for migration.
DB2 precompiler can suppress unspecified indicator variable error when the required NULL indicator is not specified. For more information, see Compatibility features for migration.
Embedded SQL applications can use EXEC SQL ROLLBACK and EXEC SQL COMMIT statements with the RELEASE option. For more information, see Compatibility features for migration.

Fix Pack 1

Fix Pack 1 includes the following changes:

The behavior of the DB2 call level interface (CLI) is changed when you specify both the SchemaList and SchemaFilter keywords with *USRLIBL value for connections to DB2 for i. For more information, see SchemaFilter IBM Data Server Driver configuration keyword and SchemaList CLI/ODBC configuration keyword.
The default values of selected IBM Data Server Driver configuration keywords that are associated with automatic client reroute is changed. For more information, see FP1: Default values of selected automatic client reroute IBM Data Server Driver keywords have changed.
The default value or behavior of selected IBM Data Server Driver configuration keywords have changed. For more information, see FP1: Default value or behavior of selected IBM Data Server Driver keywords have changed.
The behavior of IBM Data Server Provider for .NET is changed if you specify both the SchemaFilter keyword and the DB2ConnectionStringBuilder.SchemaList property with a *USRLIBL value for connections to DB2 for i. For more information, see SchemaFilter IBM Data Server Driver configuration keyword and DB2ConnectionStringBuilder.SchemaList Property.
The Informix® .NET provider (IBM.Data.Informix.dll) is deprecated. For more information, see FP1: Informix .NET provider (IBM.Data.Informix.dll) is deprecated

Fix Pack 1 also contains the following enhancements:

XML data type can now be specified when creating global variables, specifying parameters to create compiled SQL functions, or defining local XML variables in compiled SQL functions. For more information, see FP1: XML data type support added in global variables and compiled SQL functions.
The statistics event monitor now has additional logical data groups that make it possible to you view metrics monitor elements directly and from XML documents. In addition, you have the option of viewing metrics data for each monitoring interval or viewing values that have accumulated since the last database activation. See FP1: New logical data groups added to the statistics event monitor, FP1: New XML document stores metrics collected by statistics event monitor for more information.
Windows system environment variables are now updated to include the IBM Data Server Driver Package path. For more information, see System environment variables for IBM Data Server Driver Package (Windows)
You can now check the status of Net Search Extender text indexes. For more information, see Validating a text index (Windows, AIX®)
Support was added for transactional control in compiled language SQL user-defined functions (UDFs). When you set the DB2_COMPATIBILITY_VECTOR registry variable to support runtime routine SQL data-access-level enforcement, COMMIT and ROLLBACK statements are allowed in compiled PL/SQL UDFs and compiled SQL PL UDFs if the functions are defined with the MODIFIES SQL DATA clause using the CREATE FUNCTION statement. For more information, see SQL data access level enforcement.
The FLUSH FEDERATED CACHE statement was added. This SQL statement flushes the federated cache, allowing fresh metadata to be obtained the next time an SQL statement is issued against the remote table or view using a federated three part name. For more information, see FLUSH FEDERATED CACHE statement.
You can now use an in-database approach to analytics in the data warehouse by running a SAS embedded process on the DB2 database server. For more information, see In-database analytics with SAS embedded process support added.
The ADMIN_MOVE_TABLE stored procedure now has a REDIRECT option that forwards changes directly to the target table instead of capturing the changes in the staging table. For more information, see ADMIN_MOVE_TABLE procedure - Move tables online.
The CLI driver that is included with this fix pack contains several enhancements. For more information, see CLI driver enhancements.
The IBM Data Server Provider for .NET that is included with this fix pack contains several enhancements. For more information, see IBM Data Server Provider for .NET enhancements.
The installDSDriver command on UNIX and Linux operating systems now creates the db2profile and db2cshrc files to set required environment variables. For more information, see installDSDriver - Extract Data Server Driver components command.
Embedded SQL applications can use timeout values specified in the db2dsdriver.cfg file. For more information, see Use of the db2dsdriver.cfg configuration file by embedded SQL applications.
Embedded SQL applications can call a stored procedure using three-part name. For more information, see Enabling compatibility features for migration.
Embedded SQL applications can call a stored procedure using the new syntax. For more information, see Enabling compatibility features for migration.
Embedded SQL applications can use the WHENEVER condition DO action statement to take a specified action when an exception condition occurs. For more information, see WHENEVER statement .
You can now use the fcm_parallelism configuration parameter to control the degree of parallelism that is used for communication between members within a DB2 instance. For more information, see FCM parallelism support added.
You can specify the UOWTOTALTIME threshold value in multiples of 10 seconds. For more information, see FP1: Time-based thresholds support finer granularity.
The threshold violation event monitor now captures more information about the application that violated a threshold. For more information, see FP1: Threshold violations event monitor collects more application information.
Versions of the IBM Data Server Driver for JDBC and SQLJ that are included with this fix pack contain several enhancements. For more information, see FP1: Driver enhancements.