For your application to make full use of the DB2® pureScale® Feature, your clients and servers must be at certain release levels.
Server version | Client version | Features available |
---|---|---|
DB2 Version 9.8, or later | Version 9.7, Fix Pack 1, or later | Transaction-level and connection-level workload
balancing Automatic client reroute that is based on workload Client affinities |
DB2 Version 9.8, or later | Version 9.1, |
Connection-level workload balancing (transaction-level
workload balancing is unavailable) Automatic client reroute that is based on workload |
DB2 Version 10.1 | Version 9.5, and |
Connection-level workload
balancing (transaction-level workload balancing is unavailable) Automatic client reroute based on workload |
DB2 Version 10.1 | Version 9.7, Fix Pack 1, or later | Transaction-level and connection-level
workload balancing Automatic client reroute that is based on workload Client affinities |
DB2 Version 10.5 | Version 9.7, Fix Pack 1, or later | Transaction-level and connection-level workload
balancing Automatic client reroute that is based on workload Client affinities |
For further information about using these client features, search the DB2 Information Center for information about client high availability connections to DB2 database servers.
For applications that use CLI, ODBC, .NET, or JDBC APIs, if workload balancing is not allowed as a result of any of the preceding conditions, then automatic client reroute is non-seamless and affinity failback is disabled.
For applications that do not use CLI, ODBC, .NET, or JDBC APIs, such as applications that use embedded SQL, in addition to the conditions listed, the use of dynamic SQL must also be considered when it comes to workload balancing. By default, workload balancing is disabled for such applications after a statement is prepared unless the statement is prepared in a stored procedure or user-defined function. However, if the statement is always reprepared in a new transaction before it is executed, you can allow workload balancing by specifying either the KEEPDYNAMIC NO option for the bind operation or the KEEP DYNAMIC NO option for the ALTER PACKAGE statement. For applications that do not use CLI, ODBC, .NET, or JDBC APIs, automatic client reroute is always non-seamless and affinity failback is disabled under the conditions that restrict workload balancing.
For applications that use CLI, ODBC, .NET, or JDBC APIs, the use of dynamic SQL has no bearing on whether workload balancing is allowed or whether automatic client reroute is seamless or non-seamless.
In loosely coupled XA transactions, if there are multiple branches open against the same resource manager an application can encounter lock-time or a deadlock within global transactions. The lock-time or deadlock occurs because data sharing members can share locks only if multiple branches within a global transaction land on the same member. An application might not be able to use workload balancing but it can use client affinity for high availability.