DB2 - Problem description
Problem IC80093 | Status: Closed |
INCORRECT VALUES SET FOR CPU_SPEED & COMM_BANDWIDTH DURING DB2IUPDT FAILURE. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
Problem: Execution of installFixPack or db2iupdt commands may return the following warning: DBI1282W The database manager configuration files could not be merged. The original configuration file was saved as /opt/IBMdb2/home/c1adw1/sqllib/backup/db2systm.old. (The original instance type is ese. The instance type to be upgraded or updated is ese.) When DB2 fails to merge the database manager configuration files, CPUSPEED and COMM_BANDWIDTH might be set to values not reflective of the system's characteristics. These values might lead the query optimizer to determine suboptimal plans. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * move to next fp * **************************************************************** | |
Local Fix: | |
If this is an existing installation, use the UPDATE DBM CFG command to set CPUSPEED and COMM_BANDWIDTH to the values before the installation activity. Otherwise set the DBM CFG parameters as the instance user: 1) db2 update dbm cfg using CPU_SPEED -1 2) db2 update dbm cfg using COMM_BANDWIDTH -1 which directs DB2 to determine values appropriate to your system. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows | |
Solution | |
Fixed in v97fp6 | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC84235 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 30.11.2011 26.02.2013 26.02.2013 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP6 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.6 |