|
Problem IT00796
|
Status: Closed |
AN SQL STATEMENT THAT REFERENCES A CREATE GLOBAL TEMPORARY TABLE ON WHICH NO RUNSTATS WAS PERFORMED MAY RESULT IN SQL901N |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
If a table was created as CREATE GLOBAL TEMPORARY TABLE and
RUNSTATS was never performed on this table, an SQL statement
that references it may result in SQL901N error under certain
circumstances.
In the case of SQL901N, the following error and reason will be
returned:
SQL0901N The SQL statement or command failed because of a
database system error. (Reason "non-severe dms programming
error".) SQLSTATE=58004
db2diag.log will contain the corresponding entry with the
stack:
2013-11-07-21.30.55.285707-300 I22879645A5449 LEVEL:
Severe
PID : 31653994 TID : 22876 PROC :
db2sysc 11
INSTANCE: db2inst1 NODE : 011 DB :
TESTDB
APPHDL : 11-104 APPID: *N0.db2inst1.1311080220182
AUTHID : DBUSER1 HOSTNAME: p570-21
EDUID : 22876 EDUNAME: db2agent (TESTDB) 11
FUNCTION: DB2 UDB, data management, sqldFixExistingTCB,
probe:12281
MESSAGE : ZRC=0x82040001=-2113667071=SQLD_NONSEVERE_PRGERR
"non-severe dms programming error"
DIA8532C An internal processing error has occurred.
DATA #1 : String, 17 bytes
Expected TEMP TCB
DATA #2 : String, 7 bytes
sqldtcb
CALLSTCK: (Static functions may not be resolved correctly, as
they are
resolved to the nearest symbol)
[0] 0x090000000B861070 sqlzSetAndLog901 + 0x298
[1] 0x09000000095FF384
sqldFixExistingTCB__FP16sqeLocalDatabaseP9SQLP_LSN8iN33PP8SQLD_T
CB + 0xBA0
[2] 0x0000000000000000 ?unknown + 0x0
[3] 0x09000000096D7E8C
sqldLockTableFixTCB__FP8sqeAgentUsT2UcUliN26N25T6PcT6T12_T6P14SQ
LP_LOCK_INFOPP8SQLD_TCBUiT18_@OL@25033
+ 0x68
[4] 0x09000000095D4C38
sqldLockTableFixTCB__FP8sqeAgentUsT2UcUliN26N25T6PcT6T12_T6P14SQ
LP_LOCK_INFOPP8SQLD_TCBUiT18_
+ 0x218
[5] 0x0900000008BF940C
sqldGetTableDataForPermOrTemp__FP8sqeAgentP19SQLD_TABLE_DATA_REQ
P15SQLD_TABLE_DATAUsT4UcT4Ul
+ 0x24C
[6] 0x0900000008BF8EE8
sqldGetTableData__FP8sqeAgentP19SQLD_TABLE_DATA_REQP15SQLD_TABLE
_DATA +
0x160
[7] 0x0900000007445D50
sqlrkrts__FP8sqlrr_cbsP19SQLD_TABLE_DATA_REQiT4PiPPcP15SQLD_TABL
E_DATAP13SQLO_MEM_POOLPbPl
+ 0xCD8
[8] 0x0900000008F68450
populate_from_pd__9sqlnq_ftbFCP8sqlrg_pdCP11sqlrrstringCP3locCiC
PC21sqlrlc_systables_info
+ 0x2C38
[9] 0x0900000008F53ECC
populate_from_pd__9sqlnq_ftbFCP8sqlrg_pdCP11sqlrrstringCP3locCiC
PC21sqlrlc_systables_info
+ 0x2F0 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Update to 10.1.0.4 *
**************************************************************** |
| Local Fix: |
Perform RUNSTATS on the temporary table |
| available fix packs: |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Problem Fixed In 10.1.0.4 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 03.04.2014
02.06.2014
02.06.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.4
|
 |
