PM42749: INCORROUT WHEN COMPARING BINARY STRINGS

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Incorrout may happen when query is comparing binary strings.
    DB2INCORR/K
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS       *
    *                 users who use BINARY and VARBINARY data      *
    *                 types.                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION: Incorrect output may occur for an SQL   *
    *                      statement that contains a predicate     *
    *                      comparing a BINARY value with a         *
    *                      VARBINARY value.                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Incorrect output may occur for an SQL statement that contains
    a predicate comparing a BINARY value with a VARBINARY value.
    For example,
    CREATE TABLE MYTAB1 (COL1 BINARY(5)) ;
    CREATE TABLE MYTAB2 (COL1 VARBINARY(5)) ;
    INSERT INTO MYTAB1 VALUES (BINARY('ABC'));
    INSERT INTO MYTAB2 VALUES (VARBINARY('ABC'));
    SELECT HEX(MYTAB1.COL1)
    FROM   MYTAB1,
           MYTAB2
    WHERE  MYTAB2.COL1 = MYTAB1.COL1;
    
    Two binary strings are equal only if the lengths of the two
    strings are identical. If the strings are equal up to the length
    of the shorter string, the shorter string is considered
    less than the longer string even when the remaining bytes in the
    longer string are hexadecimal zeros.
    
    In the SELECT statement above, one record 'C1C2C30000' is
    returned when no record is expected(RNF). This problem happens
    because DB2 doesn't handle the data types correctly when
    comparing the two values.
    

Problem conclusion

  • DB2 code is fixed to handle the data types correctly when
    comparing BINARY with VARBINARY values.
    
    Additional Keywords: SQLINCORR SQLINCORROUT INCORROUT
                         DB2INCORR/K
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    PM42749

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-06-30

  • Closed date

    2011-08-09

  • Last modified date

    2011-09-01

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

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

    UK70654 UK70655

Modules/Macros

  •    DSNXGLIB DSNXGOJ  DSNXGTRF DSNXGVCM
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UK70654

       UP11/08/26 P F108

  • R910 PSY UK70655

       UP11/08/26 P F108

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

DB2 for z/OS

Software version:

A10

Reference #:

PM42749

Modified date:

2011-09-01

Translate my page

Machine Translation

Content navigation