|
Problem IT09420
|
Status: Closed |
IN DB2DIAG.LOG INFORMATION "DEFERRED ADC IS SKIPPED DUE TO PRIOR ERROR" MIGHT BE REPORTED FOR GLOBAL TEMPORARY TABLE WITH INDEX |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
After update to DB2 10.1 Fix Pack 4 you might notice information
in db2diag.log within GLOBAL TEMPORARY TABLE usage with index
access attempt when inserting data into table.
Information with error about the index missing in db2diag.log
are similar to the following:
2015-01-28-18.19.08.875000+180 I599854142F590 LEVEL: Info
PID : 12345 TID : 1234 PROC
:db2syscs.exe
INSTANCE: DB2INST1 NODE : 000 DB :
SAMPLE
APPHDL : 0-200 APPID:
127.0.0.1.54321.150101012345
AUTHID : DB2ADMIN HOSTNAME: MYHOST
EDUID : 4321 EDUNAME: db2agent (DB) 0
FUNCTION: DB2 UDB, data management, sqldRowInsert, probe:5541
MESSAGE : ZRC=0x8404007E=-2080112514=SQLD_IXNOEX "INDEX DOES NOT
EXIST"
DATA #1 : String, 42 bytes
Deferred ADC is skipped due to prior error
This might show up for a DECLARE GLOBAL TEMPORARY TABLE
statement, when specifying clauseNOT LOGGED with ON ROLLBACK
DELETE ROWS which is the default option for it. When index
object were marked invalid with next insert, sqldRowInsert will
get SQLD_IXNOEX, which will lead to a higher layer of DB2
recreating the index object as update. This causes no problem in
the database other than the db2diag.log message. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.5 and Fix Pack 7 *
**************************************************************** |
| Local Fix: |
|
| Solution |
Problem was first fixed in DB2 Version 10.5 and Fix Pack 7 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 11.06.2015
20.01.2016
20.01.2016 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.7
|
 |
