Informix - Problembeschreibung
Problem IT10780 | Status: Geschlossen |
WINDOWS: THREAD SUSPENSION CAN ABORT THE INSTANCE WITHOUT A SHARED MEMORY DUMP BEING WRITTEN | |
Produkt: | |
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10 | |
Problembeschreibung: | |
In recent versions a thread suspension feature is included and active by default. In the case of an assertion that would otherwise have led to a crash with thread suspension the instance will try to check if the affected thread is holding critical resources. If this is not the case the thread will be suspended only, avoiding the crash and leaving the opportunity to defer the instance restart to a more convenient time in the future. In this case currently (another defect is open to address this aspect of the default behavior) no shared memory dump will be written regardless of the DUMPSHMEM setting. For versions running on the Windows platform it has been observed that this thread suspension can lead to an unintended crash of the instance. To achieve a shared memory dump for better diagnostic abilities in this situation the thread suspension feature needs to be deactivated. This can be achieved by setting AFCRASH 0x481 in the ONCONFIG file of the instance. After a restart you can verify the setting of AFCRASH with "onstat -g ras". | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All users on Windows platforms. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Update to IBM Informix Server 12.10.xC6 * **************************************************************** | |
Local-Fix: | |
Lösung | |
Problem Fixed In IBM Informix Server 12.10.xC6 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 19.08.2015 19.01.2016 19.01.2016 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
12.10.xC6 | |
Problem behoben lt. FixList in der Version | |
12.10.xC6 |