|
Problem IC75263
|
Status: Closed |
DB2TRC ON -GLOBAL -HOST COMMAND MIGHT FAIL ON LARGE DPF SYSTEMS WITH LONG HOST NAMES |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
On large DPF systems, it is possible that the command "db2trc on
-global -host" will sometimes result in a trap, causing db2trc
to
terminate abnormally. This problem is more likely to happen when
db2nodes.cfg contains long hostnames ( 8 or more characters in
length ). |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* The problem occurs in DPF environments. All platforms are *
* affected. *
****************************************************************
* PROBLEM DESCRIPTION: *
* When using "db2trc on -global -host" on an DPF system, there *
* is a chance that the code will trap and the program will *
* exit abnormally. *
****************************************************************
* RECOMMENDATION: *
* To avoid the original problem, the customer should upgrade *
* their db2 product to version v97 fixpack 4. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
The problem has been fixed in v97fp4.
The command now successfully executes when the argument given to
-host is a valid hostname and it correctly returns an error and
gracefully exits when the argument to -host is not a valid
hostname. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 24.03.2011
29.04.2011
29.04.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP4
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.4
|
 |
