DB2 - Problembeschreibung
Problem IT25750 | Status: Geschlossen |
SIGKILL ORIGINATING FROM DB2STOP FORCE NODENUM XX | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problembeschreibung: | |
db2sysc sends SIGKILL to itself which generates FODC_Panic diagnostics when stopping nodes concurrently. This affects multiple partition systems. Reproduce by running the script below. This example uses 4 partition system. #!/bin/sh db2 "activate db t" sleep 1 db2stop force nodenum 1 & db2stop force nodenum 3 & db2stop force nodenum 2 & db2stop force nodenum 0 & sleep 1 db2stop force nodenum 0 & db2stop force nodenum 3 & db2stop force nodenum 1 & db2stop force nodenum 2 & sleep 1 db2stop force nodenum 3 & db2stop force nodenum 0 & db2stop force nodenum 3 & db2stop force nodenum 1 & sleep 1 db2stop force nodenum 1 & db2stop force nodenum 3 & db2stop force nodenum 0 & db2stop force nodenum 2 & NOTES: a) By default this fix is disabled. To enable this fix, set DB2 registry variable DB2_PMODEL_SETTINGS=PARALLEL_SINGLE_STOP:TRUE then restart DB2 instance for new change to take effect b) Can only be enabled on DPF instance which has more than one member | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.1 Mod 4 Fixpack 4 or higher * **************************************************************** | |
Local-Fix: | |
Two alternatives: a) "db2stop force" parallel db2stop on all nodes, but it lets DB2 decide order to stop each node OR b) Execute "db2stop force on nodenum xx" sequentially instead of concurrently as per the reproduction script. | |
Lösung | |
Workaround | |
See LOCAL FIX. | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 18.07.2018 27.11.2018 03.12.2018 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version |