DB2 - Problem description
Problem IC63734 | Status: Closed |
LOAD NOT HANDLING SPECIFIC LOCK FAILURE ERROR (SQLP_LCON) GRACEFULLY, CAUSES -902 INSTEAD. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
Load is not handling a specific failure when attempting to acquire a lock (SQLP_LCON - unable to acquire a conditional lock) gracefully. Instead of returning an appropriate error code(such as SQL911N), the Load fails with a 902 and application connection is severed. For example, >db2 load from ~/blah.del of del replace into table1 SQL0902C A system error (reason code = "121") occurred. Subsequent SQL statements cannot be processed. SQLSTATE=58005 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Linux AMD64 * **************************************************************** * PROBLEM DESCRIPTION: * * When timeout occurs to a resource, sql 902 is produced which * * disconnects the user from the database. A better code would * * be sql 911 (timeout) which allows the user to continue * * processing without re-connecting to the database * **************************************************************** * RECOMMENDATION: * * l * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows | |
Solution | |
replace sql902 (system error) by sql911 (timeout) on timeout | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 13.10.2009 15.01.2010 15.01.2010 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.1 |