|
Problem IT10107
|
Status: Closed |
RUNNING 'DB2FODC -HANG' ON WINDOWS PLATFORMS GIVES ERROR 'GOTO WAS UNEXPECTED AT THIS TIME.' |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* 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. |
| Solution |
First fixed in DB2 LUW 10.5 Fix Pack 7 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 16.07.2015
19.01.2016
19.01.2016 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.7
|
 |
