DB2 - Problem description
Problem IT33533 | Status: Closed |
SQL0913 RC=80 NOT BEING CAPTURED BY DB2PDCFG -CATCH LOCKTIMEOUT | |
product: | |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 | |
Problem description: | |
This problem occurs when the DB2LOCK_TO_RB registery variable is set to "statement". Under this setting, lock timeout error will trigger statement rollback instead of transaction rollback. A typical way to investigate the cause of lock timeout is via "db2pdcfg -catch locktimeout". This method is not able to produce the expected output when DB2LOCK_TO_RB=statement. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * all * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.5.5.0 or higher * **************************************************************** | |
Local Fix: | |
We can use "db2pdcfg -catch -2146434992 count=10" to capture SQLP_LTIMEOUT_STMT_RB | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 13.07.2020 20.11.2020 20.11.2020 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |