home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC65753 Status: Geschlossen

THE REORGCHK COMMAND MIGHT STOP RESPONDING (HANG), IF THE COMMAND
RECEIVES SQL ERROR.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - 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 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                                            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade to DB2 V9.7 fixpack 2 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.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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a 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

Lösung
Problem was first fixed in Version 9.7 Fix Pack 2.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC71217 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
21.01.2010
06.07.2010
06.07.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP2
Problem behoben lt. FixList in der Version
9.7.0.2 FixList