PI38994: SQLCODE413 WHEN SQL STATEMENT CONTAINS PREDICATE WITH DOUBLE OR FLOAT COLUMN AND STRING REPRESENTS NUMBER IN SCIENTIFIC NOTATION

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Unexpected SQLCODE413 could happen for an SQL statement
  containing a predicate with a DOUBLE or FLOAT column and a
  string that represents a number in scientific notation.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All DB2 10 and 11 for z/OS users of an SQL   *
  *                 statement containing a predicate with a      *
  *                 DOUBLE or FLOAT column and a string that     *
  *                 represents a number in scientific notation.  *
  ****************************************************************
  * PROBLEM DESCRIPTION: Unexpected SQLCODE413 could happen for  *
  *                      an SQL statement that satisfies all of  *
  *                      the following conditions:               *
  *                                                              *
  *                      1. It contains a subquery, references   *
  *                         a view or it is an UPDATE or DELETE  *
  *                         statement.                           *
  *                      2. It contains a predicate with a       *
  *                         column and a string that represents  *
  *                         a number in scientific notation.     *
  *                      3. The data type of column is DOUBLE or *
  *                         FLOAT.                               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  An example is shown below:
  
  CREATE TABLE T1 (C1 DOUBLE);
  INSERT INTO T1 VALUES (1.2);
  
  DELETE FROM T1 WHERE C1 < '2.8E381';
  
  DB2 did not process the aforementioned SQL statement correctly,
  and this caused the unexpected SQLCODE413.
  

Problem conclusion

• DB2 has been modified to correctly process the aforementioned
  SQL statement, so there will be no SQLCODE413.
  
  Additional keywords: SQLFLOAT SQLDECIMAL SQLDELETE SQLUPDATE
                       SQLSUBQUERY
  

Temporary fix

Comments

APAR Information

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

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

  UI28288 UI28289

Modules/Macros

• DSNXOPRU
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RA10 PSY UI28288

     UP15/06/23 P F506

• RB10 PSY UI28289

     UP15/06/23 P F506

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.