DB2 - Problembeschreibung
| Problem IT10107 | Status: Geschlossen |
RUNNING 'DB2FODC -HANG' ON WINDOWS PLATFORMS GIVES ERROR 'GOTO WAS UNEXPECTED AT THIS TIME.' | |
| Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
| Problembeschreibung: | |
If you run 'db2fodc -hang' on Windows platforms this will report
the error:
goto was unexpected at this time.
This occurs after the stage 'Collecting "Call stacks 2" info'.
The expected behavior would be to be prompted with the
following:
Hang investigation may require some additional data collection
that may
result in severe performance degradation and can take
substantial amount
of time or hang. This collection is still recommended to get
the full
set of diagnostic data.
When the error occurs the data collected will be the same as the
'basic' data collection and you will not be advised on the
location of the FODC Hang data. | |
| Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All DB2 LUW Users on Windows platforms * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 LUW 10.5 Fix Pack 7 or later * **************************************************************** | |
| Local-Fix: | |
Running 'db2fodc -hang' with either the 'basic' or 'full' option prevents the error from occurring. | |
| Lösung | |
First fixed in DB2 LUW 10.5 Fix Pack 7 | |
| Workaround | |
keiner bekannt / siehe Local-Fix | |
| Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 16.07.2015 19.01.2016 19.01.2016 |
| Problem behoben ab folgender Versionen (IBM BugInfos) | |
| Problem behoben lt. FixList in der Version | |
| 10.5.0.7 |
|