DB2 Version 9.7 for Linux, UNIX, and Windows

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

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

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.

Review the technical changes and new functionality that are included in the following Version 9.7 fix packs. Each fix pack for a release is cumulative: it contains all the technical changes and new functionality that were included in previous fix packs for that release.

Fix Pack 9
Fix Pack 8
Fix Pack 7
Fix Pack 6
Fix Pack 5
Fix Pack 4
Fix Pack 3a
Fix Pack 3
Fix Pack 2
Fix Pack 1

Fix Pack 9

Fix Pack 9 contains the functionality of previous fix packs and includes the following enhancement:

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.
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 FP9: Enhanced encryption through NIST SP 800-131A compliance.

Fix Pack 8

Fix Pack 8 contains the functionality of the previous fix packs and includes the following changes:

The IBM® DB2 SQL Skin Feature 1.0 for applications compatible with Sybase ASE is discontinued. For more information on Sybase migration to DB2 database products, contact IBM services at http://www-01.ibm.com/software/data/db2/lowerdatabasecosts/migrate-to-db2.html.

Fix Pack 7

Fix Pack 7 contains the following enhancements:

Additional client identification fields have been added to the MON_GET_CONNECTION and MON_GET_UNIT_OF_WORK table functions. For more information, see client_hostname - Client hostname and client_port_number - Client port number.
Users with DBADM authority 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.
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.
A new option, -hadr has been added to the db2fodc command to collect HADR related data, to help speed up the HADR problem determination process. The -detect option of the db2fodc command has been updated to detect HADR congestion. For more information, see ../../com.ibm.db2.luw.admin.trb.doc/doc/r0060755.html and ../../com.ibm.db2.luw.admin.trb.doc/doc/r0060632.html.
Diagnosing DB2 trace files is now easier with the new formattedFlow and perfrep options that have been added to the db2trc command. These options parse binary dump files into readable text and create performance reports. For more information, see ../../com.ibm.db2.luw.admin.trb.doc/doc/c0060647.html and ../../com.ibm.db2.luw.admin.trb.doc/doc/c0060648.html.
Support for Windows 8 operating system and Windows 2012 Server. For more information, see Installation requirements for DB2 servers and IBM data server clients (Windows).

Fix Pack 6

Fix Pack 6 contains the functionality of the previous fix packs and 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 data server driver keywords that are associated with automatic client reroute is changed. For more information, see Default values of selected automatic client reroute IBM Data Server Driver keywords have changed.
The default value or behavior of selected data server driver keywords have changed. For more information, see Default value or behavior of selected IBM Data Server Driver keywords have changed.
The behavior of IBM .NET Data Provider 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.
New logical groups have been added to the CREATE EVENT MONITOR statement for the statistics event monitor. For more information, see FP6: New logical data groups added to the statistics event monitor.

Fix Pack 6 also contains the following enhancements:

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 FP6: Driver versions enhancements.
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.
Restrictions on the Processor Value Unit (PVU) limit for DB2 Workgroup Server Edition were removed. For more information, see Processor Value Unit pricing.
The db2mscs command now provides the -user and -passwd parameters to avoid specifying this information in the db2mscs.cfg file. For more information, see db2mscs - Set up Windows failover utility command.
The SQL_BINARY and SQL_VARBINARY SQL data types are now supported with DB2 for i V6R1 and later. For more information, see SQL data type representation in ADO.NET database applications.
You can now specify the XML data type when creating global variables, specifying parameters to create compiled SQL functions, or defining local XML variables in compiled SQL functions. For more information, see FP6: XML data type support added in global variables and compiled SQL functions.
CLI now supports certificate authentication with DB2 for z/OS® Version 10 and later. For more information, see Authentication IBM Data Server Driver configuration keyword.
CLI now supports SQL BINARY and SQL VARBINARY data types for DB2 for i Version 6 Release 1 and later. For more information, see SQL symbolic and default data types for CLI applications.
CLI now supports array input by using the SQL_ATTR_PARAMSET_SIZE statement attribute, inside a trusted procedure body. For more information, see Statement attributes (CLI) list.
CLI now supports retrieval of the server time for COMMIT or ROLLBACK SQL operations on DB2 for z/OS Version 10 and later. For more information, see Connection attributes (CLI) list.
CLI now supports the SQL_C_CURSORHANDLE C data type for use with the SQL_CURSORHANDLE SQL data type. For more information, see SQL symbolic and default data types for CLI applications.
CLI now supports the QueryTimeout keyword in the db2dsdriver.cfg file. For more information, see QueryTimeout IBM Data Server Driver configuration keyword.
You can specify LDAP variables using the data server driver keywords. For more information, see Call level interface (CLI) functionality has been enhanced.
Windows system environment variables are now updated to include the IBM Data Server Driver Package path. For more information, see FP6: Environment variables now contain the driver path (Windows).
You can now check the status of NSE text indexes. For more information, see FP6: New utility validates a Net Search Extender text index (Windows, AIX).
You can use the SQLCODEMAP Data Server Driver configuration keyword or the SQLCODEMAP CLI/ODBC keyword to specify whether SQLCODE is used or turned off. For more information, see SQLCODEMAP IBM Data Server Driver Configuration Keyword.
IBM .NET Data Provider now supports changing a user password by using the DB2ConnectionStringBuilder.NewPWD property. For more information, see DB2ConnectionStringBuilder.NewPWD Property.
IBM .NET Data Provider now supports setting the CURRENT SQLID special register on DB2 for z/OS servers by using the new CurrentSQLID IBM Data Server Driver configuration keyword or the DB2ConnectionStringBuilder.CurrentSQLID property. For more information, see DB2ConnectionStringBuilder.CurrentSQLID Property.
IBM .NET Data Provider now supports setting the FetchBufferSize IBM Data Server Driver configuration keyword to configure the buffer size that is used by fetch requests. For more information, see FetchBufferSize IBM Data Server Driver configuration keyword.
You can use the ZOSDBNameFilter IBM Data Server Driver configuration keyword or DB2ConnectionStringBuilder.DBName property to filter the query result of DB2 for z/OS base tables. For more information, see DB2ConnectionStringBuilder.DBName Property.
IBM .NET Data Provider now supports CERTIFICATE authentication with DB2 for z/OS Version 10 and later. For more information, see DB2ConnectionStringBuilder.Authentication Property.
You can use the CacheUSRLIBLValue property to cache *USRLIBL for connections to DB2 for i V6R1 and later. For more information, see DB2Connection.CacheUSRLIBLValue Property.
IBM .NET Data Provider now supports the DelimIdent keyword and provides a default value for the ClientWorkStation property. For more information, see IBM Data Server Provider for .NET is enhanced.
IBM .NET Data Provider now supports DB2DataTime structure for use with Informix® database server. For more information, see DB2DateTime Structure.
IBM entity provider supports DB2 and Informix functions for LINQ to Entities queries. For more information, see Provider support for Microsoft Entity Framework.
New fields are added to the DB2Decimal class. For more information, see IBM Data Server Provider for .NET is enhanced.
You can use the db2dsdriver.cfg file to set the DIAGLEVEL keyword. For more information, see Diaglevel IBM Data Server Driver configuration keyword.
New properties and methods are added to the DB2Blob and DB2Clob classes. For more information, see IBM Data Server Provider for .NET is enhanced.
You can use the ClearUSRLIBLCache method to clear the *USRLIBL cache for connections to DB2 for i V6R1 and later. For more information, see DB2Connection.ClearUSRLIBLCache Method.
Enhancements to the db2cli command include new features to the registerdsn parameters in Windows. For more information, see Call level interface (CLI) functionality has been enhanced.
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.
Seamless automatic client reroute is enhanced. The CLI driver can now perform seamless failover when a COMMIT or ROLLBACK statement is issued against an unreachable server after all the data is returned. For more information, see Call level interface (CLI) functionality has been enhanced.
Enhancements to CLI include support for client information properties against DB2 for i. For more information, see Call level interface (CLI) functionality has been enhanced.
The threshold violation event monitor now captures more information about the application that violated a threshold. For more information, see FP6: Threshold violations event monitor collects more application information.
The statistics event monitor is enhanced with additional logical data groups that make it possible to view metrics monitor elements directly, instead of from XML documents. These new logical data groups present versions of each monitor element that shows the change in value of that monitor element since the last statistics collection or database activation, whichever was more recent. In addition, a new element was added to the output statistics event monitor that collects these metrics into a single XML document. For more information, see FP6: New logical data groups added to the statistics event monitor, FP6: XML document metrics stores system metrics collected by statistics event monitor.
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.
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.
You can specify the UOWTOTALTIME threshold value in multiples of 10 seconds. For more information, see Time-based thresholds support finer granularity.
The REBIND command now has a FUNCPATH parameter that specifies the function path to resolve user-defined distinct types and functions in static SQL. For more information, see REBIND command.
The db2look command has a new -noimplschema parameter. If you specify this parameter with the -e parameter, the CREATE SCHEMA DDL statements for implicitly created schemas are not generated. For more information, see Upgrade impact from DB2 command changes.
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.

Fix Pack 5

Fix Pack 5 contains the functionality of the previous fix packs and includes the following changes:

The IBM Software Development Kit for Java™ that is packaged with DB2 products now use the Java 6.0.9.1 version. This Java version is now the minimum level supported by DB2 products. It addresses a critical security vulnerability (CVE-2010-4476) that might cause the Java Runtime Environment to hang. For more information about Java versions that are bundled with DB2 products, see Java software support for DB2 products.
Starting with Version 9.7 Fix Pack 5, GSKit V8 is the supported version. The installation of DB2 database server product includes GSKit V8. If you have applications that use GSKit V7, you must update IBM DB2 Data Server Client to use GSKit V8 to prevent application failure. For more information on how to install the latest supported version of GSKit libraries, refer to the IBM Global Security Kit global installation instructions overview.
On Windows operating systems, IBM Tivoli® System Automation for Multiplatforms (SA MP) 3.2 is now bundled with the DB2 installation media. For Tivoli SA MP levels on all supported operating systems, see Supported software and hardware for IBM Tivoli System Automation for Multiplatforms (SA MP).
PL/SQL statement compilation and execution is now supported for DB2 Express-C. For a list of restrictions on PL/SQL support, see Restrictions on PL/SQL support
The history file will no longer be exclusively locked during the automatic deletion of recovery objects or during prune operations which delete the physical files. For more information, see FP5: History file no longer locked during automatic deletion of recovery objects.
If DB2_RESTORE_GRANT_ADMIN_AUTHORITIES is set to ON, restores to an existing database is automatically granted SECADM and DBADM authorities. For more information, see System environment variables.
The self-tuning memory manager (STMM) shared memory segment now has owner-read and owner-write permissions only. On systems with multiple instances, this introduces compatibility issues against databases belonging to downlevel instances where the database_memory configuration parameter is set to AUTOMATIC. If you do not upgrade all instances simultaneously and any of the upgraded instances are root installations, downlevel instances will be unable to have overall database memory usage tuned by STMM. To mitigate this problem, use the new DB2STMM registry variable to revert to the previous non-restrictive permissions for the STMM shared memory segment. For more information, see Miscellaneous variables.
DB2 Geodetic Data Management Feature has been deprecated and might be removed in a future release. For more information, see FP5: IBM DB2 Geodetic Data Management Feature software has been deprecated.
Microsoft Visual Studio 2005 support has been deprecated and might be removed in a future release. For more information, see FP5: Microsoft Visual Studio 2005 support has been deprecated.

Fix Pack 5 also contains the following enhancements:

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 FP5: Driver versions enhancements.
The new super asynchronous (SUPERASYNC) HADR synchronization mode which ensures that transactions can never be blocked or experience elongated response times due to network interruptions or congestion. For more information, see FP5: Super asynchronous HADR synchronization mode has been added.
You can now query inline values of XML and large object (LOB) types when you use the HADR reads on standby feature. For more information, see HADR reads on standby feature.
The IBM COBOL for AIX® Version 3.1 and Version 4.1 compilers are now supported for both 32-bit and 64-bit DB2 database application development. For more information, see Support for database application development in COBOL.
Enhancements to facilitate the migration of embedded SQL C applications from other database systems. The following enhancements are included:
- Support of local scope for host variables
- The BREAK action in a WHENEVER statement
- Use of a string literal to prepare a statement
- The VARCHAR and int types
- The sqlglm() function to retrieve the complete error message text
For more information, see Host variable names in C and C++, Supported SQL data types in C and C++, and Enabling compatibility features for migration.
The new EXCLUDE, PRECHECK, and QUIESCE DATABASE command parameters for the REDISTRIBUTE DATABASE PARTITION GROUP command make it easier to prevent errors and perform early error detection. For more information, see FP5: Access control, error checking, and table exclusion during data redistribution have been improved.
IBM solidDB® Universal Cache is now bundled with IBM Database Enterprise Developer Edition. See FP5: IBM Database Enterprise Developer Edition product bundle extended
Additional diagnostic information that is available through the db2pd command makes it easier to troubleshoot load operations. You can obtain the diagnostic information by using the enhanced -utilities parameter and the new-load parameter. For more information, see FP5: Load serviceability has been improved.
Examining databases for architectural correctness through the db2dart command is improved to increase its performance. The /QCK option and other options and actions are updated to help improve the performance of the db2dart command. For more information, see FP5: db2dart command has extended functionality that helps improve performance.
First occurrence data collection (FODC) supports new manual collection types for problems related to processor usage, memory usage, and database connections. FODC now also automatically collects diagnostic data when a user-defined threshold condition is exceeded. For more information, see FP5: First occurrence data collection supports new collection types and collection triggered by user-defined thresholds.
If you work with relational database products other than the DB2 product, Fix Pack 5 contains enhancements that make the DB2 product more familiar to you. For more information, see FP5: SQL compatibility has been enhanced.
You can now use the db2adutl command to upload locally stored backup images to Tivoli Storage Manager (TSM). For more information, see FP5: db2adutl enhancements simplify backup image and log file management.
Two new monitoring functions have been added to let you examine memory usage. For more information, see FP5: New monitoring table functions return information about memory.
You can now invoke the DB2GSE.ST_REGISTER_SPATIAL_COLUMN stored procedure to calculate geographic extents for spatial data. You can display the geographic extent information by querying the DB2GSE.ST_GEOMETRY_COLUMNS catalog view. For more information, see ST_REGISTER_SPATIAL_COLUMN stored procedure.
You can specify the ACTIVITYTOTALTIME threshold value in multiples of 10 seconds. For more information, see Time-based thresholds support finer granularity.
You can use table space modification information to make more informed decisions about the way that you perform backups. This information can be displayed through a new suboption for the db2pd -tablespaces command or a new MON_GET_TABLESPACE table function monitor element. For more information, see FP5: Table space modification status can be checked.
Allocating trace resources for the trace facility (which you invoke with the db2trc command) for remote clients can help improve application performance. Also, you can trace the operations of clients that use a fenced procedure. For more information, see FP5: db2trc command has been improved for clients.
The DB2 Design Advisor can now be called within an SQL statement using the new DESIGN_ADVISOR procedure. For more information, see the DESIGN_ADVISOR procedure.
Troubleshooting problems that arise from unsuccessful upgrades is now made easier by support for collecting diagnostic data before the upgrade operation. You can collect the pre-upgrade data by specifying the new -preupgrade parameter for both the db2fodc command and the db2support command. You can collect additional data after the upgrade operation to help troubleshoot an instance creation problem by specifying the new -clp parameter for the db2fodc command. For more information, see FP5: Diagnosing upgrade problems is easier.
You can now use the COPY_USE_LOAD option to specify that the ADMIN_MOVE_TABLE procedure is to perform recoverable load operations. For more information, see FP5: ADMIN_MOVE_TABLE stored procedure now supports recoverable load.
Merged backup images are now fully integrated with automatic recovery utilities and database history management infrastructure. For more information, see FP5: Automatic recovery utilities now recognize merged backups.
Several administrative views and table functions for monitoring database systems have been updated. The affected routines are MON_BP_UTILIZATION, MON_GET_BUFFERPOOL, MON_GET_TABLE, and MON_GET_TABLESPACE. For more information, see FP5: Some administrative routines and views have changed.
You can use three new table functions to retrieve system and network information with SQL queries. These functions are intended to replace the table function ENV_GET_SYS_RESOURCES and the administrative view ENV_SYS_RESOURCES, which are deprecated as of this fix pack. For more information, see FP5: New table functions provide SQL-based access to system information.
You can now use the CurrentPackageSet IBM data server driver configuration keyword to issue the SET CURRENT PACKAGESET SQL statement. For more information, see CurrentPackageSet IBM data server driver configuration keyword.

Fix Pack 4

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

Support to perform distributed installations using Microsoft Systems Management Server on Windows operating systems has been deprecated. For more information, see FP4: Distributed installation support with Microsoft Systems Management Server is deprecated (Windows).
The DB2 Health Advisor has been deprecated. For more information, see FP4: DB2 Health Advisor has been deprecated.

Fix Pack 4 also contains the following enhancements:

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 FP4: Driver versions enhancements.
A new aggregate function, LISTAGG, has been added. The LISTAGG function aggregates a set of string elements into one string by concatenating the strings. Optionally, a separator string can be provided which is inserted between contiguous input strings. For more information, see LISTAGG aggregate function.
You can use pattern expressions in a LIKE predicate which are based on other columns. The LIKE predicate can therefore be used as a fuzzy join predicate where the joined table provides the pattern. You can, for example, look up patterns such as area codes to filter telephone numbers from another table. For more information, see LIKE predicate.
You can specify two-part names for tables and views with the db2look command to specify the schema of the table or view. In addition, the new -xdep and -xddep parameters generate authorization DDL statements (for example, GRANT statements) on the tables, specified by either the -t or -tw parameter, and their dependent objects. For more information, see FP4: db2look command enhances DDL statement generation for database objects and dependents.
The WLM_COLLECT_STATS procedure now takes an input parameter called wait, which specifies that the procedure does not return until all the statistics have been written and flushed to the statistics event monitor tables. If you do not specify this parameter, the procedure returns immediately after initiating a statistics collection and reset. Monitoring tools can use the new functionality to collect WLM statistics in synchronous mode so that the tools are aware that all the data has been written to the statistics event monitor tables by the time the procedure returns. For more information, see WLM_COLLECT_STATS procedure - Collect and reset workload management statistics.
IBM Tivoli System Automation for Multiplatforms (SA MP) support enhanced for High Availability Disaster Recovery on Windows operating systems. New scripts have been added to improve the integration between DB2 High Availability Disaster Recovery (HADR) and IBM Tivoli System Automation for Multiplatforms (SA MP) on Windows operating systems. For more information, see FP4: New scripts improve integration between DB2 High Availability Disaster Recovery and IBM Tivoli System Automation for Multiplatforms (Windows).
Roving high availability (HA) failover support for partitioned database environments using the N plus M failover policy. For more information, see FP4: Roving high availability (HA) failover reduces downtime in partitioned database environments.
You can use the -recovery option of the db2pd command to determine whether the catalog database partition has failed. For more information, see db2pd - Monitor and troubleshoot DB2 database command.
With the new db2cklog tool, you can now check the validity of archive log files before using these files during a rollforward recovery operation. For more information, see FP4: Archive log files can be checked for validity.
You can now upgrade your DB2 Text Search server for quicker indexing and better search capabilities. For more information, see FP4: DB2 Text Search infrastructure improvements.
The CREATE TRIGGER statement has changed. A trigger event clause can contain UPDATE, DELETE, and INSERT operations together in a single clause. Additionally, a BEFORE trigger can contain UPDATE, DELETE, INSERT, and modifying data routines in a compound SQL (compiled) statement. For more information, see FP4: CREATE TRIGGER statement enhancements.
Support to perform distributed installations using Microsoft Systems Center Configuration Manager on Windows operating systems has been added. For more information, see Installation of DB2 products using Microsoft Systems Center Configuration Manager (SCCM)
Diagnostic data logging has become more resilient. You can now set an alternate path for diagnostic data with the new alt_diagpath database configuration parameter. This parameter specifies an alternate path for diagnostic data logging that is used when the primary diagnostic path is unavailable. For more information, see FP4: New configuration parameter reduces risk of losing diagnostic data.
The serviceability of large database systems has been improved. A number of functional enhancements have been made that address common pain points on large database systems, resulting in: Reduced amounts of accumulated diagnostic data; reduced overhead due to data collection on large systems; improvements to the accessibility of diagnostic data to service personnel; and, improvements to the ease of use of troubleshooting tools in complex systems. For more information, see FP4: The serviceability of large database systems has improved
Access to activity metrics in the activity event monitor is simplified with the new activitymetrics logical data group. For more information, see FP4: Simplified access to activity metrics in the activity event monitor.
Enhancements to facilitate the migration of embedded SQL C applications from other database systems. These compatibility features enable you to use C-array host variables and indicator variable arrays with FETCH INTO statements, extensions to CONNECT statement syntax, double quotation marks to specify file names with the INCLUDE statement, and the DYNAMIC_SQL option for the BIND command, to provide true dynamic SQL behavior. For more information, see Enabling compatibility features for migration
Enhancements to the DB2 Call Level Interface (CLI) include new command parameters, connection attribute, and functions. In addition, the db2diag.log path on Windows has changed and new log options are now available. For more information, see Call level interface (CLI) functionality has been enhanced.
Enhancements to facilitate the migration of embedded SQL C applications from other database systems. These compatibility features enable you to use C-array host variables and indicator variable arrays with FETCH INTO statements, extensions to CONNECT statement syntax, double quotation marks to specify file names with the INCLUDE statement, and the DYNAMIC_SQL option for the BIND command, to provide true dynamic SQL behavior. For more information, see Enabling compatibility features for migration
The IBM XL C/C++ Enterprise Edition Version 11.0 compiler is now supported for DB2 database application development on the AIX platform. For more information, see Support for database application development in C and Support for database application development in C++.
Support for .NET Framework has been enhanced. Starting in Version 9.7 Fix Pack 4, IBM Data Server Provider for .NET supports .NET Framework 4.0. For more information, see Support for .NET development software
In Version 9.7 Fix Pack 4 and later fix packs, IBM Visual Studio Add-Ins support Visual Studio 2010. For more information, see Supported IBM Data Servers and System Requirements
In Version 9.7 Fix Pack 4 and later fix packs, IBM Data Server Provider for .NET supports FitHighPrecisionType keyword. For more information, see the FitHighPrecisionType Property.
In Version 9.7 Fix Pack 4 and later fix packs, IBM Data Server Provider for .NET and IBM Visual Studio Add-Ins no longer support U2 servers.
New installFixPack command parameter enhances ability to apply fix packs. For more information, see FP4: Installation fix pack support has been extended.

Fix Pack 3a

Fix Pack 3a contains the functionality of the previous fix packs and includes the following change:

For the DB2 Workgroup Server Edition the maximum allowed memory is increased from 16 GB to 64 GB.

Fix Pack 3a contains the following enhancement:

Several advanced product capabilities are available in the DB2 database product DB2 Advanced Enterprise Server Edition for Linux, UNIX, and Windows. For more information, see FP3: Advanced product capabilities.

Fix Pack 3

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

LOB strings that have an actual length less than 32673 bytes are now supported as operands in basic predicates, IN, BETWEEN and the simple CASE expression. In comparisons using the LIKE predicate, NULL predicate, and the POSSTR function, LOB strings of any length continue to be supported.
HP-UX 32-bit client support has been deprecated and might be discontinued in a future release. For more information, see FP3: HP-UX 32-bit client support has been deprecated.
The settings of the DB2_ITP_LEVEL registry variable are ignored and have no effect on backup operations. For more information, see Some registry and environment variables have changed.
Trap resilience functionality, a feature that keeps the instance active if certain traps occur, has now been extended to the load utility. For more information, see Enhanced resilience to errors and traps reduces outages.

Fix Pack 3 also contains the following enhancements:

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 FP3: Driver versions enhancements.
Support for the AIX 7.1 operating system. For more information, see Installation requirements for DB2 servers and IBM data server clients (AIX).
You can specify that the system controller thread does not adjust resources below specific values by using the new FCM_CFG_BASE_AS_FLOOR option of the DB2_FCM_SETTINGS registry variable. For more information, see DB2_FCM_SETTINGS.
Improved support for target storage devices that support data deduplication. For more information, see FP3: Data deduplication device support has been integrated into the backup utilities.
DB2 Text Search and Net Search Extender text indexes can now coexist on the same table column. For more information, see FP3: DB2 Text Search and Net Search Extender index coexistence.
Range-clustered tables (RCT) are supported in a partitioned database environment. The distribution key must be a single column subset of the range-clustered table key. For more information, see Restrictions on range-clustered tables.
A new tool db2caem (db2 Capture Activity Event Monitor data tool) has been created to simplify the process of capturing detailed diagnostic and runtime information about one or more statements. New db2support options have been added for the optimizer mode to collect the data captured by db2caem. For more information, see FP3: Simplify capture of detailed statement information using the new db2caem tool with db2support integration options.
Two new features have been added to improve the granularity of the db2trc tool, these are an ability to trace only the members (or partitions) specified and an ability to trace based on a specific application ID (or application handle). For more information, see FP3: Improvements to the granularity of the db2trc tool.
A new OLAP specification, RATIO_TO_REPORT, can be used to provide the ratio of a value compared to the sum of a group of values. For more information, see OLAP specifications.
A new database configuration parameter, CONNECT_PROC, can be used to input a two part procedure name. This procedure is used as the connect procedure to customize the settings for the application environment when connecting to a database. For more information, see FP3: Application environments can be customized during the connection process.

Fix Pack 2

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

If DB2_RESTORE_GRANT_ADMIN_AUTHORITIES is set to ON, and you are restoring to a new database, then SECADM, DBADM, DATAACCESS, and ACCESSCTRL authorities are granted to the user that issues the restore operation. For more information, see System environment variables.
COBOL and FORTRAN language support for the db2History APIs has been deprecated and might be discontinued in a future release. For more information, see FP2: COBOL and FORTRAN language support has been deprecated for db2History APIs.
The database manager uses a new formula to automatically adjust kernel parameter settings so that manual adjustments are not required to update Linux kernel parameters related to interprocess communication (IPC). For Version 9.7 Fix Pack 1 or earlier, you might still need to adjust your Linux kernel parameter settings. For more information, see Kernel parameters requirements ( Linux ).
The DB2 Advanced Copy Services (ACS) component is no longer automatically installed during a compact installation. For more information, see FP2: DB2 Advanced Copy Services (ACS) is not automatically included in a compact installation.
Issuing the db2updv97 command is mandatory in order to execute the SYSPROC.ADMIN_GET_MSGS table function. However, after the db2updv97 command is issued, if you are reverting back to Version 9.7 Fix Pack 1 or earlier, you are required to contact DB2 Support in order to have this table function run. For more information, see db2updv97 - Update database to Version 9.7 fix pack command

Fix Pack 2 also contains the following enhancements:

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 versions enhancements.
National character support has been extended by means of NCHAR, NCLOB, and NVARCHAR. For more information, see National character strings.
New scalar functions have been added to assist with national character support; NCHAR, NCLOB, NVARCHAR, TO_NCLOB, and TO_NCHAR. For more information, see Supported functions and administrative SQL routines and views.
Procedure enhancements introduced at Version 9.7 have been extended to user-defined functions (UDFs):
- The ability to create UDFs and specify default values for parameters
- The ability to invoke a UDF with named arguments
For more information, see Default values and named arguments promote flexibility for creating and calling procedures and functions.
You can use the new WAIT FOR OUTCOME keyword in a SELECT statement to indicate the concurrent access resolution. WAIT FOR OUTCOME specifies to wait for the commit or rollback when encountering data in the process of being updated, deleted, or inserted. For more information, see select-statement.
Support for applications on Solaris UltraSPARC and x64. For more information, see Support for database application development in C.
Tivoli Storage Manager (TSM) proxy nodes support. For more information, see FP2: Proxy node support for the db2adutl command has been added.
Integrated support for POWER7® systems and the SUSE Linux Enterprise Server (SLES) 11 distribution. For more information, see IBM Tivoli System Automation for Multiplatforms (SA MP) support has been improved.
The new RESTRICTED ACCESS option can be specified to prevent authorization checking for all connect attempts to the databases of a quiesced DB2 instance. The new option can also be used when there is a need to have exclusive connections to a database within the quiesced instance. For more information, see FP2: New RESTRICTED ACCESS option restricts database connections within quiesced instance.
You can use the RESTORE command with the TRANSPORT option to copy table spaces and SQL schemas as a set from a database backup image to another active database. For more information, see FP2: Databases can be restored using transportable sets.
You can obfuscate or encode the body of a routine, trigger, view, or PL/SQL package, so that the proprietary portion cannot be read by a user, but it is still understood by DB2 for Linux, UNIX, and Windows. For more information, see Obfuscation.
The db2pd -reorgs index command supports index reorg progress reporting for partitioned indexes. For more information, see Additional system monitoring information can be generated.
The db2pd command has additional functionality to help control which engine dispatchable units (EDUs) are included in the output, the ability to define a time interval in some cases, and improved stack output on Linux operating systems. For more information, see db2pd - Monitor and troubleshoot DB2 database.
Restrictions on the maximum size of core files (CORELIMIT) have been removed on AIX. For more information, see db2pdcfg - Configure DB2 database for problem determination behavior.
A new registry variable setting has been added to the DB2_WORKLOAD aggregate registry variable when it is set to SAP. For more information, see Some registry and environment variables have changed.
The DB2_SMS_TRUNC_TMPTABLE_THRESH registry variable has a new default setting which prevents unnecessary file system access for small temporary objects while still truncating large temporary objects to 0 extents. For more information, see Some registry and environment variables have changed.
The WLM_SET_CONN_ENV procedure enables for a particular connection the collection of activity data and measurement of section actuals (runtime statistics measured during section execution). For more information, see WLM_SET_CONN_ENV.
The WLM_GET_CONN_ENV table function returns for a particular connection the values of settings that control collection of activity data and section actuals. You can use this table function to check the current values of the settings applied by the WLM_SET_CONN_ENV stored procedure. For more information, see WLM_GET_CONN_ENV.
NULL indicators support has been extended to enable applications to use all-columns INSERT, UPDATE, and MERGE statements without having to specify the current value of columns whose values are not to be changed or inserted. For more information, see "References to host variables" in Identifiers.
Support for IBM Rational® Developer for zSeries v7. For more information see Support for database application development in COBOL.
Transparent LDAP authentication and group lookup support on AIX is extended to certify Kerberos authentication support. For more information, see FP1: Transparent LDAP authentication and group lookup is supported (Linux and UNIX).
Auditing improvements have been added to allow for the replay of past database activities. For more information, see FP2: Audit improvements allow replay of past database activities.
Two new table functions, MON_GET_FCM and MON_GET_FCM_CONNECTION_LIST, improve the monitoring of fast communications manager (FCM). For more information, see FP2: Identify FCM issues more easily.
The IBM Data Server Provider for .NET has been enhanced in several ways that might help with application performance, data server compatibility, and simplifying application development. For more information, see IBM Data Server Provider for .NET is enhanced.
Some queries using spatial data run faster in partitioned database environments. For more information, see FP2: Materialized query tables with spatial columns can be replicated.
When using the ADMIN_MOVE_TABLE procedure, you can use the new LOAD_MSGPATH option to define the load message file path. The FORCE option no longer needs to be specified with the COPY_USE_LOAD option. For more information see ADMIN_MOVE_TABLE procedure - Move an online table.
Restrictions on the DB2_SKIPDELETED registry variable during an online ADMIN_MOVE_TABLE procedure have been removed. For more information see ADMIN_MOVE_TABLE procedure - Move an online table.

Fix Pack 1

Fix Pack 1 includes the following changes:

The -file option of the db2rfpen command has been deprecated. For more information, see FP1: -file option of db2rfpen command has been deprecated.
The process to detach a data partition from a data partitioned table has been changed. For more information, see FP1: Detach operation for data partitions has been changed.
If an XML schema that is registered in the DB2 XSR uses the maxOccurs attribute where the value is greater than 5000, the maxOccurs attribute value is treated as if you specified "unbounded". For more information, see FP1: XML schema maxOccurs attribute values greater than 5000 are parsed differently.
The workload management statistics collection interval is synchronized relative to a day of the week and an hour of the day, rather than relative to when the DB2 instance was started. For more information, see FP1: Collection interval time for workload management statistics has changed.

Fix Pack 1 also contains the following enhancements:

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 versions enhancements.
Read operations support on High Availability and Disaster Recovery (HADR) standby databases. For more information, see FP1: Read operations on HADR standby databases are supported.
DB2 Advanced Copy Services (ACS) support for the AIX 6.1 operating system. For more information, see FP1: DB2 Advanced Copy Services (ACS) is supported on AIX 6.1.
Last referenced date support for some objects, which helps you understand when these were last used. For more information, see FP1: Last referenced date is available for tables, table partitions, indexes, and packages.
The SUBSTRB scalar function, which returns a substring of a string. For more information, see SUBSTRB scalar function.
Compiled user defined functions with OUT and INOUT parameters are supported in SQL PL. For more information, see SQL PL functionality has been extended for user-defined functions.
Global variables assignments in nested contexts are supported. For more information, see FP1: Global variable assignments in nested contexts are supported.
OUT and INOUT parameters are supported in user-defined functions. For more information, see FP1: User-defined functions support OUT and INOUT parameters.
Support for PL/SQL functions that modify the database. For more information, see CREATE FUNCTION statement (PL/SQL).
The IBM Data Server Provider for .NET includes multiple enhancements. For more information, see IBM Data Server Provider for .NET is enhanced.
The db2pd command has a new parameter that makes it easier to collect the fenced routines history information. For more information, see FP1: Fenced routines history information is easier to collect.
The DB2 PL/SQL compiler supports FORALL and BULK COLLECT INTO syntax. For more information, see FORALL statement (PL/SQL) and BULK COLLECT INTO clause (PL/SQL).
You can use new XQuery functions to retrieve current date and time values using the local time zone of the DB2 database system. For more information, see FP1: XQuery functions make it easier to retrieve date and time values for local time zones.
The diagpath database manager configuration parameter has new values, which allow you to store DB2 diagnostic data in separate directories named according to the physical host, database partition, or both. The db2diag command also has a new -merge parameter to merge multiple db2diag log files. For more information, see FP1: Diagnostic data can be stored in separate directories.
The new package cache event monitor captures information about cached statement entries after they have been flushed from the database package cache, which can help to resolve SQL query performance and problem determination issues. For more information, see FP1: New event monitor for dynamic and static SQL statements in package cache.
New lock-related relational monitoring interfaces replace deprecated snapshot interfaces. For more information, see FP1: New relational monitoring interfaces for locking events.
Runtime statistics are available for access plan operators. For more information, see FP1: Explain enhanced with actual values for operator cardinality.
Section explain functionality captures explain information about a statement using only the contents of the runtime section. For more information, see FP1: Statements from a runtime section can be explained.
New component time monitor elements can be combined with existing wait times monitor elements, provided in DB2 Version 9.7, to provide a comprehensive breakdown of time spent within the DB2 database manager. For more information, see Time-spent monitor elements are more comprehensive.
Time monitor elements, reported in XML documents, can be displayed and analyzed in a generic fashion using new row-based formatting functions. For more information, see FP1: Table functions for row-based formatting of monitoring information are available.
Package cache information can be retrieved in XML form using a new package cache details table function. For more information, see MON_GET_PKG_CACHE_STMT_DETAILS.
New administrative views encapsulate key queries using the new monitoring table functions introduced in DB2 Version 9.7 and V9.7 Fix Pack 1. For more information, see FP1: Monitoring table functions information can be viewed using administrative views.
A list of packages used within each unit of work can be obtained through the unit of work event monitor. For more information, see A new unit of work event monitor supports transaction monitoring.
Reorganization of data or indexes for a specific data partition of a data partitioned table. For more information, see FP1: Data partitions and partitioned indexes can be reorganized.
A partitioned table remains available during roll-out operations. For a partitioned table, a roll-out operation no longer takes the table offline. For more information, see FP1: Partitioned table data remains available during roll-out operations.
Multidimensional clustering (MDC) block indexes are partitioned when creating a table that uses both MDC and table partitioning. For more information, see Partitioned indexes on partitioned tables improve performance.
Distribution statistics are collected for indexes over XML data. For more information, see FP1: Distribution statistics collected for XML columns.
The ADMIN_MOVE_TABLE procedure has new options which prevent locking overhead on the target table in the copy and swap phases and improve the data movement speed. For more information, see Table data can be moved online using a new stored procedure.
Additional keywords can be added to the db2relocatedb command configuration file which makes it easier to relocate a database when the paths used are different. For more information, see FP1: relocating databases using the db2relocatedb command has been improved.
New routines, views, and modules for monitoring, workload management, and explaining statements have been added and some routines have been changed. For more information, see Some system catalog views, system-defined administrative routines and views have been added and changed.
You can monitor the progress of the RUNSTATS command as well as table and index reorganizations. For more information, see Additional system monitoring information can be generated.
Transparent LDAP is supported on the Linux, HP-UX, and Solaris operating systems. For more information, see FP1: Transparent LDAP authentication and group lookup is supported (Linux and UNIX).
32-bit GSKit libraries are now installed automatically. For more information, see FP1: 32-bit GSKit libraries are included in the 64-bit DB2 product installation.
Additional support is provided for the GB18030 code set. For more information, see FP1: GB18030 code set support has been extended.
DB2 database products installed on HP-UX operating systems now support long host names. For more information, see Installation requirements for DB2 servers and IBM data server clients (HP-UX).
Multiple result sets can now be returned from an SQL procedure by enabling multiple instances of the same cursor. For more information, see Returning result sets from SQL procedures.
The db2support tool includes new filtering options that you can use to gather specific diagnostic data more easily and an archiving option for storing diagnostic files in a different location. For more information, see FP1: db2support tool has been enhanced.
Work action sets can be defined at the workload level to control workloads, based on the type and size of work, before they enter the system. For more information, see FP1: Work action sets can be defined at workload level.
The UOWTOTALTIME threshold specifies the maximum amount of time that a unit of work may spend in the DB2 engine. For more information, see FP1: New time threshold limits unit of work duration.
A sample script (qpwlmmig.pl) has been provided to facilitate the migration from the deprecated DB2 Query Patroller environment to the DB2 workload manager environment. For more information, see FP1: Script facilitates migration from Query Patroller to workload manager.
A new optional AUTOGRANT command parameter for the DB2 Text Search ENABLE DATABASE FOR TEXT command, which tries to grant the necessary DBADM with DATAACCESS privileges to the instance owner when running the ENABLE command, in case the instance owner misses these privileges for this database.For more information, see db2ts ENABLE DATABASE FOR TEXT command.
For Linux operating systems, users can specify that activated databases are to use minimal processing resources when the database manager is idle, using a new registry variable DB2_MIN_IDLE_RESOURCES. For more information, see the "DB2_MIN_IDLE_RESOURCES" entry in Miscellaneous variables.
With the new DB2_USE_FAST_PREALLOCATION registry variable, the Veritas fast allocation file system feature can be used to reserve table space, and speed up the process of creating or altering large table spaces and database restore operations. For more information, see the "DB2_USE_FAST_PREALLOCATION" entry in Miscellaneous variables.
With the new DB2TCP_CLIENT_KEEPALIVE_TIMEOUT registry variable, users can specify a keep alive setting that is lower than the system default, allowing the database manager to detect connection failures sooner. For more information, see the "DB2TCP_CLIENT_KEEPALIVE_TIMEOUT" entry in Communications variables.
The DB2_WORKLOAD aggregate registry variable now has a new value, INFOR_ERP_LN, which configures a set of registry variables for Infor ERP Baan. For more information, see the "DB2_WORKLOAD" entry in System environment variables.