DB2 - Problem description
Problem IC90789 | Status: Closed |
RESTORE DB2_VENDOR_INI REGISTRY VARIABLE | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
In v9.5 the registry variable DB2_VENDOR_INI was deprecated. In it's deprecated state, the registry variable still worked and was supported, but it was encouraged that customers use DB2_DJ_INI instead. (See the Information center topics about deprecations and discontinuations). At the release of v10.1, DB2_VENDOR_INI was discontinued and removed from the product, no longer supported. However, since the DB2_DJ_INI only works in a federated environment, customers that previously used DB2_VENDOR_INI in a non-federated environment were left without a solution in v10.1. As such, DB2_VENDOR_INI has been re-enabled here in FP3. It will, however, remain in a deprecated state, such that we continue to encourage the use of DB2_DJ_INI wherever possible instead. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All users wishing to set environment variables in a * * non-federated db2 instance * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Version 10.1 Fix Pack 3 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in Version 10.1 Fix Pack 3 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 12.03.2013 27.09.2013 27.09.2013 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.3 | |
10.1.0.3 |