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 IC80237 Status: Geschlossen

UNDER RARE CONDITIONS, THE RUNSTATS UTILITY MIGHT TRAP OR RETURN SQLCODE
-901 WITH SQLR_UPDATE_CATALOGS IN THE CALLSTACK

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
The RUNSTATS utility might trap or return sqlcode -901 with 
sqlr_update_catalogs in the callstack.  The problem occurs 
rarely.  For the problem to occur, the memory allocations done 
by utility must have specific addresses of significance only to 
the particular execution.  When the problem occurs, the 
following might be seen: 
 
- sqlcode -901 
 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -901   sqlerrml: 20 
 sqlerrmc: Scan interface error 
 sqlerrp : SQLRL041 
 sqlerrd : (1) 0x00000385      (2) 0x801A006D      (3) 
0x00000000 
           (4) 0x00000000      (5) 0xFFFFFFF6      (6) 
0x00000000 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate: 58004 
 
  [0] pdLog 
  [1] pdLog 
  [2] checkForError 
  [3] checkForError 
  [4] buildIndexes 
  [5] open 
  [6] update 
  [7] updateOneRow 
  [8] sqlr_update_catalogs 
  [9] sqlrLocalRunstats 
 
- signal#11 trap 
 
 0         ossDumpStackTraceEx 
 1        OSSTrapFile::dumpEx 
 2        sqlo_trce 
 3        sqloEDUCodeTrapHandler 
 4        __pthread_mutex_cond_lock 
 5        sqlr_update_catalogs 
 6        sqlrLocalRunstats 
 
It is likely that a subsequent RUNSTATS will be successful. 
 
This problem was introduced in DB2 Version 9.7 Fixpack 1.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The RUNSTATS utility might trap or return sqlcode -901 with  * 
* sqlr_update_catalogs in the callstack.  The problem occurs   * 
* rarely.  For the problem to occur, the memory allocations    * 
* done                                                         * 
* by utility must have specific addresses of significance only * 
* to                                                           * 
* the particular execution.  When the problem occurs, the      * 
* following might be seen:                                     * 
*                                                              * 
* - sqlcode -901                                               * 
*                                                              * 
* sqlcaid : SQLCA    sqlcabc: 136  sqlcode: -901  sqlerrml: 20 * 
* sqlerrmc: Scan interface error                               * 
* sqlerrp : SQLRL041                                           * 
* sqlerrd : (1) 0x00000385      (2) 0x801A006D      (3)        * 
* 0x00000000                                                   * 
*           (4) 0x00000000      (5) 0xFFFFFFF6      (6)        * 
* 0x00000000                                                   * 
* sqlwarn : (1)      (2)      (3)      (4)        (5)      (6) * 
*           (7)      (8)      (9)      (10)        (11)        * 
* sqlstate: 58004                                              * 
*                                                              * 
*   [0] pdLog                                                  * 
*   [1] pdLog                                                  * 
*   [2] checkForError                                          * 
*   [3] checkForError                                          * 
*   [4] buildIndexes                                           * 
*   [5] open                                                   * 
*   [6] update                                                 * 
*   [7] updateOneRow                                           * 
*   [8] sqlr_update_catalogs                                   * 
*   [9] sqlrLocalRunstats                                      * 
*                                                              * 
* - signal#11 trap                                             * 
*                                                              * 
* 0        ossDumpStackTraceEx                                 * 
* 1        OSSTrapFile::dumpEx                                 * 
* 2        sqlo_trce                                           * 
* 3        sqloEDUCodeTrapHandler                              * 
* 4        __pthread_mutex_cond_lock                           * 
* 5        sqlr_update_catalogs                                * 
* 6        sqlrLocalRunstats                                   * 
*                                                              * 
* It is likely that a subsequent RUNSTATS will be successful.  * 
*                                                              * 
* This problem was introduced in DB2 Version 9.7 Fixpack 1.    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fixpack 6.                        * 
****************************************************************
Local-Fix:
There is no workaround to avoid experiencing the rare problem. 
A subsequent RUNSTATS is likely to be successful.
verfügbare FixPacks:
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

Lösung
Problem first fixed in DB2 Version 9.7 Fixpack 6.
Workaround
See Local Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
06.12.2011
05.06.2012
05.06.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP6
Problem behoben lt. FixList in der Version
9.7.0.6 FixList