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 IT19362 Status: Closed

ENV_GET_REG_VARIABLES RETURNS INCORRECT DEFAULT VALUES FOR DB2CHGPWD_EEE
AND DB2LOGINRESTRICTIONS.

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
The values set to REG_VAR_DEFAULT_VALUE returned by 
ENV_GET_REG_VARIABLES table function for DB2CHGPWD_EEE 
and DB2LOGINRESTRICTIONS registry variables are incorrect. 
 
1. 
The default value for DB2CHGPWD_EEE should be NULL. 
However, the value returned by ENV_GET_REG_VARIABLES is 'DB2'. 
 
Example: 
$ db2 "select substr(REG_VAR_NAME, 1, 40) as REG_VAR_NAME, 
substr(REG_VAR_DEFAULT_VALUE, 1, 20) as REG_VAR_DEFAULT_VALUE 
from table (ENV_GET_REG_VARIABLES (-2,1)) where REG_VAR_NAME = 
'DB2CHGPWD_EEE'" 
 
REG_VAR_NAME                             REG_VAR_DEFAULT_VALUE 
---------------------------------------- --------------------- 
DB2CHGPWD_EEE                            DB2 
 
  1 record(s) selected. 
 
2. 
The default value for DB2LOGINRESTRICTIONS should be 'LOCAL'. 
However, the value returned by ENV_GET_REG_VARIABLES is NULL. 
 
Example: 
$ db2 "select substr(REG_VAR_NAME, 1, 40) as REG_VAR_NAME, 
substr(REG_VAR_DEFAULT_VALUE, 1, 20) as REG_VAR_DEFAULT_VALUE 
from table (ENV_GET_REG_VARIABLES (-2,1)) where REG_VAR_NAME = 
'DB2LOGINRESTRICTIONS'" 
 
REG_VAR_NAME                             REG_VAR_DEFAULT_VALUE 
---------------------------------------- --------------------- 
DB2LOGINRESTRICTIONS                     - 
 
  1 record(s) selected.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 11.1 Mod 2 Fix Pack 2 or higher               * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
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 2 Fix Pack 2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
21.02.2017
23.06.2017
23.06.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)