suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT22624 Status: Closed

DB2VAL FAILS TO VALIDATE SYSADMIN AUTHORITY IF SYSADM_GROUP IS LESS THAN 8
CHAR LONG

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
When the value of sysadm_group is less than 8 chars long, the 
remaining bytes get padded with spaces. E.i. "DB2ADM  ". 
 
The spaces cause the check of whether user is in the group to 
fail due to group not found. 
 
Trimming trailing spaces should fix this problem. 
 
Update: 
The lookup logic for db2val should be changed to the same one 
used by the Engine
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Db2 11.1 Mod 3 Fix Pack 3 or higher               * 
****************************************************************
Local Fix:
To avoid this problem before fix is released, use 8 characters 
long group names (i.e. DB2ADMNS)
available fix packs:
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows

Solution
First fixed in Db2 11.1 Mod 3 Fix Pack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
02.10.2017
19.03.2018
19.03.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)