DB2 - Problem description
Problem IC61819 | Status: Closed |
THE DB2AUTOSTART VARIABLE DOESN'T GET SET AUTOMATICALLY USING THE RESPONSE FILE TO INSTALL DB2. | |
product: | |
DB2 CONNECT / DB2CONNCT / 970 - DB2 | |
Problem description: | |
During a silent install using a response file, the value for the keyword DB2AUTOSTART is not set. Thus, when the system is rebooted, DB2 instances aren't started automatically. You can verify the problem by running <DB2 Install Path>/adm/db2set and it should not show the variable, DB2AUTOSTART, as being set to YES. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * During a silent install using a response file, the value for * * the keyword DB2AUTOSTART is not set. Thus, when the system * * is rebooted, DB2 instances aren't started automatically. * * * * You can verify the problem by running <DB2 Install * * Path>/adm/db2set and it should not show the variable, * * DB2AUTOSTART, as being set to YES. * **************************************************************** * RECOMMENDATION: * * Upgrade to Version 9.7 Fix Pack 2 or use the following * * workaround: * * * * 1) Run <DB2 Install Path>/instance/db2iauto -on <Instance * * Name> * * 2 ) Verify the DB2AUTOSTART is set via the command, <DB2 * * Install Path>/adm/db2set * **************************************************************** | |
Local Fix: | |
Run <DB2 Install Path>/instance/db2iauto -on <Instance Name> Verify the DB2AUTOSTART is set via the command, <DB2 Install Path>/adm/db2set | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows | |
Solution | |
Problem will be fixed in Version 9.7 Fix Pack 2 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 03.07.2009 12.03.2010 12.03.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP2 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.1 |