IBM Support

IC67359: SELECT QUERY ON DATATYPE DATE AND REGISTER CURRENT DATE WITHIN STORED PROCEDURE MAY RETURN UNEXPECTED RESULT ON SOME LOCALES

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The problem may occur under the following scenarios.
    
    1. Using a locale with the date format other than following, for
    example, Australian English.
         ISO yyyy-mm-dd
         USA mm/dd/yyyy
         EUR dd.mm.yyyy
    
    2. Running a select query on datatype DATE and register CURRENT
    DATE within stored procedure.
       CHAR(CURRENT DATE) will not cause the problem.
    
    Here is an example on Australian English locale.
    
    CREATE PROCEDURE S1.TEST1()
        SPECIFIC S1.TEST1
        DYNAMIC RESULT SETS 1 LANGUAGE SQL P1:
    BEGIN
            Declare c_Hits Cursor with return for
            SELECT CURRENT DATE AS DATE1
            from sysibm.SYSDUMMY1;
            Open c_Hits;
    END P1
    
    
    $ db2 call TEST1
    
      Result set 1
      --------------
    
      DATE1
      ----------
      0022-65534
    
      1 record(s) selected.
    
      Return Status = 0
    

Local fix

  • Not available.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL who are using locale with date format other than         *
    * ISO(yyyy-mm-dd), USA (mm/dd/yyyy),EUR (dd.mm.yyyy).          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * As same as Error description.                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Version 9.7 FixPack 3.                            *
    ****************************************************************
    

Problem conclusion

  • Problem was first fixed in DB2 UDB Version 9.7 FixPack 3.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC67359

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-03-22

  • Closed date

    2010-09-27

  • Last modified date

    2010-09-27

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

    IC67358

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

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSN

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.7","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
27 September 2010