DB2 - Problem description
Problem IT06853 | Status: Closed |
DB2 MAY FAIL TO MOVE TABLE INTO NOT_SHARED STATE | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
DB2 pureScale server may fail to move a table into NOT_SHARED state for explicit hierarchical locking even there is only one member accessing that table. During the time of the problem, db2diag.log will continually show up error messages that db2ehl EDU gets interrupted when ever the table is accessed. Here is an example of the error messages: 2015-01-01-01.01.01.000000+480 I53630300E567 LEVEL: Error PID : 123456 TID : 6789 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-12345 APPID: *N0.DB2.150101010101 AUTHID : DB2INST1 HOSTNAME: db2server EDUID : 6789 EDUNAME: db2ehl 0 (SAMPLE) 0 FUNCTION: DB2 UDB, data management, sqldEHLPrepForPhaseOne, probe:897 MESSAGE : ZRC=0x80020003=-2147352573=SQLB_INTRP "USER INTERRUPT DETECTED" DIA8003C The interrupt has been received. 2015-01-01-01.01.01.000001+480 I53630868E1423 LEVEL: Error PID : 123456 TID : 6789 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-13526 APPID: *N0.DB2.150120081603 AUTHID : DB2INST1 HOSTNAME: db2server EDUID : 6789 EDUNAME: db2ehl 0 (SAMPLE) 0 FUNCTION: DB2 UDB, data management, sqldEHLAttemptUpgradePhaseOne, probe:1545 MESSAGE : ZRC=0x80020003=-2147352573=SQLB_INTRP "USER INTERRUPT DETECTED" DIA8003C The interrupt has been received. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * The user is running with EHL feature. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Update to 10.5.0.6 * **************************************************************** | |
Local Fix: | |
Deactivate the database on the member where the table state shows incorrectly and access the table would move the table into correct state again. | |
Solution | |
Problem Fixed In 10.5.0.6 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 29.01.2015 26.08.2015 26.08.2015 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.5.0.6 |