IBM Support

IC77152: SQL1224N ERROR AND SIGNAL 11 CRASH IN SQL CONTAINING LIKE PREDICATES IN CULTURALLY CORRECT COLLATION DATABASES.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as fixed if next.

Error 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.
    

Local fix

  • No local fix available
    

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.             *
    ****************************************************************
    

Problem conclusion

  • Problem (APAR IC77121) will be fixed in version 9.7 Fix Pack 5
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC77152

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    950

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-06-24

  • Closed date

    2011-07-22

  • Last modified date

    2011-07-22

  • APAR is sysrouted FROM one or more of the following:

    IC77121

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

  • R950 PSY

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.5

Reference #: IC77152

Modified date: 22 July 2011