|
Problem IC96155
|
Status: Closed |
When doing switch user in a trusted connection, the client omits to send User Registry Name (USRREGNM) to the database server |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
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). |
| Problem Summary: |
****************************************************************
* 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: *
* . *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in Version 10.5 Fix Pack 4
At a minimum, this fix should be applied on the client and any
DB2 Connect gateway. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 23.09.2013
15.09.2014
15.09.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.4
|
 |
