|
Problem IC63992
|
Status: Closed |
Downlevel DB2 instance wont autostart after install higher level |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
If you have 2 versions of DB2 on the same machine configured
correctly for autostart (DB2AUTOSTART set to yes), only the
latest version will autostart due to library incompatibility
with the old version. Even if the instance is migrated from a
lower level, the newly migrated instance will autostart, but the
older ones will not. The fix for APAR IZ45208 will resolve this.
There should only be 1 entry (latest DB2 version) in
/etc/inittab. The db2fmcu is then expected to start all the
other instances (same version AND older versions of DB2) on the
same machine. However due to this APAR, the older versions of
DB2 will not autostart.
The solution is to upgrade the most current DB2 version
(whichever one has is in the /etc/inittab) to the fixpack that
contains the fix to resolve it. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users with DB2 instances on different DB2 release level *
* and are using autostart *
****************************************************************
* PROBLEM DESCRIPTION: *
* If you have 2 versions of DB2 on the same machine configured *
* *
* correctly for autostart (DB2AUTOSTART set to yes), only the *
* *
* latest version will autostart due to library incompatibility *
* *
* with the old version. Even if the instance is migrated from *
* a *
* lower level, the newly migrated instance will autostart, but *
* the *
* older ones will not. The fix for APAR IZ45208 will resolve *
* this. *
* *
* *
* There should only be 1 entry (latest DB2 version) in *
* *
* /etc/inittab. The db2fmcu is then expected to start all the *
* *
* other instances (same version AND older versions of DB2) on *
* the *
* same machine. However due to this APAR, the older versions *
* of *
* DB2 will not autostart. *
****************************************************************
* RECOMMENDATION: *
* Upgrade the most current DB2 version (whichever one that has *
* an entry in /etc/inittab) to the fixpack level that contains *
* the fix. e.g. DB2 version 9.7.0.1. *
**************************************************************** |
| Local Fix: |
|
| 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 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 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 |
Upgrade the most current DB2 version (whichever one that has an
entry in /etc/inittab) to the fixpack level that contains the
fix. e.g. DB2 version 9.7.0.1. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.10.2009
17.02.2010
17.02.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.0.1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
