DB2 - Problem description
Problem IT38541 | Status: Closed |
INSERT INTO XML COLUMN OF A DRDA NICKNAME MAY CAUSE A SIGNAL 11 TRAP | |
product: | |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 | |
Problem description: | |
The insert of data into an XML Column of a DRDA Nickname may fail with SQL1224N The database manager is not able to accept new requests, has terminated all requests in progress, or has terminated the specified request because of an error or a forced interrupt. SQLSTATE=55032 and a trap occurs. The top of the stack will contain sqlqg_piece_lob sqlqgInsert sqlriDjxIns sqlriSectInvoke This can occur when the XML Column is the only LOB column. The problem does not occur if there is another LOB column also being inserted. Altering the Nickname and changing a VARCHAR column to a CLOB will work-around the problem. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All users of DB2 Federated fucntionality * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 11.5 Mod 7 * **************************************************************** | |
Local Fix: | |
ALTER NICKNAME and alter a VARCHAR column to CLOB will work-around the problem | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * All users of DB2 Federated fucntionality * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 11.5 Mod 7 * **************************************************************** | |
Comment | |
Problem fixed in DB2 11.5.7 | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 29.09.2021 30.11.2021 30.11.2021 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |