DB2 FOR LUW / DB2FORLUW / A10 - DB2

When an application switches the user ID for an explicit trusted 
connection then any User Registry Name that is associated with 
the connection is incorrectly omitted from data the client sends 
to the database server. 
 
Applications that use the CLI (Call Level Interface) API can 
associate a User Registry Name to the connection 
by assigning a value to the the CLI environment handle or 
connection handle attribute SQL_ATTR_USER_REGISTRY_NAME before 
it connects to a database. 
 
If the User Registry Name is set then it ought to be included as 
the USRREGNM (User Registry Name) attribute of DDM 
(Distributed Data Management) commands that are sent to the 
database server. 
 
When the User Registry Name is missing from the data sent by the 
client that can cause errors such as "DISTRIBUTED IDENTITY IS 
NOT DEFINED" and "378-014 ABEND DURING RACINIT PROCESSING" on a 
DB2 on z/OS database server. 
 
This defect affects DB2 for Linux, UNIX and Windows both as a 
database client and as a database gateway (DB2 Connect).

**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of DB2 for Linux, UNIX and Windows applications that   * 
* use the CLI (Call Level Interface) API to connect to a       * 
* database using an explicit trusted connection                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* .                                                            * 
****************************************************************

DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

Problem was first fixed in Version 10.1 Fix Pack 4 
At a minimum, this fix should be applied on the client and any 
DB2 Connect gateway.

keiner bekannt / siehe Local-Fix

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

23.09.2013
03.06.2014
03.06.2014