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

DB2 may abend when using the ADMIN_MOVE_TABLE procedure with the TRACE
option when DB2 is running on a Sun Solaris system

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
For example, calling the admin_move_table procedure as follows : 
 
 
db2 "call admin_move_table ('NEWTON','TEST','','','MOVE,TRACE')" 
 
SQL1224N  The database manager is not able to accept new 
requests, has terminated all requests in progress, or has 
terminated the 
specified request because of an error or a forced interrupt. 
SQLSTATE=55032 
 
Error SQL1224N is an indication that the DB2 server side has 
encountered a serious error 
and has most likely shut down itself. 
 
The ( partial ) TRACE file, produced by the TRACE directive will 
show : 
 
 
(19190)ENTRY: adminotm_online_table_move     |DBGUEST4 | TEST | 
MOVE,TRACE 
. (1072)ENTRY: adminotm_Otm_constructor         | 
ffffffff49e9c9a0 
. . (2027)ENTRY: adminotm_StoredProcedure_connect| 
ffffffff49e9c9a0 
. . (2060)EXIT: adminotm_StoredProcedure_connect | 0 
. . (1998)ENTRY: adminotm_StoredProcedure_initVersion | 
ffffffff49e9c9a0 
. . (2016)EXIT: adminotm_StoredProcedure_initVersion | 0 | 
09.07.0005 
. . (1108)DATA: adminotm_Otm_constructor  indexNameSz | 128 
. . (1111)DATA: adminotm_Otm_constructor       | 
              triggerNameSz | 128 
. (1114)EXIT: adminotm_Otm_constructor           | 0 
 
and then nothing more. 
 
When reviewing the db2diag.log, you will see a trap file was 
created 
in a DB2FODC subdirectory. 
 
This trap file will have the following stacktrace : 
 
strlen 
_doprnt 
vsnprint 
ossSnprintf 
pdTraceSP 
admin_move_table
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 on Solaris                                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade the DB2 server to V9.7 Fix Pack 6                    * 
****************************************************************
Local-Fix:
do not use the TRACE option with the ADMIN_MOVE_TABLE procedure 
on the Sun Solaris operating system.
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
This problem was first fixed in V9.7 Fix Pack 6
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
09.02.2012
04.07.2012
04.07.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP6
Problem behoben lt. FixList in der Version
9.7.0.6 FixList