DB2 - Problem description
Problem IC69500 | Status: Closed |
DB2PROCESSORS INSTANCE PROFILE VARIABLE IS NOT NEEDED ANYMORE | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
When you create a new instance the DB2PROCESSORS profile variable is automatically created and set to maximum 2 processor. You can display the instance profile with the "db2set -all" command: db2set -all [i] DB2PROCESSORS=0,1 This variable is no longer needed and after applying this fix the variable will not be defined anymore when the instance is created. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Express-C users. * **************************************************************** * PROBLEM DESCRIPTION: * * When you create a new instance the DB2PROCESSORS profile * * * * variable is automatically created and set to maximum 2 * * * * processor. * * * * You can display the instance profile with the "db2set -all" * * * * command: * * * * * * * * db2set -all * * * * [i] DB2PROCESSORS=0,1 * * * * * * * * This variable is no longer needed and after applying this * * fix * * the variable will not be defined anymore when the instance * * is * * created. * **************************************************************** * RECOMMENDATION: * * Upgrade to Express-C version 9.7 Fix Pack 3. * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
First fixed in Express-C version 9.7 Fix Pack 3. | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC69502 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 28.06.2010 16.09.2010 16.09.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP3 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.3 | |
9.7.0.3 |