|
Problem IC65204
|
Status: Geschlossen |
THE REORGCHK COMMAND MIGHT STOP RESPONDING (HANG), IF THE COMMAND RECEIVES SQL ERROR. |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problembeschreibung: |
The reorgchk command might stop respond (hang) if the command
receives SQL error.
While executing reorgchk, if the table display or index display
function of reorgchk will return any error, the reorgchk and
back-end process of CLP will finish execution but, control of
the execution may not be transferred to the front-end process
and CLP could hang.
The following db2diag.log entry illustrates one of the cause,
reorgchk receives SQL0911N during retrieving pagesize of given
table or index object.
2009-12-12-19.11.39.996120+540 I23144472A1258 LEVEL: Severe
PID : 2392224 TID : 1 PROC : db2bp
INSTANCE: udbebb01 NODE : 000
APPID : *N0.udbebb01.091212095629
EDUID : 1
FUNCTION: DB2 UDB, command line process,
clp_reorgchk_get_tpagesize, probe:2622
<snip>
DATA #7 : unsigned integer, 4 bytes
4294966385 = -911 |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* Users who use reorgchk command. *
****************************************************************
* PROBLEM DESCRIPTION: *
* The reorgchk command might stop responding (hang) if *
* thecommand receives SQL error.While executing reorgchk, if *
* the table display or indexdisplay function of reorgchk will *
* return any error, thereorgchk and back-end process of CLP *
* will finish executionbut, control of the execution may not *
* be transferred to thefront-end process and CLP could *
* hang.The following db2diag.log entry illustrates one of *
* thecause, reorgchk receives SQL0911N during retrieving *
* pagesizeof given table or index *
* object.2009-12-12-19.11.39.996120+540 I23144472A1258 LEVEL: *
* SeverePID : 2392224 TID : 1 PROC : *
* db2bpINSTANCE: udbebb01 NODE : 000APPID : *
* *N0.udbebb01.091212095629EDUID : 1FUNCTION: DB2 UDB, *
* command line process,clp_reorgchk_get_tpagesize, *
* probe:2622<snip>DATA #7 : unsigned integer, 4 *
* bytes4294966385 = -911 *
****************************************************************
* RECOMMENDATION: *
* Please upgrade to version 9.5 fixpack 6 or later. *
**************************************************************** |
| Local-Fix: |
No local fix. This problem will be fixed in db2_v95fp6,
db2_v97fp2, db2_v98fp1 or heigher releases. |
| verfügbare FixPacks: |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Lösung |
Problem was first fixed in Version 9.5 Fix Pack 6. |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Bug-Verfolgung |
Vorgänger : APAR is sysrouted TO one or more of the following: IC65753
Nachfolger : |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 18.12.2009
09.09.2010
09.09.2010 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.5.FP6
|
| Problem behoben lt. FixList in der Version |
