|
Problem IC67646
|
Status: Closed |
DAS INSTANCE IS NOT AUTO STARTING AFTER REBOOT DESPITE CORRECT DASAUTO SETTINGS ARE IN PLACE. |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
This defect is due to a change introduced by APAR IZ45208 and it
applied to DAS instances only. DB2 instances are not affected
and can be successfully autostarted after reboot.
If db2fmcs is at level containing IZ45208 then the above symptom
may occur. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DAS user who have configured to use fault monitor to *
* autostart DAS instance after reboot. *
****************************************************************
* PROBLEM DESCRIPTION: *
* DAS instance is not auto starting after reboot despite *
* correct dasauto setting. *
* Problem affects DAS instance only, DB2 instances are not *
* affected and can be autostarted after reboot. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 9.5.0.6. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Upgrade to DB2 9.5.0.6. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 05.04.2010
31.05.2010
31.05.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.0.6
|
| Problem solved according to the fixlist(s) of the following version(s) |
