|
Problem IC84254
|
Status: Closed |
DB2ADUTL TRUNCATES THE USERNAME AND NODENAME TO 7 CHARACTERS |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
When calling the db2adutl utility with the 'GRANT' or 'REVOKE'
options on DB2 v97fp5. The db2adutl utility will truncate the
instance owner and node name to 7 characters. The truncation
occurs when parsing the user and nodename parameters from the
command line.
The excerpt below demonstrates the symptoms of this problem:
$ db2adutl grant user XXXXXXXX on nodename NNNNNNNN for db
<database_name>
Successfully added permissions for db2inst to access
<database_name> on node NNNNNNN.
$ db2adutl queryaccess
Node Username Database Name Type
--------------------------------------------------------------
NNNNNNN XXXXXXX <database_name>
A
--------------------------------------------------------------
Access Types: B - backup images L - logs A - both |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users running DB2 v10 GA *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 v10.1 FP1 or higher *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
The problem was fixed in DB2 v10 FP1 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 13.06.2012
13.11.2012
13.11.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
