DB2 - Problem description
Problem IC77152 | Status: Closed |
SQL1224N ERROR AND SIGNAL 11 CRASH IN SQL CONTAINING LIKE PREDICATES IN CULTURALLY CORRECT COLLATION DATABASES. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problem description: | |
DB2 generates SQL1224N error and crashes with Signal 11 when 'LIKE' predicate is used on tables in database created with Unicode codeset and Culturally Correct Collation. The issue can be reproduced with the following test: create database caseins using codeset utf-8 territory ru collate using UCA500R1_LRU_S2 create table test_like (name varchar(20)) in userspace1; insert into test_like values ('test'); insert into test_like values ('test'); db2 -td@ "begin declare p_par varchar(20) default '%t%';declare cnt int;set cnt = (select count(name) from test_like where name like p_par);end@" The following error gets generated: 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 For this error to occur, the following conditions should be met: 1. UTF database using a Culturally Correct Collation must be used 2. The table involved in the SQL statement including a LIKE predicate should contain more than 1 row A sample stack for the crash above is: sqlriCCCLikeFree sqlricls_complex sqlriCloseExecuteSection sqlrr_execute_immediate sqlrr_execimmd sqljs_ddm_excsqlimm sqljsParseRdbAccessed sqljsParse sqljsSqlam sqljsDriveRequests sqljsDrdaAsInnerDriver sqljsDrdaAsDriver sqeAgent::RunEDU sqzEDUObj::EDUDriver sqlzRunEDU sqloEDUEntry start_thread The error can be produced on any platform. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * The problem is due to incorrect pointer operations that * * control link list of structures containing rows evaluated in * * select statements. It causes memory leak and eventually * * segfault with Signal 11. * **************************************************************** * RECOMMENDATION: * * None for 9.5 version. Upgrade to 9.7 Fix Pack 5. * **************************************************************** | |
Local Fix: | |
No local fix available | |
Solution | |
Problem (APAR IC77121) will be fixed in version 9.7 Fix Pack 5 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 24.06.2011 22.07.2011 22.07.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.5., 9.7.FP5 | |
Problem solved according to the fixlist(s) of the following version(s) |