DB2 FOR LUW / DB2FORLUW / A50 - DB2

Only application to purescale server using release v10.5.4. 
APAR should be applied on server. 
 
If enableWLB=true or client affinity is enabled, application 
using non-java driver/client, may report SQL0501N, gets wrong 
value of global variables,incorrectly move to a new member or 
failback, incorrectly tries to drive seamlessACR, if server is 
setup as purescale server and if application is running under 
any of the following restrictions: 
 
http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com. 
ibm.db2.luw.qb.server.doc/doc/r0056430.html?lang=en. 
Restrictions for workload balancing and automatic client reroute 
 
During COMMIT and ROLLBACK operations, DB2 pureScale database 
servers prevent applications from using workload balancing if 
any of the following conditions apply: 
 
    The connection uses global variables. 
    An encrypted password is used. 
    Open WITH HOLD cursors are used. 
    Declared temporary tables (DGTT) are used. 
    A transform group was set. 
    The session authorization ID was changed. 
    PL/SQL packages or SQL/PL modules are used. 
    Cursor variables are used. 
    Sequence values are used and DB2_ALLOW_WLB_WITH_SEQUENCES 
communication variable is not enabled. 
    Created temporary tables (CGTTs) that were created with the 
PRESERVE ROWS option are used. 
 
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.

**************************************************************** 
* USERS AFFECTED:                                              * 
* PureScale users                                              * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v10.5.5.                                          * 
****************************************************************

Fixed in v10.5.5

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

14.10.2014
15.12.2014
15.12.2014