|
Problem IC63971
|
Status: Closed |
EXTENDED SECURITY USED BY IBM DATA SERVER DRIVER WHERE IT SHOULD NOT |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
You might encounter situations where the IBM Data Server Driver
for ODBC and CLI is using extended security feature although it
should not. This might result in unpredictable application
behaviour.
This issue happens if the following conditions are meet:
- the IBM Data Server Driver for ODBC and CLI package is being
used
- there is no other DB2 product installed or no installed DB2
product is using the extended security feature. (no DB2USERS
and DB2ADMNS Windows user groups have been created on the
system)
- DB2 Connect Server license files are used to enable direct
host connectivity for the IBM Data Server Driver
This APAR enhances the code to distinguish between the client,
that is coming with a full installation, and the client
that was just unzipped and run. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All using IBM Data Server Driver for ODBC and CLI *
****************************************************************
* PROBLEM DESCRIPTION: *
* You might encounter situations where the IBM Data Server *
* Driver for ODBC and CLI is using extended security feature *
* although it should not. This might result in unpredictable *
* application behaviour. *
* *
* This issue happens if the following conditions are meet: *
* - the IBM Data Server Driver for ODBC and CLI package is *
* being used *
* - there is no other DB2 product installed or no installed *
* DB2 product is using the extended security feature. (no *
* DB2USERS and DB2ADMNS Windows user groups have been created *
* on the system) *
* - DB2 Connect Server license files are used to enable direct *
* host connectivity for the IBM Data Server Driver *
* *
* This APAR enhances the code to distinguish between the *
* client, that is coming with a full installation, and the *
* client that was just unzipped and run. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 V9.7 FixPack1 *
**************************************************************** |
| Local Fix: |
There a three possible workarounds:
- use DB2 Connect Personal Edition License file instead of
DB2 Conect Server License files
- set DB2_EXTSECURITY=NO in Windows environment
- create the Windows User groups 'DB2USERS' and 'DB2ADMNS' |
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in Version 9.7 Fix Pack 1 |
| Workaround |
See LOCAL FIX |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.10.2009
16.12.2009
16.12.2009 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.,
9.7.FP1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
