|
Problem IC65113
|
Status: Closed |
THE PROGRAM DB2TRC TRAPS WHEN FORMATTING THE COMMUNICATIONS BUFFER OF A TRACE DUMP FILE |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Command Issued:
db2trc format -c <tracefile> <outputfile>
Result:
ATTENTION: db2trc terminated abnormally because it detected a
trap inside the "SQJC" component custom formatter. This
occurred while
formatting trace record #1212425.
Please notify the component owner of this problem.
You can workaround this problem by using the "-ncf" option when
formatting your dump file. This option disables the component
custom
formatting.
Result:
User is unable to format the trace dumps communication buffer.
There is no workaround. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 v9.7 FP1 installed on any supported hardware *
****************************************************************
* PROBLEM DESCRIPTION: *
* A variable is incorrectly typed as an unsigned int andtested *
* for being greater than 0. When a customer attemptsto format *
* the communications buffer of a trace dump wherethe *
* communications buffer includes a segment larger than32KB *
* this variable will underflow. Since it is unsigneddb2trc *
* will attempt to continue formatting into anon-existant *
* buffer resulting in a trap. The followingmessage is *
* displayed:ATTENTION: db2trc terminated abnormally because it *
* detectedatrap inside the "SQJC" component custom formatter. *
* Thisoccurred whileformatting trace record #1212425.Please *
* notify the component owner of this problem.You can *
* workaround this problem by using the "-ncf" *
* optionwhenformatting your dump file. This option disables *
* thecomponentcustomformatting. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to v9.7 FP2. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows
|
| Solution |
DB2 v9.7 FP2 includes a fix for this problem. The customer will
be able to format their trace file without db2trc trapping. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 11.12.2009
05.07.2010
05.07.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
