DB2 - Problem description
Problem IT34469 | Status: Closed |
CLIENT GETS -901 DTS MISMATCH BETWEEN REQUEST AND CACHE INSTEAD OF -910 | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
Intermittent -901 instead of expected -910 are possible when running ALTER SQL statements and commits are not done by the application as expected. In sql where user should commit immediately after the ALTER SQL statement, if that is not done, SQL910N should be returned. However sometimes SQL0901N is returned and FODC directory is created. This is wrong. db2diag.log will have: FUNCTION: DB2 UDB, data management, sqldSeqFetchUpdateGen, probe:3038 MESSAGE : ZRC=0x82040001=-2113667071=SQLD_NONSEVERE_PRGERR "non-severe dms programming error" DIA8532C An internal processing error has occurred. DATA #1 : String, 38 bytes DTS mismatch between request and cache DATA #2 : String, 21 bytes | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users expecting -910 could get -901. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * See Error Description * **************************************************************** | |
Local Fix: | |
Do: execute immediate 'alter table alter column ... commit;-- As expected | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * Users expecting -910 could get -901. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * See Error Description * **************************************************************** | |
Comment | |
See Error Description | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 07.10.2020 19.03.2021 19.03.2021 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |