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.
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
- 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 offerings
DB2 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.
- The
following new DB2 offerings are available as add-ons to
different DB2 product editions:
-
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 offerings
DB2 database product editions and DB2 offerings
in .
- 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.
- Column-organized tables enhancements:
- BLU
Acceleration is now supported on these additional operating systems:
- Linux on zSeries. 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).
- Linux on POWER® for little endian. 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).
- Windows operating systems that are supported by and . For 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). Also see Additional installation considerations (Windows)
Additional installation considerations (Windows)
in .
Column-organized tables
in .
- BLU
Acceleration is now supported on these additional operating systems:
- 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 availability
High availability
in .
- introduced HADR database
support of column-organized tables. introduces BLU Acceleration
support on Windows operating systems, including HADR
databases. See Column-organized tables enhancements
-
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)
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.
- A
geographically dispersed cluster (GDPC)
environment is now supported on any x64 Intel compatible rack
mounted server which supports these Ethernet RoCE adapters:
- 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.
User-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 port
Specifying 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 .
- 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
- 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 rules
User, user ID and group naming rules
in .
- 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.
- 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 pack
db2checkCOL - 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 technote
Steps 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 .
DB2 Cancun Release 10.5.0.4
- Column-organized tables enhancements:
- You
can use a new type of column-organized table called shadow table to gain the
performance benefits of BLU Acceleration for the reports and other analytic queries that you perform
on your row-organized tables in OLTP databases. For more information, see Shadow
tables
Shadow tables
in the . - The
MERGE SQL statement is now supported for column-organized tables. For more
information, see Merge statement
Merge statement
in . - The performance of some statements with common table expressions that are running against column-organized tables can now be improved by executing the operations with common table expressions during column-organized data processing. For more information, see c0060601.html.
- You can now use the ADD
COLUMN clause of the ALTER TABLE statement to add any column type that is supported for
column-organized tables. For more information, see ALTER
TABLE statement
ALTER TABLE statement
in the . - Synopsis
tables can now include CHAR and VARCHAR columns.
This change can result in performance benefits
when these columns are well clustered. For more information, see Synopsis tables
Synopsis tables
in the . - Page-level
compression for insert operations is now enabled by default. Such operations, including import and
ingest operations, can take advantage of higher compression ratios and data clustering at the page
level for improved insert performance. For more information, see Column
compression dictionaries after a load or insert operation
Column compression dictionaries after a load or insert operation
in the . Additional compression enhancements might now be applied to VARCHAR and VARGRAPHIC data by default when dictionaries are built. - Index access
for SELECT statements that are executed with the cursor stability (CS) isolation level is now
supported. An additional runtime optimization is also available to help improve the performance of
column-organized CS index scans when the data does not require column-organized processing. For more
information, see Types of index access
Types of index access
in and c0060601.html. - You
can now create column-organized user-maintained materialized query tables (MQTs). This enhancement
is particularly useful if you are upgrading your DB2 server to
and
have existing MQTs. Help reduce upgrade costs by converting your MQTs into column-organized
user-maintained MQTs that are eligible to match queries that contain a mix of column-organized and
row-organized tables. For more information, see CREATE
TABLE statement
CREATE TABLE statement
in . - If an error occurs while you are
converting a row-organized table into a column-organized table, you can cancel pending conversion
changes by running the db2convert command with the new
-cancel
parameter.
For details, see db2convert - Convert row-organized tables into column-organized
tables
db2convert - Convert row-organized tables into column-organized tables
in the . - On AIX, Linux, or Windows operating systems, the automatic NUMA awareness that is provided by setting the
DB2_RESOURCE_POLICY registry variable to AUTOMATIC is
enhanced. This enhancement introduces resource groups, which are sets of resource
bindings that are logically collocated. Resource groups make column-organized processing more
efficient by ensuring that agents that are working on a particular query share the same set of
processor cores and caches. The
AUTOMATIC setting also determines whether to enable memory affinitization, whereby
EDUs attempt to allocate local memory during processing. For more information, see
DB2_RESOURCE_POLICY
in Performance variablesPerformance variables
in the . - DECFLOAT
is now supported as a column type on column-organized tables. For more information, see CREATE
TABLE
CREATE TABLE
topic in the . - SQL
Compatibility features provided by the DB2_COMPATIBILITY_VECTOR registry
variable are now available for column-organized tables. For more information, see the DB2_COMPATIBILITY_VECTOR registry variablethe
DB2_COMPATIBILITY_VECTOR registry variable
topic in the .
- You
can use a new type of column-organized table called shadow table to gain the
performance benefits of BLU Acceleration for the reports and other analytic queries that you perform
on your row-organized tables in OLTP databases. For more information, see Shadow
tables
- High availability disaster recovery (HADR) enhancements:
- Shadow
tables are now supported in HADR environments. For more information, see Shadow tables in HADR
environments
Shadow tables in HADR environments
in . - HADR databases now support
column-organized tables. For more information, see Column-organized tables
Column-organized tables
in . - If you are using Internet
Protocol version 6 (IPV6) adapters, you can now configure HADR with the db2haicu
command. In previous releases, you had to either add an IPV4 interface or manually configure network
monitoring with commands.
For more information, see DB2 high availability instance
configuration utility (db2haicu)
DB2 high availability instance configuration utility (db2haicu)
in . - To enhance your ability to monitor major errors or communication problems with the standby, three new monitoring fields are added to the db2pd command and the MON_GET_HADR table function. For more information, see c0060950.html.
- Shadow
tables are now supported in HADR environments. For more information, see Shadow tables in HADR
environments
-
Feature enhancements:
- The following supported network enhancements are added:
- On supported AIX and Linux operating systems, you can now run the Feature on a Transmission Control Protocol/Internet Protocol over Ethernet (TCP/IP) network without special remote direct memory access (RDMA) capable adapters. For more information, see c0061609.html.
- A
geographically dispersed cluster (GDPC)
environment is extended to support a remote direct memory access (RDMA) over Converged Ethernet
(RoCE) network on:
- AIX operating systems,
- SuSE Linux Enterprise Server (SLES) operating systems.
GDPC infrastructure and GDPC-specific prerequisite conditions
in .
- On
supported Linux operating systems, a environment
can now be run on a set of virtual machines (VMs). The VMs that are supported are VMware ESXi and
KVM as hypervisor, with guest VMs running Linux RHEL 6 or
SLES 11, using sockets (TCP/IP). For more information, see DB2
pureScale Feature in a virtual environment (Linux)
DB2 pureScale Feature in a virtual environment (Linux)
in . - Backup and recovery operations are extended to include incremental backups. For more information, see c0061394.html.
- In a environment, the DB2 Spatial Extender is now supported. For details, see c0061514.html.
- When
applying a fix pack in a environment,
if GPFS, Tivoli® SA
MP, or RSCT were already manually installed or updated manually, you can force the
installFixPack command to overwrite the already installed version.
For more information about the new -f parameter for GPFS,
TSAMP, and RSCT, see installFixPack - Update installed DB2 database products
command the
installFixPack - Update installed DB2 database products command
topic in the . - Inplace
(online) table reorganization is now supported in a . See Inplace
(online) table reorganizationthe
Inplace (online) table reorganization
topic in the . - Federated
two-phase commit is now supported in a . See Enabling two-phase commit for federated transactionsthe
Enabling two-phase commit for federated transactions
topic in the . - A
new db2iupgrade parameter, -g, upgrades all the members and
cluster caching facilities (CFs) at the same time, in parallel. For more information, see db2iupgrade - Upgrade instance commandthe
db2iupgrade - Upgrade instance command
topic in the .
- The following supported network enhancements are added:
- SQL compatibility enhancement and multicultural support enhancement:
- Handling of multibyte characters in character and graphic string data types is improved by allowing data type lengths to be specified as a number of string units. For more information, see c0060911.html.
- For
successfully matching SQL statements, three new inexact statement matching rules are now supported.
For more information, see Inexact matching examples for SQL statements in optimization
profiles
Inexact matching examples for SQL statements in optimization profiles
in the .
- Monitor elements enhancements:
- New time-spent monitor elements provide more granular information about the time that is spent by the database manager on various operations. For more information, see c0061521.html.
- New monitor elements monitor the use of sort heap memory to help you with its sizing and allocation. For more information, see c0061520.html.
- New monitor
elements assist with aggregation of package cache monitor data and detection of plan changes. The
new elements are as follows:
- stmtid - Query statement ID monitor elementstmtid - Query statement ID monitor element
- planid - Query plan ID monitor elementplanid - Query plan ID monitor element
- semantic_env_id - Query semantic compilation environment ID monitor elementsemantic_env_id - Query semantic compilation environment ID monitor element
For details about these elements, refer to the .
- New
monitor elements identify statements in the package cache that had a suboptimal compilation:
- prep_warning - Prepare warning SQLCODE monitor element prep_warning - Prepare warning SQLCODE monitor element
- prep_warning_reason - Prepare warning SQLCODE reason identifier monitor element prep_warning_reason - Prepare warning SQLCODE reason identifier monitor element
For details about these elements, refer to the
. - The
new built-in routine MON_GET_SECTION
MON_GET_SECTION
helps to retrieve and store a copy of the executable section for further investigation. The new built-in routine MON_GET_SECTION_OBJECTMON_GET_SECTION_OBJECT
helps to identify sections that access an object or set of objects, and helps explore which objects a section depends on. For details about these routines, refer to .
- 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 array variables in
INSERT, UPDATE, and DELETE statements are supported by embedded SQL applications. See Compatibility features for migrationthe
Compatibility features for migration
topic in . - You can skip local code page conversion for the graphic data types in
embedded SQL application with the SkipLocalCPConversionForWcharConvert
IBM data server driver configuration keyword
SkipLocalCPConversionForWcharConvert IBM data server driver configuration keyword
topic. - JSON (Java™ Script Object Notation) DB2 NoSQL capabilities are enhanced with new security features, new flexible data types for the _ID field, capped collections, new aggregate functions, and better control through various administration changes. For more information, see the JSON application development for IBM data servers topic.
- Other miscellaneous enhancements:
- On
supported Linux and AIX
operating systems, a non-root installation of DB2 database
server product supports thin server instance environment. For more information, see Thin
server instance topology overview
Thin server instance topology overview
in . - The
db2look command supports two new parameters. To generate the CREATE
DATABASE command that was used to create the source database, you can now use the
-createdb parameter. To generate UPDATE DB CFG commands from the source
database configuration parameters, you can use the new printdbcfg parameter.
For more information, see db2look - DB2 statistics and
DDL extraction tool command
db2look - DB2 statistics and DDL extraction tool command
in the . - The
db2trc command now includes the following enhancements:
- You can now obtain the details of all statement handles that were allocated by the driver prior to
enabling a
trace. To obtain this information, the db2trc trace utility can be enabled with
the -dumpstmt option. See db2trc -
Trace commandthe
db2trc - Trace command
topic in the . - You can now format the trace that is taken
with the -cli option to a directory, where separate trace files are created for
each thread id in a process. See db2trc -
Trace commandthe
db2trc - Trace command
topic in the .
- You can now obtain the details of all statement handles that were allocated by the driver prior to
enabling a
trace. To obtain this information, the db2trc trace utility can be enabled with
the -dumpstmt option. See db2trc -
Trace commandthe
- The db2cli command now includes the following enhancements:
- You can now obtain the connect license
information with the -displaylic option. See db2cli -
interactive
commandthe
db2cli - interactive command
topic in the . - You can now test the connection to or server with
the server-side connect license when
the -useserverlic option is specified. See db2cli -
interactive
commandthe
db2cli - interactive command
topic in the . - You can now test the data source name (DSN) connection with the ODBC driver manager when the
-odbcdsn option is specified. See db2cli -
interactive
commandthe
db2cli - interactive command
topic in the .
- You can now obtain the connect license
information with the -displaylic option. See db2cli -
interactive
commandthe
- The
following EXPLAIN arguments are now supported:
- APREUSE
- BUFFSORT
- BUSTSENS
- BY DPART
- DPFXMLMV
- EXECUTID
- IDXMSTLY
- OPROFERR
- PLANID
- RAND ACC
- SKIPLOCK
- STMTID
- SYSTSENS
- TBISOLVL
EXPLAIN_ARGUMENT table
in the . - 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 c0061452.html.
- You can now ensure that all database backups are always encrypted. New database configuration parameters, encrlib and encropts, allow you to specify an encryption library to use.
- The
performance of SQL Procedural Language (SQL PL) and SQL/PL language execution has been enhanced.
Improvements include the handling of nested routines, global variables, array variables and simple
scalar UDF executions. See PL/SQL language and SQL
Procedural Languagethe
PL/SQL language
andSQL Procedural Language
topics in the . -
The following operating system support is
added:
- Red Hat Enterprise Linux (RHEL) 5.9, 5.10, 6.4, 6.5, and 7 (however, RHEL 7 is not supported in a environment)
- SUSE Linux Enterprise Server (SLES) 11 SP3
- Ubuntu 14.04 LTS 3
- Solaris 11
- Windows 8.1 and Windows 2012 R2
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).
- The move from a DB2 Information Center documentation to the more dynamic, robust, and powerful IBM Knowledge Center is complete. Now, when you access a DB2 Information Center, you are automatically redirected to IBM Knowledge Center. IBM Knowledge Center gathers all IBM product information into one easy-to-access place. IBM Knowledge Center provides an improved search experience that supports saving your searches for future use, and capturing personalized collections of just the information you need.
- On
supported Linux and AIX
operating systems, a non-root installation of DB2 database
server product supports thin server instance environment. For more information, see Thin
server instance topology overview
db2checkCOL - Check database for table accessibility in a prior fix packin the .
Fix Pack 3
Steps 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 .
- In Fix Pack 3, supports Inspur Itanium K1 platform running Inspur K-UX. For the most up-to-date requirements for DB2 database products, see http://www.ibm.com/support/docview.wss?uid=swg27038033.
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.
- The default setting for connections to
is
changed. For details, see InterruptProcessingMode
IBM data server driver configuration keywordthe
InterruptProcessingMode IBM data server driver configuration keyword
topic and DB2Connection.ConnectionString propertytheDB2Connection.ConnectionString property
topic. - The default value of a client
parameter is changed. For details, see rqrioblk - Client I/O block size configuration parameterthe
rqrioblk - Client I/O block size configuration parameter property
topic in .
- 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
- LOB types (BLOB, CLOB, and DBCLOB) are now supported as input to expression-based index keys. For details, see CREATE INDEX statementCREATE INDEX statement.
- You can create a DB2 Text Search index on a nickname. For details, see DB2 Text Search indexes on nicknamesDB2 Text Search indexes on nicknames.
- DB2 for Linux, UNIX and Windows now supports JavaScript Object Notation (JSON) DB2 NoSQL capability. For details, see JSON application development support has been addedJSON application development support has been added.
- There are new parameters for the
db2convert command. For details, see db2convert - Convert row-organized tables into column-organized tablesthe
db2convert - Convert row-organized tables into column-organized tables
topic in the . - The DB2_COLLECT_TS_REC_INFO registry variable is now set to OFF by default for high availability disaster recovery (HADR) databases. For details, see i0052034.html.
- 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
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 .