|
Problem IC81312
|
Status: Closed |
DB2 may abend when using the ADMIN_MOVE_TABLE procedure with the TRACE option when DB2 is running on a Sun Solaris system |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* 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. |
| available fix packs: |
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
|
| Solution |
This problem was first fixed in V9.7 Fix Pack 6 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 09.02.2012
04.07.2012
04.07.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.6
|
 |
